ReSharper does not work when FIPS enabled
This is a known issue here: https://youtrack.jetbrains.com/issue/RSRP-428664
Suggested workaround:
- update <program>.exe.config with:
<configuration>
<runtime>
<enforceFIPSPolicy enabled="false"/>
</runtime>
</configuration>
For VS 2017 the path is "C:\Program Files (x86)\Microsoft Visual Studio\2017\{Edition}\Common7\IDE\devenv.exe.config"
For previous VS versions - "C:\Program Files (x86)\Microsoft Visual Studio {VS version}\Common7\IDE\devenv.exe.config"
Starting with ReSharper 2018.3, it will not be necessary to update the <program>.exe.config for license activation.
Please sign in to leave a comment.
Where is this file located?
As we are talking about Visual Studio executable file, so you may find a related config file next to devenv.exe here "C:\Program Files (x86)\Microsoft Visual Studio {VS version}\Common7\IDE\" directory
For Visual Studio 2017 the path is
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe.config
You may need to return and update this file with the setting mentioned above after each Visual Studio Update (I had to each time when going from 15.4.2 -> 15.4.3 -> 15.4.4)
I wanted to add here, that while this fix solved part of my licensing issue, I did need to take another action.
The issue I had was with Resharper, dotTrace, dotCover, and dotMemory.... Each license summary showed 'No valid license found' even though I was logged in via my JB account. None accepted my activation code either.
Applying the suggested workaround from this page DID allow me to active and use Resharper. It did NOT allow me to use dotTrace, dotCover, or dotMemory. To get those to work, I disabled FIPS system-wide via the Group Policy editor:
https://www.howtogeek.com/245859/why-you-shouldnt-enable-fips-compliant-encryption-on-windows/
The group policy edit may not pertain to those who can not access or affect change in their GP editor. The top part of the article does give instructions on 'enabling' FIPS for a single network connection, and one could follow that to instead DISABLE FIPS for one connection. (In step 8, UNCHECK “Enable Federal Information Processing Standards (FIPS) compliance for this network” under 802.11 settings).