I was setting up a new system recently, and when I installed Visual Assist X (my favorite development utility), I experienced a package load failure when starting VS.NET 2003. After a few emails with their support staff, we figured out the problem: I had installed VSIP prior to running their installer, and the VSIP installation sets a global environment variable called ENVSDK_REGKEY, which fooled them into installing their package into the experimental hive instead of my normal development environment. My workaround was to invoke their installer from a command prompt where I had removed that environment variable.
Although I have not had the time to test this, I would think that this could be a problem with any VS.NET package installation.
Post a Comment