Hi,
I've got a slight issue here where I have my existing web site which runs on 
ASP.net.  I want to do a couple things to it.  
One: I want to be able to recompile the entire framework to use .NET 4.5 
instead of 4.0 (though the main developer's not down with that).  I know how to 
do this; take the developer package and just tell it to compile to the latest 
framework instead of the earlier one and then press F5 again, but the question 
is that the developer package and the deployment package are different, so what 
is the best way to incorporate my changes from the development environment into 
the production environment on my server (no source code) with as little work as 
possible?  And then without dumping source code on the server as well?  What I 
would think about doing is to compile the application again and then move the 
compiled folder into production from the development machine either by FTP or 
via manual upload if I'm that lazy.  The question though is whether that would 
be enough though.  Or is there something more I'd have to do?  
Then there's the problem of having a primary and backup server in two different 
locations.  Would I use Web Deploy for moving the application between the two 
IIS servers?  What about the nasty bug in Web Deploy that causes the IIS 
extension not to be able to deploy imported applications correctly?  What about 
the fact that the primary and backup server are running two different versions 
of IIS?  Is there a reliable way to do this to ensure that the backend database 
running behind the application stays in sync as well?  This is over a WAN 
connection between two opened ports.  Do you folks have any ideas?  Thanks.  


Reply via email to