DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Location of Your VSIX Files in Experimental HIVE during Visual Studio Plugin Development

Ricci Gian Maria user avatar by
Ricci Gian Maria
·
Aug. 27, 12 · Interview
Like (0)
Save
Tweet
Share
3.24K Views

Join the DZone community and get the full member experience.

Join For Free

when you are developing visual studio plugins, your project is usually configured to launch a special instance of visual studio under the visual studio debugger (excellent example of dogfooding), this special instance is called experimental hive.

image

figure 1: configuration of a standard vsix project to test your addin

as you can see the project is configured to start visual studio as external program to be debugged and it is started with the option /rootsuffix exp to start in experimental hive . this permits you to test your plugin in a configuration of visual studio that is isolated from your standard instance.  as an example, you might develop a plugin that makes visual studio unstable and you cannot open visual studio due to this addin.

if you want to remove or look at the current configuration of experimental hive you can go to this folder:

c:usersusernameappdatalocalmicrosoftvisualstudio

you should see all configuration folders for the various editions of visual studio.  those that end with exp are related to experimental hive.

image

figure 2: folders related to experimental hive.

you can now enter an experimental hive folder and in the extensions folder you should see all of your plugins that are under development.  now you can remove them if you want to restore everything to the original value.

alk.

Testing

Published at DZone with permission of Ricci Gian Maria, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • ChatGPT: The Unexpected API Test Automation Help
  • Efficiently Computing Permissions at Scale: Our Engineering Approach
  • A Simple Union Between .NET Core and Python
  • Building a Scalable Search Architecture

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: