Source Code Version Control

I personally don't like connecting to production site directly with VS.net.

Reason:

1) Unlike ASP, VS.net compiles the whole application into a single dll (at least in most cases). THis means that you can ruin your whole site when you make a mistake in your code. We have seen this happened w/ several customers before.

2) When you edit your site directly on our server, you have many files that are not needed for your application to run. Most of the files in a web projects are not need, for example, *.vb, *.cs, *.resx, *.pdb, etc.... It just takes up your webspace and create confusion. It can also be a security threat because all you source code is there.

3) You do not have the ability to use debugger on our server

4) You do not have a back up of your site.

5) Everytime you recompile, it clears all the session var.

This is how we deploy to our site.

- Develop and test on our development server
- Deploy to a staging area (using VSS) on the production server w/ FP installed. Compile there.
- Use the copy project function of VS.net to copy the necessary files to the live site.

Hope this helps.

quote:Originally posted by Mark Jerde

I figured out how to use Visual Studio directly on my site. Very impressive! Unfortunately Visual SourceSafe won't work on the solution because of the FrontPage extensions.

Are there better ways than just ftp'ing the whole site to my hard drive & periodically VSS'ing it?

Thanks.

-- Mark

</blockquote id="quote"></font id="quote">

 

Very cool.

Glad you figured that out.

quote:Originally posted by Mark Jerde

Found a KB article. Plenty of disk space now.

http://support.microsoft.com/?id=261002

-- Mark

</blockquote id="quote"></font id="quote">