	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

05/11/2009 at 12:24PM PDT, ID: 24399184

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.1

Deploying Websites Via Visual Source Safe

Asked by MClarkCCR in Visual SourceSafe-Team Foundation, Programming for ASP.NET, Visual Studio

Tags: Visual Source Safe, Visual Studio, Web.config

Hello,

We have recently installed a Visual Source Safe solution on our network and we are currently experimenting with deploying from VSS to our live servers. We've hit two issues that while deploying that we think can probably be handled easier, we're just not sure what we should do.

We place all 3rd party .dlls included in a site within the App_Code\Libraries folder and then we add a reference to that file, which copies those files and their .refresh files to the bin folder. Every file in the project EXCEPT the dlls in the bin folder are in source safe and get pushed to the live server when we deploy, but the dlls in the bin folder don't so then the site errors out with the message that it can't find the required assemblies. There doesn't seem to be an option to add them to source control either. Then what we have to do is FTP the .dll files into the \bin on the live server. Seems like an unecessary last step, and we'd like it so that the .dlls just get pushed when we deploy from VSS. What could we do to correct that?

The second issue is a more minor one, but it deals with connection strings in web.config. We point the web.config for the dev site to a dev version of the related DB, so when we push changes the web.config gets pushed with the dev connection string to the live server. Is there a way to have the deployment ignore connection strings in web.config so that all other changes are recorded and deployed? Or will we just have to comment/uncomment the dev and live connection strings just before deploying?

TIA,

Mike

View the Solution FREE for 30 Days

20091111-EE-VQP-91 - Hierarchy / EE_QW_3_20080625

1. Admin3k23,450
2. TheSaturn496,000
3. alainbryden4,500
4. RiteshShah4,000
5. PaulHews3,750
6. jpadda3,500
7. emoreau2,950
8. TheLearn...2,750
9. rascalpants2,500
9. tedbilly2,500
9. melmers2,500
9. nutsch2,500
13. dglenp2,000
13. TheVeee2,000
13. Mikal6132,000
13. LordWabb...2,000
13. sunnycoder2,000
13. samtran0...2,000
13. aneeshatti...2,000
13. spprivate2,000
13. matthews...2,000
13. ezraa2,000
13. tillo-httpd...2,000
13. DaTribe2,000
13. Shaun_Kl...2,000
13. elimesika2,000
13. GMurad2,000
13. Hairbrush2,000
13. GuitarRich2,000
13. Archyon2,000
13. Laindow2,000
13. fryezz2,000
13. prabhakar...2,000
13. trideep2,000
13. htcsoccer2,000

1. Admin3k23,450
2. emoreau11,150
3. TheLearn...10,750
4. TheSaturn496,000
5. gauthampj5,500
6. alainbryden4,500
7. elimesika4,000
7. RiteshShah4,000
9. PaulHews3,750
9. GrahamSkan3,750
11. HooKooD...3,600
12. samtran0...3,500
12. jpadda3,500
14. Mikal6133,200
15. JuckMan2,750
16. rascalpants2,500
16. tedbilly2,500
16. melmers2,500
16. nutsch2,500
20. iboutchkine2,000
20. Rem2,000
20. dglenp2,000
20. TheVeee2,000
20. Dhaest2,000
20. LordWabb...2,000
20. Paka2,000
20. PhilAI2,000
20. rettiseert2,000
20. existenz22,000
20. sunnycoder2,000
20. exalkonium2,000
20. dungla2,000
20. aneeshatti...2,000
20. rgautier2,000
20. spprivate2,000
20. jjones6662,000
20. vadimrapp12,000
20. matthews...2,000
20. smitcham2,000
20. jake0722,000
20. rsomasun...2,000
20. ezraa2,000
20. CSecurity2,000
20. tillo-httpd...2,000
20. strickdd2,000
20. DaTribe2,000
20. Shaun_Kl...2,000
20. G0ggy2,000
20. davrob602,000
20. nds_rahu...2,000
20. slm5112,000
20. GMurad2,000
20. Hairbrush2,000
20. GuitarRich2,000
20. Archyon2,000
20. Laindow2,000
20. fryezz2,000
20. prabhakar...2,000
20. trideep2,000
20. htcsoccer2,000

Deploying Websites Via Visual Source Safe

Asked by MClarkCCR in Visual SourceSafe-Team Foundation, Programming for ASP.NET, Visual Studio

Tags: Visual Source Safe, Visual Studio, Web.config

About this solution