Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Newbie Deployment Question(s)

Status
Not open for further replies.

whateveragain

Programmer
Apr 20, 2009
92
US
I'd like to deploy my web application before it's finished to make sure my approach is working.
1. Is it better to deploy a debugable version?
2. Since I'm a newbie, I'm concerned about bugs (or whatever) causing a server crash. How can I avoid causing a server crash. The portion of the application I play to deploy does not have any errors at this time.
3. Any suggestions on deployment will be greatly appreciated.

Thanks
 
1st, don't treat your production environment as a sandbox for testing. You should find another box(es) to test your software on before you deploy to production. Ideally your testing boxes should be similar to your production boxes. And, if possible, isolated from the production network.

Another option is to use a virtual network with servers and clients to test the software on existing hardware without interfering with the physical network.

answers to your questions
1. it's testing so preformance isn't the top concern, although load testing should be done at this point. I would deploy a release build. Hopefully the application includes some logging, so you can enable logging if things aren't working quite right to determine what the problem is. If your not, then i recommend a logging library like log4net.

2. you can't. However if you built a typical webforms based website you will likely not crash the server, only the web application. To prevent bugs I recommend a testing framework like nunit or mbunit. they allow you to test pieces of your code in an automated fashion. then when you tie all the pieces together they should work without error.

along unit tests you can test the complete application in a virtual environment. see my starting comment.

3. Again I strongly recommend not deploying from your development machine to production. There are too many variables between the 2 environments for things to just work. Deploy to the intermediate server for acceptance testing and make sure everything is working properly. once this is confirmed, then deploy to the production server.

Jason Meckley
Programmer
Specialty Bakers, Inc.
 
this tool would not solve your problems of a testing environment.

that might be useful for large enterprise size applications which require large amounts of configuration. My gut feeling says in your case this isn't required. Also, alot of what this tool does can be done by other tools which specialize in each area (automated builds, version control, configuration)

I deploy may apps using xcopy (copy and paste) and then create the associated virtual directory.

If I encountered a larger project which required fine tuning the deployment and configuration I would use an automated deployment script with a package like nant or psake. I doubt I would use the tool listed above.

Jason Meckley
Programmer
Specialty Bakers, Inc.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top