As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
Is there a list of all the source control systems that have visual studio plugins? If not, we can make one here...
Subversion
AnkhSVN
VisualSVN
Git
Git Extensions
Git Source Control Provider
Team Foundation Server
Visual Source Safe
CVS
IBM Rational ClearCase
Plastic SCM
Mercurial
VisualHG
Visual SVN with Tortoise and ankhsvn plugin works like a charm. Very easy to install and administrate.
There's also Git Source Control Provider for Visual Studio:
http://gitscc.codeplex.com/
This one actually works with VS2010 for me. Git Extensions does not.
AccuRev's Microsoft Visual Studio Plug-in
Team Foundation Server
IBM Rational ClearCase
SourceGear's Vault has a Visual Studio plugin. Some of Vault's great features are:
free for single users
SQL Server backend
atomic checkins / changesets
Screenshots of Vault
IBM Rational Team Concert
This client integration supports Jazz Source Control, Work Items and Build Engine.
Visual SourceSafe
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
What is the Best/Worst features of Visual Studio 2010 you like/dislike most, comparing to VS 2008?
Worst feature? Only one built-in color theme which does not allow for customization. Not everyone is crazy about blue, you know.
I'd say that without question, the best feature is the whole add-in support and ecosystem (with built-in browser).
It's the first time that Visual Studio can actually compete with Eclipse - at least in my opinion :)
Worst thing: the removal of .dbp Database projects. Almost as bad as when they removed ETP projects in Visual Studio 2005.
I hate it when they remove things that were working perfectly well. In this case the replacement has a learning curve, appears to be SQL Server only, and doesn't have some of the convenient features of dbp projects such as right-click / Run On.
ETP projects in .NET 1.x were great as containers to contain groups of projects and/or files such as documentation or third party dlls, which could then be all added to a solution in one step.
well, I'll answer with what is a regression to me, unless I've missed it in which case please point me to the solution.
When using VS2008 with TFS, to add an existing project from the source explorer to a solution, you could simply double click the project file, that was nice. Now if you double click a project file, it opens a new solution with just that projet. That means if you want to create a new solution and add multiple existing project, you'd have to go through those steps :
Right click solution
Add existing project
Browse
Navigate to the project file
Select it
Click OK
Repeat
Worst feature: It's not vim
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am using c# express and would like to use a free version control system. Please share your recommendations.
Visual Studio Express is crippled in the sense that it cant load any plugins or addons.
Just go with TortoiseSVN. Works easy enough.
It seems to me you are new to Version Control. If you haven't used source control before, I recommend looking at a distributed version control system (DVCS) directly. My choice was Mercurial, because it has excellent documentation, a clean and consistent interface, works well on all major platforms (using it on Windows, Linux and MacOSX) and a great support for PlugIns (several are officially redistributed, such as mq) that let you do very advanced stuff. There are great GUIs available (TortoiseHG, but also standalone). There is a nice introduction to Mercurial here, but the it's also useful for the general conept.
Popular DVCS include: Mercurial, Git and Bazaar but in the end it doesn't matter which tool you choose There is lots of information here on SO about comparisons.
The best IDE PlugIn is don't use one. I think IDE integration is not necessary when working with a DVCS. When working in a centralized system, it is reasonable for the purpose of automatic check out on edit, rename support etc.. However, I like keeping things seperate. I don't want my IDE cluttered up. I don't see any benefits in using a plugin compared to a standalone solution (that I keep running on a second monitor). To support renaming, a good DVCS has built in heuristics to find and track renames automatically.
I am fine with TortoiseHG and the command line for more complicated tasks.
Don't use your IDE for version control. Get to know your version control system itself. Which one you should use depends on your requirements. My personal favourite at the moment is Mercurial.
Subversion along with AnkhSVN plugin for VStudio and TortoiseSVN plugin for the windows explorer.
It tracks folders as well as files and keeps history on renames. Those are really useful for refactoring your code.
Edit: forget about AnkhSVn in VisualStudio Express because it can't load plugins.
Personally, I hate the tortoise type clients, mainly because Explorer frustrates the hell out of me and isn't a good file-system browser at all..
I choose an unorthodox approach and install NetBeans and use the "favorites" tab to add locations for versioned file systems I wish to manage.
I use this approach for Visual Stuido.
My prior tool was WinCVS.
Since 2012 you can use TFS (Team Foundation Studio) 2012 Express with Visual Studio 2012 Express editions for free.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Has anyone found a plugin for Visual Studio to allow for PowerShell syntax highlighting or IntelliSense? If not, does anyone have any idea why not? I keep hoping someone else with copious free time would have tackled this by now. I have hope since other folks have managed to take the limited documentation and build custom IntelliSense providers for other languages such as NHaml.
Edit: To clarify,I'm not looking for a list of IDEs that can be used to develop PowerShell . I spend 90% of my day in Visual Studio. It already does a really good job of slicing and dicing code. That is the IDE I prefer to use to edit all text and code. The lack of PowerShell syntax highlighting now that I work with PowerShell scripts is down right painful.
Update 2013-08-20
Adam Driscoll has recently announced the PowerShell Tools for Visual Studio as successor of his former PowerGUI Visual Studio Extension - see his blog post about The Future of PowerGUI VSX for details, where he acknowledges the drawbacks of the predecessor outlined by Simon Gillbee (see previous update below) and describes how they will be addressed by removing the dependency on PowerGUI:
[...] By embedding the PowerGUI editor directly in Visual Studio it caused a multitude of problems because it really wasn’t a true language integration but more like a hack.
[...] PowerGUI VSX v2 will offer
true Visual Studio language support for PowerShell. It uses the Visual
Studio editor and the raw PowerShell debugger, tokenizer and
completion engine. Currently, the requirement is PowerShell v3 and
Visual Studio 2012. This requirement may change depending on community
support and adoption. [emphasis mine]
Update 2013-07-31
Simon Gillbee has just referenced/promoted a PowerShell syntax highlighting alternative, that doesn't expose the drawbacks of the PowerGUI Visual Studio Extension he previously summarized:
TextHighlighterExtension2012 (Visual Studio 2012)
TextHighlighterExtension (Visual Studio 2010)
Initial Answer
The recently released PowerGUI Visual Studio Extension adds PowerShell IntelliSense support to Visual Studio. While it depends on the (free) PowerGUI graphical user interface and script editor, reusing this editor component should be a sign of maturity rather than an impediment I'd hope. (See Kirk Munros PowerShell support in Visual Studio! blog post for an introduction.)
Being a 1.0 there are still some minor issues with the extension as such, but Adam Driscoll seems to be pretty active tackling these - the PowerShell syntax highlighting and IntelliSense support is working most excellent for me already!
Here's a useful one: PowerGUI VS Extension.
I have not seen anything about Visual Studio Intellisense for PowerShell scripts.
I recommend you to try some other tools like:
PowerTab
PowerGUI
Look this screen cast:
(source: aaronlerch.com)
The PowerConsole extension for VS2010 is very nice and looks promising. I am not sure though that it is suitable (or able) to edit scripts. It is worth to try in any case.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I currently use AnkhSVN to integrate subversion into Visual Studio. Is there any reason I should switch to VisualSVN?
AnkhSVN is free (in more than one sense of the word) while VisualSVN costs $50. So right there unless I'm missing some great feature of VisualSVN I don't see any reason to switch.
I used VisualSVN until Ankh hit 2.0, and ever since, I've abandoned VisualSVN. Ankh has surpassed VisualSVN in functionality, in my mind, and all the 1.x perf and integration issues are gone.
I recently tried Ankh but quickly switched back to VisualSVN. Because:
Better commit dialog (use UI of tortoise)
No refresh problems (which i had using ankh)
Imho visual svn is easilty worth its money
For me, VisualSVN is pretty, but useless. AnkhSvn on the other hand, after it came in v2 as an scc provider, it works very good.
VisualSVN tries to think for you, which is not an good thing, the user should be the controller, not the software.
The main thing is that VisualSVN uses TortoiseSVN for nearly all of its UI. So you only really have to set up one client (preferred diff viewer, etc), and you can take advantage of things like the same "Previous messages" button on the Commit dialog, whether you're committing from Explorer or Visual Studio.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I support a third party system that uses COM, classic ASP, and SQL Server. Our company has gone to using TFS as our source control provider - which pushes things through Visual Studio. So, what's the best way to get a classic asp front-end into Visual Studio?
When I had to do this, I created a blank solution in VS and then added the folders from the ASP site one at a time, adding "existing items" to each folder as I created it.
In this way I'm able to open the solution which keeps track of what files I had open at last open, plus I get the benefits of intellisense
I have done this frequently over the last 5 years...
You could create an Empty Website, or even create a standard (.NET) website and simply delete the default stuff it generates (web.config etc). Note: create a website, creates a solution and adds a website project within it, which is arguably slightly more preferable than simply adding files and folders to solution.
As Geoff says, you get most of the benefits of VS including intellisense.
Suck it and see... Have a fiddle - you are not going to break anything!
Did any of you heard of Visual Web developer 2008 Express edition?
Work wonders for me.
Most important as soon as you ask to open website in it- it opens each folder of intended website and when you save project it does what you need to do to later open this website in regular visual studio.
It have some limited capability even to convert simple Classic ASP pages into NET code!
Create a blank solution in VS and add all the files by choosing "Add Existing Item.."