Andrew Boyarshin
Andrew Boyarshin
@moh-hassan ref #189.
Yeah, that seems like it. Although [this page](https://portablelibraryprofiles.stephencleary.com) is better in that respect (don't forget to enable showing legacy profiles).
Well, that's strange. There is no point in preventing the user to convert if they are aware of `net40` default in MSBuild. It is more like inconsistency in CPS MSBuild...
Legacy will. CPS will assume _, v0.0, but if we set TargetFrameworkIdentifier to .NETFramework, everything (even restore) will work fine.
@hvanbakel I'm still looking for the optimal solution. > Also we could just set that in the main property group with the condition on the TargetFramework node, right? I'm afraid...
@hvanbakel > I'm still looking for the optimal solution. In fact, the condition is wrong (TargetRuntime is not set at the moment of the evaluation when TargetFramework is not set).
Diagnostics left to implement after #146: * [ ] W012 * [ ] W013 (suggested by @hvanbakel — pending clarification)
@hvanbakel I'm not sure about your PackageReference concerns. [This doc page](https://docs.microsoft.com/en-us/nuget/reference/package-versioning#examples) clearly shows it should work. Do I understand your comment correctly?
@hvanbakel oh, you mean when you update deps in VS NuGet package manager for example, VS overwrites Version property with precise version instead of preserving it and merely updating local...
W012 ref #190