Web Project Artifacts - Best Practices?


I'm wondering if anyone has recommended best practices when it comes to publishing artifacts for a typical .Net web application. We have a typical .Net web application project (3.5) which references some class library projects. When TeamCity completes a build successfully, we want to have the application "staged" for deployment to one of the test environments (so that we can simply xcopy the site to the test server). I think I can setup all of the artifact publishing rules in TeamCity that would be needed to do that (.aspx files, .ascx files, dll's, etc.)  But I was just curious how others are doing that and if there's an easier way. Thanks for any advice you can provide.

Kevin Kuebler

1 comment
Comment actions Permalink

Sorry for the delay. The question is still actual with latest TeamCity release?

Kind regards,

Please sign in to leave a comment.