Split to two packages for visualstudiogallery about gitdiffmargin

[SLaks]

Why?
You should be able to support both with one build.

If you have any trouble with that, ask me; I have a lot of experience with this.

On a related note, can you please declare support for Dev14?

[laurentkempe]

Because I would like to support VS2013 and VS2012. For that I plan to have two VS projects sharing the code, because GitDiffMargin uses an API of VS2013 which is not available in 2012. Do you see a better way?
It would be great to get your help, thanks.
I could but I don't like the idea of doing that without having tested it and currently I don't have the infrastructure to test it.

[SLaks]

Which APIs?

[laurentkempe]

The one to be able to display the diffs in the Scroll Bars in map and bar mode

[SLaks]

You mean scroll bar map mode?
Which specific classes / methods are those? (where in your code?)

Depending on how your code works, you should be able to simply wrap that code in a version check.
However, you would probably need to move it into a separate project that references v12 of the relevant DLLs so that your main project can reference v10 & work on VS2010+.
See also http://blog.slaks.net/2014-02-25/extending-visual-studio-part-4-writing-cross-version-extensions/

[laurentkempe]

I mean the scroll bar on the right of the window
Here are some specific code for VS13

Sure I could use C# Preprocessor Directives for the different versions but this solve only the problem of the source code. Then I thought I could solve the problem of references with the following way but it doesn't work for references. So this is why I thought to go to two projects as my code let you do that with the two Factories: EditorDiffMarginFactory & ScrollDiffMarginFactory.

So the idea would be to remove in the VS12 versions the source code for ScrollDiffMarginFactory and all it's related classes/views...

[laurentkempe]

In fact I changed the references to use SDK of VS12 and the only specific thing are the 4 Order lines

[laurentkempe]

You might have a look to the Pull Request which solve the problem in a different way.

[SLaks]

Yes; that PR is exactly what I was going to suggest.
(since you're only using new constants, not new APIs)

[sharwell]

Aside from inlining the constants, you have to use different values for the [MarginContainer] attribute, since the graphics show next to the scroll bar in 2010-2012, but over the scroll bar in 2013+. The rest of it was just improvements for loading and debugging the project.