Design DLL references Microsoft.Windows.Design.Extensibility.dll for VS2010, but what about VS2012? RRS feed

  • Question

  • Hi, our control DLL is packaged in an assembly X.dll and we also provide the designer assembly X.design.dll (which actually just says which controls are toolbox items).

    X.design.dll has to reference Microsoft.Windows.Design.Extensibility.dll

    Now, the problem is, VS2010 uses Microsoft.Windows.Design.Extensibility v4.0 and VS2012 uses v4.1

    How should we package this for our users?

    My thoughts;

    A. we cannot put X.design.DLL for 2012 and 2010 in the same folder, because AFAIK there's a naming convention, it must be named X.design.dll

    B. we could have separate folders, one for 2010 and one for 2012, with the same copy of X.dll but different X.design.dll.  That would in theory work, but it's not that nice (the duplication) and could confuse users.  Plus, we'd have to do one for 2013 soon enough...

    C. some way to redirect from 4.0 to 4.1?  A policy won't do it because it has to be written my MS.

    Are there any official guidelines for this by any chance?



    Thursday, July 25, 2013 7:17 PM