Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Best Practice of .net deployment

Best Practice of .net deployment

Best Practice of .net deployment

Hi guys,

Just wondering how you guys usually do the deployment package for .net application.

I have read some people usually create 2 packages:
one - for bin directory included dll file and default.aspx without any cs files.
the other one - for web.config

Any input about this will be much appreciated.

RE: Best Practice of .net deployment

Best practices are to automate the process. Don't deploy directly from Visual Studio. Separate configuration from installation. Doing this, it won't matter if you put everything into one deployment package. The automation will change the web.config settings to their proper values. You should have separate settings for debug, staging, and release.

You may want to readup on web.config transformations.

Craig Berntson
MCSD, Visual C# MVP, www.craigberntson.com/blog

RE: Best Practice of .net deployment

Hi craigber,

Would you care to elaborate more about automate the deployment process from your side? with example if possible.

and where do we store the proper values (ie. connectionstring) to update the web.config

Thanks Heaps in advance man

RE: Best Practice of .net deployment

Read the links I posted about web.config transformations to find out where to store connection strings.

Automated deployment is easy to do with tools such as Go or Octopus. You can even setup TFS or Team City to do it. Research topics such as Continuous Integration or Continuous Deployment. My book, Continuous Integration in .Net has some good information.

Basically, you have a build server that builds and handles automated testing of your app. It stores and catalogs the build artifacts (assemblies, etc). Then, when you're ready, you use a deployment tool to select which version of the artifacts to deploy.

Craig Berntson
MCSD, Visual C# MVP, www.craigberntson.com/blog

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close