jose-jwt icon indicating copy to clipboard operation
jose-jwt copied to clipboard

Published 20 hours ago • verified publisher icon dvsekhvalnov

Any plan to move the solution to the new VS 2017 format

Open StefH opened this issue 8 years ago • 5 comments

Do you have any plans to migrate the solution to the new VS 2017 csproj format ?

And additional question : why do you require netstandard 1.4 instead of netstandard 1.3 ?

StefH avatar Jul 17 '17 14:07 StefH

Hi @StefH ,

  1. instead of project.json? will it solve any issues?

  2. was missing some package in netstandard 1.3, can't recall which one exactly to be honest.

dvsekhvalnov avatar Jul 17 '17 19:07 dvsekhvalnov

  1. It's better to move on to the new format, better support for .net core / .netstandard in vs 2017
  2. It's always better to keep the dependencies as low as possible.

I can help you on both points, do you want help?

StefH avatar Jul 19 '17 18:07 StefH

Hi @StefH ,

sure i'm always open to merge requests.

If you gonna migrate off from project.json, please submit to separate branch (not master), i probably will need to upgrade my dev env first.

dvsekhvalnov avatar Jul 25 '17 10:07 dvsekhvalnov

Heads-up that VS 2017 does not support (visually) multi-targeting with csproj as well as it did on project.json. I just did multi targeting last night and it was all csproj work.

aidapsibr avatar Jul 25 '17 23:07 aidapsibr

Indeed correct. I do also have moved a lot of projects to the new csproj format, and all is some manual work. But creating NuGets is very easy.

StefH avatar Aug 02 '17 18:08 StefH