locked
VSPackage: Compatibility of VSPackage created with VS SP1 SDK RRS feed

  • Question

  • Hi,

    I'm developing a VSPackage and I was wondering whether VSPackages created using Visual Studio 2010 SP1 SDK (http://www.microsoft.com/download/en/details.aspx?id=21835) are compatible with VS 2010 RTM?

    I stumbled upon a case where my VSPackage compiled with VS SP1 SDK does not work on VS 2010 RTM.
     - On Dev machine: The VSPackage works correctly when installed on VS 2010 SP1
     - On Test machine: with VS 2010 RTM - “Exception has been thrown by the target of an invocation.” message box is displayed when I try to open my ToolWindow.

    More details:
    Dev machine:
     - OS: Win7 x64
     - VS 2010 SP1 (10.0.40219.1 SP1Rel)
     - VS SP1 SDK
    Test machine:
     - OS: Win7 x64
     - VS 2010 RTM (10.3.30319.1 RTMRel)


    If I'm targeting VS 2010 RTM and VS 2010 SP1, should I use the VS RTM SDK or it's possible to use the VS SP1 SDK?

    Thanks


    • Edited by Nik Z Wednesday, December 21, 2011 11:31 AM
    • Changed type Nik Z Thursday, December 22, 2011 1:29 PM
    • Changed type Ryan MoldenMicrosoft employee Thursday, December 22, 2011 3:53 PM This was a question not a 'general discussion'
    Wednesday, December 21, 2011 11:02 AM

Answers

  • Turns out one of the referenced projects was with "Delay Signing". Interestingly the validation only fails under VS 2010 RTM.

    The moral of the story is: Be careful when using "Delay Signing"

    References:
     - http://msdn.microsoft.com/en-us/library/t07a3dye.aspx
     - http://www.c-sharpcorner.com/UploadFile/vandita/delaysignassemblies08022006120501PM/delaysignassemblies.aspx 

    Thursday, December 22, 2011 1:28 PM

All replies

  • My understanding is VS2010 SDK SP1 should work for VS2010 SP1 only and VS2010 SDK should works for RTM, may SP1. What I think is SP1 includes all the feature of the RTM.

    Generally, always target SP1 with SP1' SDK and target RTM with RTM SDK, this will save our lots time to figure out such compatible issue.

    Wednesday, December 21, 2011 3:24 PM
  • That should only happen if you ended up taking dependencies on functionality that is only in SP1. I am not aware of any such functionality added to the extensibility libraries in SP1, but it may have happened.  Do you have a repro of a project that when compiled with RTM vs SP1 stops working?

    Ryan

    Wednesday, December 21, 2011 7:23 PM
  • Hi,

    I have kind of a break-through on the problem. I attached windbg to VS and tracked the exception. The xaml file that I use in my tool window uses a 3rd party component. The exception that is thrown is System.Windows.Markup.XamlParseException (Could not load file or assembly '<fully qualified assembly name here>' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)).

    I'm still trying to find a solution for this problem, and why it only happens in VS RTM.

    Thursday, December 22, 2011 9:35 AM
  • Turns out one of the referenced projects was with "Delay Signing". Interestingly the validation only fails under VS 2010 RTM.

    The moral of the story is: Be careful when using "Delay Signing"

    References:
     - http://msdn.microsoft.com/en-us/library/t07a3dye.aspx
     - http://www.c-sharpcorner.com/UploadFile/vandita/delaysignassemblies08022006120501PM/delaysignassemblies.aspx 

    Thursday, December 22, 2011 1:28 PM