Geeks With Blogs

News



Microsoft Store

Support This Site


AddThis Social Bookmark Button

Locations of visitors to this page

Subscribers to this feed

TwitterCounter for @sdorman

Creative Commons License


Scott Dorman Microsoft MVP, Software Architect, Developer, Author

In a recent email discussion between a few of the Subtext developers and myself, we talked about the need to have the Visual Studio editor settings (like tab size, curly brace location, etc.) stored with each solution as well as globally.

The problem here is that many of us use the same development machine for our "real work" and our personal or open source projects. For some people this might not be a problem, but for most of us, it is. The real issue comes about when one client mandates a certain style that is different from either your personal preferences or from any other projects you work on. In order to accomodate these differences, you end up creating multiple Visual Studio settings files, one for each client or project you work on that has different settings. That's the realtively easy part. The hard part comes when you have to constantly remember to switch settings files and remember which file belongs to which client or project.

The solution that we discussed is that these settings should be stored at the solution level, most likely in a separate settings file (like <solutionname>.settings). There should be an easy way to set these options, and possibly apply them globally as well. If the settings file doesn't exist, then the global settings should be used.

The benefits are:

  1. The settings can be managed and placed under source control.
  2. The settings travel with the solution, so new developers automatically pick up the desired settings.
  3. The developer no longer has to create multiple settings files and switch between them each time he/she changes projects.

The settings file could even be pushed in to TFS in the same way the code analysis settings can be migrated to the solution.

This request has been submitted to  Microsoft Connect, and can be viewed here:

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=272773

Posted on Monday, April 23, 2007 11:12 AM General | Back to top


Comments on this post: Visual Studio user settings per project/solution

# re: Visual Studio user settings per project/solution
Requesting Gravatar...
Good call - I like it!

I'll be keeping an eye on it for sure :)
Left by Steve on Apr 23, 2007 3:27 PM

# Visual Studio user settings per project/solution
Requesting Gravatar...
You've been kicked (a good thing) - Trackback from DotNetKicks.com
Left by DotNetKicks.com on Apr 23, 2007 6:40 PM

# re: Visual Studio user settings per project/solution
Requesting Gravatar...
Scott,

I had posted a similar suggestion a few months ago:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=253597

and talked about it on my blog
http://www.winterdom.com/weblog/2007/01/24/VisualStudioCodeFormattingPropertiesAndSolutions.aspx

Didn't get much traction, though (few people voted for it, and MS closed it down in less than a couple of days). Hopefully yours will get farther.
Left by Tomas Restrepo on Apr 23, 2007 9:49 PM

# re: Visual Studio user settings per project/solution
Requesting Gravatar...
I know someone that is working in MS, I asked him to try and push that on the VS team...
Anyway the solution proposed on the feedback by the VS team seems to working.
Left by Simone on Apr 23, 2007 11:59 PM

# re: Visual Studio user settings per project/solution
Requesting Gravatar...
Oh yes, I've been looking forward for this option for a long time already. Every day I have to switch between settings files, and I would love this feature.
May the Microsoft Gods have mercy on our sols :)
Left by Paul Vassu on Jan 28, 2008 2:28 PM

Your comment:
 (will show your gravatar)


Copyright © Scott Dorman | Powered by: GeeksWithBlogs.net | Join free