Developer Support Blog for Visual Studio Extensibility - All Comments

re: How to register existing packages to run under VS 2010 Experimental Instance

Francine — Thu, 12 Jan 2012 15:37:36 GMT

Thanks for this blog entry.

If your package assembly has references, do they need to be added to this project in a special way?

I followed the steps above for my VS2005 extension package that I want to debug in the VS2010 experimental hive. When I build at the end, I run into an error saying: "Could not load file or assembly 'file:<path to my DeployToVS2010Exp project>\bin\Debug\DeployToVS2010Exp.dll' or one of its dependencies. The system cannot find the file specified." (And there is no information in the File and Line columns of the error list. I can't use Fusion Log Viewer to get an information either since it is not a load error...)

Obviously it won't find that DLL since that is the one I am specifically building. So I assume it is complaining about my VS2005Package.dll that I added to the project. The file properties are correct, so maybe it is the dependencies of that file that are missing. I added the 5 DLLs that I know it references to the project references, but that didn't help. Maybe I needed to add it to the reference section of the vsixmanifest, but non of the drop-down choices looked reasonable.

Any thoughts?

re: How to register existing packages to run under VS 2010 Experimental Instance

Ed Dore — Wed, 05 Oct 2011 22:16:30 GMT

Hi Vic,

User2 will not see the package, as each user has their own experimental instance courtesy of the Visual Studio SDK. If you want all users to see/use the package, you'll want to actually redist/deploy your package via .VSIX, with the <AllUsers> element in your .vsixmanifest set to TRUE.

re: How to register existing packages to run under VS 2010 Experimental Instance

Vic Vega — Tue, 13 Sep 2011 06:49:07 GMT

Hi Ed Dore,

Thanks for blog. Think User1 builds and registers the package (I assume it goes to HKCU). Now another user (User2) logs into the machine. Will he able to use package registered by user1.

Regards

Vic

re: How to localize a managed VS Package

phoenix26984 — Fri, 27 Nov 2009 19:04:24 GMT

Is there a solution or a work around for the known bug with the Visual Studio "Isolated Shell" installation that prevents the installation of localized resources ? Where can I find more info on this?

re: How to localize a managed VS Package

sorporbear — Mon, 08 Jun 2009 23:53:04 GMT

This is good info. Can you shed some lights on how to localize the UI of a custom project template wizard (a class implementing Microsoft.VisualStudio.TemplateWizard.IWizard)? I can't find much info on MSDN except I have to create a separate .vstemplate file in the corresponding lcid folder under Visual Studio install but that doesn't cover how resources get loaded from the custom wizard implemented in .NET.

How to push F1 context keywords for property pages in the project designer? | ASP NET Hosting

Tue, 02 Jun 2009 02:14:53 GMT

PingBack from http://asp-net-hosting.simplynetdev.com/how-to-push-f1-context-keywords-for-property-pages-in-the-project-designer/

How to localize a managed VS Package | ASP NET Hosting

How to localize a managed VS Package | ASP NET Hosting — Tue, 26 May 2009 23:13:31 GMT

PingBack from http://asp-net-hosting.simplynetdev.com/how-to-localize-a-managed-vs-package/