VSSDK in paket.dependencies

[smoothdeveloper]

attempt (almost complete!) to solve #1425

• make projects to compile against VS SDK nuget packages
• cleanup duplicate references in different groups (such as FAKE)
• reorganize all paket files contents

the vsix doesn't package itself due to weird errors that needs investigation

[vasily-kirichenko]

Rebase it on master.

[smoothdeveloper]

Ok, now all the "normal" compile time build failures are fixed on appveyor, only the vsix packaging is failing (same as what I'm seeing locally).

I wonder if someone with a bit more of experience with VSSDK could give it a quick look (don't spend hours) to see if this can be solved.

cc @jaredpar any idea how to diagnose this Given type must derive from ITag:

https://ci.appveyor.com/project/dungpa/visualfsharppowertools/build/2.6.0-a1607161349#L735

[dungpa]

As the first step, you could:

• merge vssdklegacy and vssdk10 groups.
• remove vssdk11 and vssdk12 groups completely by changing references to vssdk14.

This will simplify package management of VSSDK assemblies.

[smoothdeveloper]

@dungpa are we dropping support for VS2013?

[dungpa]

Although we compile for VS2015, binaries can still be used for VS2013.

[smoothdeveloper]

Ok, I'm giving it another shot, I'm thinking, do we need a separate v2015 project if the SDK/VS doesn't have issue with code calling later part of SDK?

Say we develop feature for next release VS15, does that have to be in separate project?

[smoothdeveloper]

Problem if I remove vssdk12 (and keep only vssdklegacy and a merged vssdk) is that I get obsolete feature warning (as error) at each usage of SmartTag.

I don't know how to suppress those wanrnings.

[smoothdeveloper]

@dungpa @vasily-kirichenko this is green :)

I had to add 44 at the warning exclusion list though (Obsolete members), I hope we are ok with this.