I've been using Resharper (v8.0.14.856) with VS2012 for some time now, but I've recently installed VS2013. However, Resharper does not appear in the menus for VS2013, or in the options (under Tools->Options).
I've re-run the installer, and selected VS2013. As far as the
installer is concerned, it is installed for VS 2013.
I've tried repairing the install.
I've tried deleting the
%AppData%Roaming\JetBrains folder (as suggested elsewhere).
I've read this:
http://resharper-support.jetbrains.com/entries/21204867-ReSharper-is-not-available-in-Visual-Studio-after-installation and I've tried running Visual Studio with /resetskippkgs command line
key.
I am an administrator, so I've run the installer as administrator, and I run VS2013 as administrator.
I've tried running in Compatibility mode for Windows 7
I've also tried contacting JetBrains, but have yet to receive a reply
Note. I don't have an "\Common7\IDE\Extensions" folder, but I don't have one for my VS2012 install either, and Resharper works just fine there.
Does anyone have any other suggestions?
You need 8.1 to work with VS2013.
http://blog.jetbrains.com/dotnet/2013/11/04/visual-studio-2013-support-resharper-81/
This is also marked with a small "8.1" image on this page:
http://www.jetbrains.com/resharper/whatsnew/
Cheers
I had the same issue. I Googled around and found a blog post explaining how to add a previously installed Resharper to various newly installed versions of Visual Studio on your machine via the Windows Control Panel.
The article outlines these steps...
Go to 'Control Panel' and select 'Programs and Features'.
Select 'JetBrains ReSharper' and click on 'Change'.
The ReSharper Setup main dialog will appear, here click on 'Change'.
The ReSharper Setup integration options dialog will appear, check the Visual Studio version that that you wish to enable ReSharper in. Click 'Install'.
Here is the original blog post...
http://fitgeekgirl.com/2014/02/25/enabling-already-installed-resharper-for-newly-installed-visual-studio/
Related
I'm a new to SSIS development and I'm using a 64-bit computer on Windows 7. I wanted to change a script task, but when clicking on the 'Edit Script' button nothing happens.
Here is the ScriptLanguage searched:
I tried a new installation VS2012 and SSDT_BI2012, as suggested on different forums, but that doesn't fixed my issue.
If anyone had the same issue can you guide me to the resolution?
If you need additional information please let me know.
Thank you
I had the same problem. Here is what I did to fix this issue:
Go to the control panel and locate the instance of Visual Studio Tools for Applications (VSTA).
In your case you should look for something like "Microsoft Visual Studio Tools for Applications 2012"
Right click on the VSTA component and select "Change"
In the next popup click "Repair"
In my case the problem was with Microsoft Visual Studio Tools for Applications 2017:
Once I repaired this VSTA installation everything worked correctly.
I had the same problem. I tried to repair the Visual Studio with the installation, but it didn't work.
After, the solution that worked for me:
Install the SSDT in a new instance of Visual studio.
Since some days the feature files are broken.
VS2017:
Colors dissapeard, everything is white.
When I press F12 nothing happens.
When I run the test from solution explorer the tests work fine.
VS2015:
Everything works fine.
What I tried to do:
Option 1: Run Binding Tool
Right-click on the feature file
Select "Run Custom Tool"
This causes the SpecFlowSingleFileGenerator to regenerate the code-behind for your test framework.
Option 2: Restart Visual Studio
Close Visual Studio
Open Visual Studio
Reopen solution
This causes any bindings that haven't been cached to rerun.
Option 3: Clear SpecFlow Step Mapping Cache
Close Visual Studio
Open Windows Explorer
Type %TEMP% in Address Bar and hit Enter
Search for "specflow-stepmap-*.cache"
Delete those files
Open Visual Studio
Reopen solution
Option4: Uninstall and reinstall visual studio 2017
None of them fixes the issues for VS2017.
Some help is more than welcome.
I solved this issue by updating VS2017 to v15.6.1. Prior to that I've tried all the steps you mentioned and it did not work.
Also, found this article: https://github.com/techtalk/SpecFlow/issues/1049 which is saying the same.
These symptoms sound like you haven't installed Specflow extension on your VisualStudio 2017.
What happens when you dont have it is that VS can't work with feature files and can't navigate to anything when pressing F12.
Tests are working because VisualStudio executes already generated NUnit tests from feature.cs files.
Double check your VisualStudio Tools -> Extensions And Updates -> Check in Installed if you have Specflow for Visual Studio 2017 installed and Enabled.
Note: Each time you install a new Visual Studio you have to install the extension.
Came across the same issue, installed Specflow for Visual Studio 2017 from Tools >> Extensions And Updates and found as working fine.
Go the colours for feature file lines back and F12 is working fine.
Thanks.
I have Visual Studio 2013 which included "PreEmptive Dotfuscator and Analytics".
It's always worked fine for me until recently.
Suddenly it will not open from Visual Studio, icon or commandline.
Even when I manually open it, it does not show up in the task manager.
It simply does nothing.
There's nothing in the Event Viewer logs.
Visual Studio shows no error.
Basically, I can't even begin to find the problem.
I tried to find a download to attempt to reinstall it but all I've seen on the website for this version is that it's included in VS2013.
There's other sites in search results which claim to have the installer but none I trust.
Has anyone had this issue in the past?
It's Visual Studio 2013 Professional on Windows 8.1.
I'm not sure how to address this so I would greatly appreciate any possible input.
Thanks in advance!
You can try uninstalling, wiping the settings, and reinstalling. Dotfuscator Community Edition is uninstallable via the Windows control panel. Once uninstalled, delete %LOCALAPPDATA%\PreEmptive Solutions. You may be able to reinstall it as a component via the Visual Studio installer. If not, it is actually a standalone installer, so if you have a Visual Studio disc or .iso, it will be in \packages\Dotfuscator.
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 think I may have accidently disabled stylecop in my Visual Studio 2008 enviroment. If I right click a project and click "Run Stylecop", or "Stylecop Settings" nothing happens. Its the same from the Tools menu. It runs fine from Visual Studio 2005. I have Microsoft StyleCop 4.3.3.0. I was playing about with making custom rules and may have clicked Yes on a random box that popped up when there was a problem with a custom rule dll that I created, so I think this may have disabled Stylecop in my VS 2008 enviroment.
Does anyone know how to get this re-enabled? I have re-installed stylecop but to no avail.
Thanks
Neil
Problem solved, run devenv /resetskippkgs (not from cmd though, has to be via windows interface)