Moving ASP.Net programs to production

[Jim Smith]

Hello everyone,

I work for a large company that supports many websites. My manager
wants everything rewritten in ASP.Net. He has given me the task to
find out the best method for putting programs into production. I know
that there is a "bin" issue with the different projects that are
created. I don't have a clue on how to organize everything so he can
move programs into production easily. Any help would be greatly
appreciated!

Our current traditional ASP structure is as follows:
We store all programs in Source Safe.
Programs are checked out to our Programming Test Server.
After the programs are programmer tested, they are moved to the Users
Test Server.
If approved by the users, the programs are moved by our Manager to the
Production Server in a New Release every 6 weeks.

Thanks!
Jim Smith
Lead Internet Specialist
http://FunPlacesToFly.com

 

[Helen]

Hello everyone,

I work for a large company that supports many websites. My manager
wants everything rewritten in ASP.Net. He has given me the task to
find out the best method for putting programs into production. I know
that there is a "bin" issue with the different projects that are
created. I don't have a clue on how to organize everything so he can
move programs into production easily. Any help would be greatly
appreciated!

One thing I found helpful about ASP.NET was that pretty much all the
stuff that wasn't actually a webpage (so library code, web components,
even code behind code) could be stored in another dll file.

When the solution is compiled, the dll is copied to the webapp's bin
directory and moving the site to another server is simply a matter of
copying the webapp directory.

Helen

 

[Curt_C [MVP]]

Unleash It (formerly WebDeploy) will handle this for you.
It's quite handy.
http://www.eworldui.net/UnleashIt/