Share via

Important workaround for VS 2008 SDK July CTP for building VS Shell!

  • Article

Yesterday, we released the VS 2008 SDK that targets the Beta 2 release of Visual Studio. You can read all the details on our team blog. One of the most exciting things about this release is the ability for customers to build the VS Shell (isolated mode). Unfortunately, there is a last minute bug that we found that caused the location of the VS Shell wizard to change. When you open the New Project dialog, the VS Shell is supposed to be under the "Extensibility" node. Due to this bug, we were forced to make it appear under the "Visual C++" node.

 

So for this release of the VS SDK, you should look for the VS Shell template under "Visual C++" !

Comments

  • Anonymous
    August 01, 2007
    Yesterday, we released the VS 2008 SDK that targets the Beta 2 release of Visual Studio. You can read

  • Anonymous
    August 01, 2007
    Hi James, That is very funny bug! :)

  • Anonymous
    August 01, 2007
    I have watched the video interview on your team blog. Thats great - good way to tell us about the latest news! Thanks!

  • Anonymous
    August 02, 2007
    I can't create the project and I found another workaround here: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=290221 When successfully created a VS Shell project, there are some errors after I try to build it, the error messages are: Processing "VSShellStub3UI.vsct" into target "DebugVSShellStub3UI.cto" C:Program FilesMicrosoft Visual Studio 2008 SDKVisualStudioIntegrationCommonIncwbids.h(4,1): error VSCT1118: File not found: Unable to locate 'MsHtmCID.h' on the include paths provided C:Program FilesMicrosoft Visual Studio 2008 SDKVisualStudioIntegrationCommonIncAppIDCmdUsed.vsct(733,44): error VSCT1103: Undefined 'id' attribute 'icmdOpenLink' in a <UsedCommand> element C:Program FilesMicrosoft Visual Studio 2008 SDKVisualStudioIntegrationCommonIncAppIDCmdUsed.vsct(733,44): error VSCT1103: Undefined 'id' attribute 'icmdOpenLink' in a <UsedCommand> element ... Looking forward for more info of VS Shell, thanks.

  • Anonymous
    August 02, 2007
    Adrian.h, The Shell project has a depedency on the Windows SDK. This problem may be caused by the fact that you chose not to install the Win SDK when you were installing VS 2008. To fix this, run setup for VS 2008 again and install WinSDK. Let me know if that works for you. thanks, James

  • Anonymous
    August 02, 2007
    The comment has been removed

  • Anonymous
    August 02, 2007
    La semaine dernière, l'équipe VS a publié la Beta2 de VS 2008. Hier, la VSX Team sortait le premier CTP...

  • Anonymous
    August 04, 2007
    Hi Adrian.h, Please see my latest post (http://blogs.msdn.com/jameslau/archive/2007/08/03/building-vs-shell-with-vs-2008-sdk-july-ctp.aspx) on my blog about this issue. There is a bug in the default package that gets created and you can just remove the package to get away from getting this build error. thanks, James

  • Anonymous
    August 10, 2007
    The comment has been removed