I'm using Resharper 8.0 together with Visual Studio 2013.
Now i like to add some own rules.
I read about the stylecopforresharper, but it seems this one is deprecated.
It is now integrated right into stylecop.
I did install stylecop 4.7, and it is added to my visual studio:
In the documentation, i read that the stylecop should also be present as a tool in resharper options, but it is not:
What do i have to do in order to get the stylecop integrated into resharper?
Edit:
Answer of citizenmatt is correct. I had the wrong version of Resharper. And it is even correctly documented on the stylecop website. Just my fault.
funny thing though, if i have the correct version of reharper installed, the stylecop setup shows me the supported resharper versions.
Without valid resharper version, there is no hint of which versions are supported.
StyleCop doesn't support ReSharper 8.0. But it does provide support for 8.1, which is a free minor upgrade to ReSharper 8.0. You can download it for free here - http://www.jetbrains.com/resharper/download/ (note that 8.2 is currently in beta - StyleCop doesn't support it yet, so stick with 8.1 for now!)
I also had trouble making VS 2013 compatible with StyleCop and ReSharper at the same time.
I am now able to make it work with the following configuration: VS2013 update 2, StyleCop 4.7.48 and Resharper 8.1.23.456.
Hope this helps.
Related
I have ReSharper 2016.2.2 installed onto Visual Studio "15" Preview 5.
When I use the new language features for C# 7.0 I get warnings that look like design-time errors, but my application compiles and runs fine.
I have also added this line to my Project's DotSettings file:
<s:String x:Key="/Default/CodeInspection/CSharpLanguageProject/LanguageLevel/#EntryValue">Experimental</s:String>
I had understood this to be the correct setting for C# 7.0 ?
I would like to know if there is a setting/configuration that allows ReSharper 2016.2.2 to work correctly with Visual Studio "15" Preview 5.
Install the latest EAP build for Resharper to get support for Visual Studio 15 Preview builds and C# 7 features.
Looks like I may be jumping the gun. The link here explains that C#7.0 support is still very much in the development stages and is not coming till version 2016.3 of ReSharper.
I was running Visual Studio 2013 with Resharper 8, and everything was fine and dandy untill I tried to install Jetbrain's Dottrace trial version. It brought with it something called Resharper Ultimate, which in turn made sure none of my Intellisense or Resharper features worked.
So I uninstalled Resharper Ultimate using the Windows uninstall feature. But Visual Studio seems to still consider it installed, because its options appears in the program's preferences dialog. Not to mention the top menu choice.
I have also tried installing Resharper 8 anew, in hopes that it will cleanse my machine of Ultimate, but it detects no previous installs. So now, I'm getting options dialogs for both Resharper and Resharper Ultimate. And none of the features work.
Plus I'm getting this error message when opening a solution with Resharper active:
I have looked at the mentioned XML file, but am not sure of what to make of it.
The solution from ReSharper Support Site:
To completely remove new .NET tools from Visual Studio, please try the
following:
Run ReSharper 9.x (new .NET Tools) installer once again - do you have
any products with status Repair? If so, please select Remove for them
and select Skip for others. If there are no items with Repair action,
please remove the following folder manually C:\Users{User
Name}\AppData\Local\Microsoft\VisualStudio{Visual Studio
version}\Extensions\JetBrains
I would try to clean the registry as per this article.
At the top of the blog post, there is a continuation of this story which describes fow to finalize the fix of the issue you experience by removing manifest and package definitions of your VS extensions.
Hope it helps
I have just installed VS 2013 RC2 and TypeScript refactoring stopped working. It disappeared from context menu, and pressing Ctrl+R, Ctrl+R gives the following error message:
The key combination (Ctrl+R, Ctrl+R) is bound to command (.Refactor.Rename) which is not currently available.
I have tried restarting VS, didn't help. Any ideas, workarounds?
Edit:
I have submitted a bug to Microsoft. Please upvote it if you have the same issue:
https://connect.microsoft.com/VisualStudio/feedback/details/860463/typescript-refactoring-stopped-working-in-vs-2013-rc2
Microsoft posted the following answer to my question on MS Connect. Seems that while refactor/rename was available in VS Express Edition with TypeScript 0.9, in TypeScript 1.0 it's only available from VS Pro upwards.
Posted by Microsoft on 19/05/2014 at 09:25
Thank you for reporting this issue.
Refactor/rename and NavigateTo are features that are found in the Pro+
versions of TypeScript in Visual Studio 2013. The Pro+ tools are aimed
at helping users work with larger codebases, so there is a focus on
building up tools to help support those codebases in those versions of
Visual Studio. We're working to continue to refine to make the
experience best across both Express and Pro+, with the right features
to help users who want to learn TypeScript and those who want to move
to using TypeScript in larger projects.
For me it happened because of resharper conflict. I uninstalled resharper and restarted visual studio
Does Resharper 6.1 support Visual Studio 2012? I have it working with VS2010 but wondering do I need to upgrade to ReSharper 7.0 for support in VS2012. It would be disappointing if I did.
JetBrains admitted that though Resharper 6.1 integrates well with VS 11, they have missed the installer. Here is a nice step-by-step explanation on how to get it to work with vs 11.
If you install VS2012 after installing VS2010+ReSharper, then the latter does NOT appear in VS2012.
I'm assuming -- I haven't tested this -- that even if you install R# after VS2012 it won't show up either simply because the R# installer does not offer the option to integrate into VS2012.
Therefore, I think R# 6.1 is incompatible with VS2012.
I've read articles that explain how to enable Visual Studio 2010 managed extensions to get them working with Microsoft Visual Studio 11 Developer Preview
Running VS2010 Gallery Extensions In VS11, Meet Git Source Control Provider
However I haven't been able to apply the same logic to Resharper. Although it's a managed extension now, it doesn't appear to be packaged in a VSIX file, so I can't follow all the steps in the above mentioned article.
No (For R#6.0)
Whilst I can't find an official looking page on JetBrain's resharper web site, I did find a reply from a JetBrain's engineer
The upcoming ReSharper 6.1 will have initial experimental support for Visual
Studio vNext.
http://devnet.jetbrains.net/message/5320971#5320971
Yes (For R#6.1)
Resharper 6.1 has now got experimental support for Visual Studio 11, albeit via a separate download to the normal 6.1 installer: http://www.jetbrains.com/resharper/download/index.html#related
Blog post explaining the current level of support in VS11: http://blogs.jetbrains.com/dotnet/2011/12/christmas-is-here-resharper-61-dotcover-12-and-dottrace-452-released/
Resharper 6.0 does not support VS11.
The nightly builds of Resharper 6.1 though are now available, and do support VS11.
To download Resharper for VS 11:
http://confluence.jetbrains.net/display/ReSharper/ReSharper+6.1+Nightly+Builds
To learn more about Resharper 6.1:
http://blogs.jetbrains.com/dotnet/2011/11/resharper-61-eap-opens-much-more-than-a-bugfix-release/
For details on how the experience with VS11 in general is like, compared to VS2010:
http://gurustop.net/blog/2011/11/10/notes-on-using-visual-studio-11-as-primary-ide-on-windows-7/
Update:
For notes on installing Resharper on VS 11, and small gotachas and solution, check this post as well:
http://gurustop.net/blog/2011/11/11/resharper-6-0-resharper-6-1-vs11-visual-studio-11-support-keyboard-shortcuts/
Update 2:
Since VS11 has been fully released as VS 2012, Resharper has released final version 6.1 (free for 6.0 owners), and 7.x for it already and they're working just nice. Wrote this update as the answer still gets up-votes (thank you).