Library conflict with Microsoft.Bcl.Memory

[Nness]

Microsoft has released Microsoft.Bcl.Memory to allow use of index and range in .Net 4.6.2. Where IndexRange package start conflict with other Microsoft owned library due to this.

[Nness]

Refer to pull request #179

[Nness]

@saucecontrol when you have time, could you take look this pull request to resolve conflict on index and range in .Net 4.6.1 above projects.

[saucecontrol]

Hey, thanks for logging this. I'm aware of the new package, but I chose not to use it for now, because it brings its own set of issues.

The dependencies for the Microsoft.Bcl.Memory package are out of sync with the current version numbers of System.Memory's dependencies, which results in assembly load failures for some legacy project types unless the user manually creates all the necessary binding redirects.

The conflicts with Index and Range types can be resolved through aliasing if you add an explicit reference to the IndexRange package.

I realize this is not ideal, but unfortunately, this is a case where one or the other groups of users will be broken without manual intervention. Since the Microsoft package doesn't offer any benefits beyond reducing potential conflicts, I'm going to wait until they sort out their transitive dependencies before adopting their package.

[Nness]

That worked, thanks

[saucecontrol]

That worked, thanks

Glad to hear it!

I'm going to leave this open for visibility and because I do hope to switch over at some point.