This article applies to Visual Studio 2015. If you're looking for Visual Studio 2017 documentation, use the version selector at the top left. We recommend upgrading to Visual Studio 2017. Download it here.
Use the CreateExpInstance utility to create, reset, or delete an experimental instance of Visual Studio. You can use the experimental instance to debug and test Visual Studio extensions without changing the underlying product.
CreateExpInstance.exe [/Create | /Reset | /Clean] /VSInstance=VsInstance /RootSuffix=Suffix
Creates the experimental instance.
Deletes the experimental instance, and then creates a new one.
Deletes the experimental instance.
The name of the directory that contains the base Visual Studio instance to copy.
The suffix to append to the name of the experimental instance directory.
When you are working on a Visual Studio extension, you can press F5 to open the default experimental instance and install the current extension. If no experimental instance is available, Visual Studio creates one that has the default settings.
The default location of the experimental instance depends on the Visual Studio version number. For example, for Visual Studio 2015, the location is %localappdata%\Microsoft\VisualStudio\14.0Exp\ All the files in the directory location are considered part of that instance. Any additional experimental instances will not be loaded by Visual Studio unless the directory name is changed to the default location.
Visual Studio does not access the system registry when it opens the experimental instance. This differs from earlier versions of Visual Studio, which used an experimental version of the registry hive.
The CreateExpInstance utility replaces the VsRegEx utility.
The following example resets the default experimental instance of Visual Studio.
CreateExpInstance.exe /Reset /VSInstance=14.0 /RootSuffix=Exp