...
- Use the Clear MEF Component Cache extension that will automatically clear the MEF cache (download here).
- Manually delete the cache directory. Depending on your installation details, the cache directory may be available in the following locations:
- If the Plugin has been installed with the default options: %localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
- If the Visual Studio registry suffix has been specified with the<SUFFIX>
parameter during installation: %localappdata%\Microsoft\VisualStudio\14.0<suffix_name>\ComponentModelCache
Why does dotTEST not report results for some rules and metrics when integrated with Visual Studio 2013?
Some static analysis rules and metrics require Visual Studio Update 5 to be installed on your machine if you run analysis with dotTEST from Visual Studio 2013. You may need to install Visual Studio Update 5, or run analysis from the command line.
How can I prevent my machine ID from floating?
...
- Set up the PARASOFT_SUPPORT_NET_INTERFACES environment variable.
Set the variable value to a stable Ethernet network interface. Do not use virtual, temporary or loopback interfaces.
- On Windows: Set the value to the MAC address of your network card. You can use theipconfig -all
command to obtain the address. For example:
- On Linux: Set the value to one of the network interfaces from the "inet" or "inet6" family. You can use theCode Block SET PARASOFT_SUPPORT_NET_INTERFACES=00-10-D9-27-AC-85
ifconfig
command to obtain the list of available interfaces. For example:Code Block export PARASOFT_SUPPORT_NET_INTERFACES=eth1
If the problem persists, you can obtain diagnostic information by setting up the environment variable PARASOFT_DEBUG_NET_INTERFACES and setting its value to true. This will print to the standard output the checking procedure that can be shared with technical support, as well as the interface that is used to compute your machine ID. The interface will be marked with the [SELECTED] prefix.