From here on, they will be collectively described as “ReSharper”, but the information equally applies to dotCover, dotMemory and dotTrace. net tools that integrate with Visual Studio. The information in this article relates to all. This allows for ReSharper (dotTrace, et al) to not be loaded in experimental instances, should the need arise. net tools, has support to move its registration from per-machine to per-user, and per-experimental instance. The Platform layer that provides Visual Studio integration to ReSharper and the other. This means that they are available to all users on the machine, but also that they are loaded in all experimental instances. net tools, dotCover, dotMemory, dotTrace, etc.) are installed as per-machine Visual Studio extensions. “Experimental instances” were previously known as “custom hives”īy default, ReSharper (and the other. Each experimental instance can have an entirely different configuration, from theme and window layout to the extensions that are loaded. Visual Studio’s “Experimental Instance” feature is intended for developing and debugging Visual Studio extensions, and maintains a separate copy of the configuration needed to run Visual Studio. This topic relates to ReSharper 8, and has not been updated to ReSharper 9 or the ReSharper Platform. Running ReSharper in Visual Studio Experimental Instance
0 kommentar(er)
