[1.1.x patch] Fix API set target

[Tratcher]

#347
@jchannon

[jchannon]

Excuse my lack of internal MS workflow but where do we go from this issue being marked as a "patch-proposed" to a patch?

[Eilon]

@jchannon this issue is not currently slated for a patch release. Would it be possible for you to use a custom build of the package? Or use a 2.0.0 nightly build (where this issue is already fixed).

[jchannon]

Would the custom build be built by myself? I could use a v2 nightly but I assume that would mean upgrading our whole app to run on netcore v2?

…

On 25 April 2017 at 04:56, Eilon Lipton ***@***.***> wrote: @jchannon <https://github.com/jchannon> this issue is not currently slated for a patch release. Would it be possible for you to use a custom build of the package? Or use a 2.0.0 nightly build (where this issue is already fixed). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#349 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGapj8zO5bI3dRuCQU90PfB_UOLdy6gks5rzW7qgaJpZM4NDVvl> .

[Eilon]

@jchannon yeah using 2.0 would mean using nightly 2.0 bits for the whole app. Would that work for you?

It should be pretty easy to make your own build: just clone the repo on Windows/Mac/Linux to the right branch/tag, make the change, and run build - it'll produce all the required NuGet packages and DLLs.

[muratg]

@Eilon should we close this one? (And #348)

[Eilon]

Why close it?

[muratg]

@Eilon IIRC, this was rejected for the previous patch release.

[Eilon]

Ok... if there are bugs we don't want to consider for the patch, go ahead and close 😄

[muratg]

Closing this. The bug is fixed in 2.0.0 RTM, and we don't plan to bring the fix back to 1.x.