How to build MPFProj10 samples with VS 2012+ and VSSDK.* NuGet packages?
Opened this issue · 2 comments
I've spent the last 2 weeks day and night to figure this out, but zero result.
Could you please help or point to some working sample?
I've tried the original MPFProj10 with VS 2012 + SDK and VS 2013 + SDK, the original MPFProj11 with VS 2013 + SDK, your MPFProj10 fork with VS 2012, but I've never ever get the sample CustomProject-s in them to work. VS installs are fresh new Professional installs.
Simply adding VSSDK.Shell.10 to the original MPFProj10 sample CustomProject under VS 2012 doesn't work: errors, I have to add several other VSSDK packages, manually edit the "Embed Interop Types" and other properties, manually set the specific versions to get it build, at least with warnings. And VS always finds a way to reference an SDK dll or a GAC dll, even if the HintPath points to the NuGet packages folder. There is no way to get VS to reference only the dll-s under the NuGet packages folder.
I've tried this with MPFProj11 + VS 2013 + SDK, I've got it to build with the same manual editing, it works under VS 2013, but it references VS 2013 dll-s, and it crashes under VS 2012 when I install the .vsix built under VS 2013.
I've tried your MPFProj10 fork with VS 2012, it references a nonexistent Microsoft.VisualStudio.Project.csproj file, I've tried to modify it to the specific ...11.0.csproj, or ProjectBase.Files or install Microsoft.VisualStudio.Project NuGet package and add VSSDK.Shell.10, but still errors, errors, errors, hundreds of errors...
I've never experienced in my life such an impossible problem. I would like to create a vsix extension that targets VS 2010+ and can be built with any VS 2010+, and the binaries built with any VS 2010+ will work under any VS 2010+.
I totally hear you on this. 😞 I've been working to get the sample code running well enough to write tests for all the recently reported issues, and it hasn't been easy. I'll try to get my working branch pushed so you can review the changes and let me know if it improves the situation (would just me a start, but have to start somewhere).
Oh, I've thought mpfprojXX and vsxdeps are already compatible. :) I'm sure, my knowledge about .Net/VS .dll reference resolution is not even comparable to yours, but I'm happy to contribute at least with testing! Fresh new VS 10, 11, 12, 14 + SDK VBox VM-s are ready. :)