DCSIMG
Experimental Instance of VS 2010 – Safe And Easy Debugging - Oshry Horn

Oshry Horn

Experimental Instance of VS 2010 – Safe And Easy Debugging

When you develop a Visual Studio package or add-in you want to be able to run and debug it without having to pollute your environment with untested and\or unfinished applications and components.
This is where the Experimental Instance of Visual Studio 2010 shines. When using this method to debug, what will happen is the following:

  1. A new instance of visual studio will be opened when in the window title bar will written “Start Page – Microsoft Visual Studio (Administrator) - Experimental Instance”.
  2. If the developed app is actually a Visual Studio Package (Visual Studio SDK) the new instance will be loaded as if you have installed your Package already:

image
(New Project window - Visual Studio Package)

If you wish to see how is it done (even though its automatically set) go to the properties of you project and see in the VSIX tab that the checkbox “Deploy VSIX content to experimental instance for debugging” is checked:

image
(Visual Studio Package Project’s properties window)

If the developed app is not a Visual Studio Package it is still possible to use the “Experimental Instance”, but the “face” install will have to be implemented manually (copy dll’s to specific location or whatever).

To use the “Visual Studio Experimental Instance” all you have to do is to do the following:

  1. Go to the project’s properties window.
  2. Go to the “Debug” tab.
  3. In the “Start Action” section, select the “Start external program” radio button. And select your local visual studio executable (devenv.exe), such as: “C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe”.
  4. In the “Start Options” section, write in the “Command line arguments” textbox “/RootSuffix Exp”.

image
(Visual Studio Project’s properties window)


Now that we have Visual Studio Experimental Instance and we know how to use it, we should use it when needed to make our lives easier, and help us see what we’re doing!

Comments

Oshry Horn said:

My friend Assaf Stone have seen my method of debugging Custom Work Item Controls and demanded that I

# March 10, 2011 10:46 AM

Strong name verification issues when creating a customized build of the CKS.Dev solution « Second Life of a Hungarian SharePoint Geek said:

Pingback from  Strong name verification issues when creating a customized build of the CKS.Dev solution « Second Life of a Hungarian SharePoint Geek

# September 22, 2011 12:44 AM

Nigel said:

This is great - but then how do I get my Addin to load in the experimental version.  I tried adding a folder key to

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0Exp_Config\AutomationOptions\LookInFolders

but when I debug from the normal VS something deletes my new key so it never loads :(

# October 19, 2011 9:07 PM

How to get an addin to load in Visual Studio Experimental said:

Pingback from  How to get an addin to load in Visual Studio Experimental

# October 19, 2011 11:29 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Enter the numbers above: