Best way to deploy from dev to production site using VStudio

  • Thread starter Thread starter Kent P. Iler
  • Start date Start date
K

Kent P. Iler

Hi,

I'm using Visual Studio, and I'm used to the VS6 way of having multiple
projects open in one solution, and then you can just move files that have
changed from one environment to another.

With VS.NET, if I try to setup a project on my dev machine, and a project on
my production machine under that same solution, I get an error saying you
can't have the same project name under the same solution.

If I just have the dev site open, and choose Copy site, it moves
everything - not just the changed files!!! This, of course, stinks if you
only need a few files updated instead of the entire site.

Can someone recommend a good way of doing this so I can move an individual
file or a selection of files instead of the entire project?

Thank you!

-- Kent Iler
 
Hi,

ASP.NET pages are coupled due to code behind. All code behind classes
compiled to single DLL that exist in application "bin" directory.
Automatic deployment should not just check and compare changes that made
on ASPX files but also check and compare code behind files against ...
IL presentation of all code behind files. Comparing code behind files
are more complicated then comparing file size (such as ASP or HTML
pages). if you want you can apply such mechanism if you don't use code
behind files.

Natty Gur[MVP]

blog : http://weblogs.asp.net/ngur
Mobile: +972-(0)58-888377
 
Natty Gur said:
Hi,

ASP.NET pages are coupled due to code behind. All code behind classes
compiled to single DLL that exist in application "bin" directory.
Automatic deployment should not just check and compare changes that made
on ASPX files but also check and compare code behind files against ...
IL presentation of all code behind files.
Click to expand...

Why not just notice that the .dll file has changed and then deploy it
because it's changed?
 
Back
Top