Good evening,
I'm trying to run my first VSPackage by creating one through the VSIP
Wizard in 2005 Beta1. I followed all the steps in the help topic "How
to: Create a VSPackage Using the Visual Studio Integration Package
Wizard" and then ran the project. The help article mentions that I
should be able to test my menu command, tool window, and custom
editor. Neither of the three show up.
Is there something further that I need to do?
Here's what the end of the build output looks like before it launches
another instance of VS.Net (does this look like it did everything it's
supposed to do??)
Build complete -- 0 errors, 1 warnings
"C:\Program Files\VSIP 8.0\EnvSDK\tools\bin\x86\RegPkg"
/root:Software\Microsoft\VisualStudio\8.0Exp /codebase "C:\Documents
and Settings\Administrator\My Documents\Visual
Studio\Projects\VsPackage1\Debug\VsPackage1.dll"
Registering : VsPackage1 1.0.1710.40181
Registry Root : Software\Microsoft\VisualStudio\8.0Exp
------------------------------------------------------
Installed Product: VsPackage1, Version 1.0
Package: VsPackage1 {8a88b4b0-1505-4dbd-b2b6-f242443c0369}
Menu: 1000, 1
ToolWindow: Vsip.VsPackage1.MyToolWindow,
{85367281-1014-4dac-a33f-532650a92c15}
Editor Extension: .myext, {3c8c4f6d-1e5a-45d7-b96d-0f5096f21408}
LoadKey: Sissonix TestPackage
Version 1.0
Edition Required: Standard
SUCCEEDED: VsPackage1
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
"Ed Dore [MSFT]" - 08 Sep 2004 17:07 GMT
Hi Mark,
You need to run "devenv /rootsuffix Exp /setup" to merge the UI changes,
and then run "devenv /rootsuffix Exp".
Also, Allen Denver posted a resopnse back on 8/25 (which may have scrolled
off by now), about a known bug that won't merge the UI changes unless you
have selected a profile other than "General Development Settings". Just
reconfigure the IDE to use the "General Development Settings" profile, and
you should be good to go. This should be corrected by Beta2.
Sincerely,
Ed Dore [MSFT]
This post is 'AS IS' with no warranties, and confers no rights.