What does "deployment" actuly do?

[skitty123]

I had some basic questions about application deployment:
I have a small ASP .NET application in C# that is in development on an XP machine, Uses a sql server 2000 database on the same machine. the web application has dependency on 2 other projects that are part of the same .sln (solution) file (Using VISUAL STUDIO .net 2003)
Concurrent users will proabably be 5-6 as it will be an intranet appication only
I have created the .msi file for deployment.

I was wondering:
1) Instead of running the setup.exe and installing the application on a different machine, can I leave it on the development machine (Xp pro operating system)? (users can currently access the application by navigating to the computer name within the network), what might be the implications of this?

1) If decided to keep the current XP machine as the application host, do I still need to run the set up (.MSI) file on this machine? (I mean are there any performance benefits to this , as the source code is already on this machine anyway, will the Setup do anything different?)



Send to a Friend Printer Friendly

 

[marinero]

You can deploy the executable from your machine acting as server. If you have IIS running you create a virtual directory and give the users the link to it. Make sure the server is listed in the client's browser security setting to be part of the intranet.

 

[skitty123]

thanks marinero,
I have IIS and have created the visrtual directory and other users can browse to it ok.

but do I still need to run "setup" ( i mean the .msi file to install the application) if so, why , as i already have teh source code on this machine, will running the deployment haev any performace/ security advantage?

 

[skitty123]

...I guess my question is this if I leave the current set up is thecode getting compiled each time someone navigates to the site? or once i compile it in my editor, that is the version being used untill i compile it again.