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've seen ReSharper recommended a lot Unfortunately, it doesn't support C++ in Visual Studio. Is there anything out there you can recommend? I already use Visual Assist, and it does its job very well, but it's quite limited in comparison with ReSharper.
Any suggestions?
IMHO - Visual Assist X is best but expensive code completion/refactoring tool for C++.
VAX has not so much features as ReSharper for C#, but it makes your C++ programming easier and faster... Just looked on CodeRush - it su%% as most of DevExpress libs & tools.
Refactor Pro is available for Visual C++, this will give you some functionality. Also check out CodeRush, I think it also supports C++.
I tried both Refactor Pro and Visual Assist/X. Neither of them thrilled me in the same way that ReSharper does. I guess that mostly, this is because C++ is such a hard language to write automatic refactorings for.
The solution is to code in Eclipse or NetBeans, but such IDEs are not Visual Studio.
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 11 years ago.
Would you consider it a reasonable idea to implement a Visual Studio 2010 add-in in C++ because it's the language you know best/that's normally used in-house/that gives you the full power to do even rare things? Today C++ seems quite unpopular in this area.
AFAICT writing Visual Studio add-ins in C++ means dealing with COM, at that is cumbersome in C++. I, for one, would avoid writing add-ins in C++ for this reason alone.
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'm after a Any free documentation tool for Visual Stusio 2010?
Any good ones with sample demo?
Cheers
You can take a look at sandcastle for generating documentation.
Atomineer Utils
Visual Assist X
Both have 30-day free trials, neither work for Express Editions, after the free trial ends, the cost is minimal (VAX is 40 for students)
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 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.