Deploying a simple app.

[Ant]

Hi, I'm a newbie to .NET so...
After developing a simple, non distributed application (if that's still
applicable these days), how do I move the appliation to another PC?
Is it simply a matter of copying a folder, or exe file over? If so, do you
copy over the bin folder, the obj folder or just the exe file? Both seem to
work for me but what is the proper way?

Thanks for any ideas on this.
Ant

[Tedmond]

If you use 100% .Net component. Just copy everything from the \bin folder
PLUS any runtime file of your application such as runtime images or
configuration files etc...

"Ant" wrote:

Hi, I'm a newbie to .NET so...
After developing a simple, non distributed application (if that's still
applicable these days), how do I move the appliation to another PC?
Is it simply a matter of copying a folder, or exe file over? If so, do you
copy over the bin folder, the obj folder or just the exe file? Both seem to
work for me but what is the proper way?

Thanks for any ideas on this.
Ant

[Light]

if you dont use the GAC or any components that use the GAC then you can
just copy and paste. You'll probably want to create an MSI installer
for it though so you can create short cuts. You'll only need the EXE
and any DLL it access. If any components use the GAC then you'll need
to use MSI installer.
Curtis
http://www.ghostclip.com
The Premier Help System For Developers

[Light]

btw.. the object files are intermediate files that are not needed.
they are used by linker.

[Arnd Hurlbrink]

Copy and paste the contents of the bin\release folder after release build of
course - if you use any config or references to other projects or dlls they
will automatically updated. If you any external resources such as images or
data files, these shuld be in this or in a subfolder.

Copying the files over is referred to as 'xcopy' deployment.

You can run a dotnet app from a fileserver, but you are severely restricted
to what it can do. You'll get security exceptions if you do anything more
ambitious than display some forms and controls. With the framework
configuration, you can grant an app more permisions, but then I would urge
you to sign it with a strong name (sn) or a private key and only allow those
to run. Similarly you can launch a .net app from a webpage.

Consider putting your dlls in the Global Application Cache (GAK) if you have
a stable dll that if used across a number of applications.

VS 2005 introduces a number of cool options to make deployment a whole lot
easier.

I hope that helps.

Arnd Hurlbrink
"Light" <Li********@gmail.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...

if you dont use the GAC or any components that use the GAC then you can
just copy and paste. You'll probably want to create an MSI installer
for it though so you can create short cuts. You'll only need the EXE
and any DLL it access. If any components use the GAC then you'll need
to use MSI installer.
Curtis
http://www.ghostclip.com
The Premier Help System For Developers