Meta: Blocking RTM issues

[clairernovotny]

As of today, the Rx.NET solution using xproj/project.json (Rx v3.1.1 in master) does not successfully migrate to the latest CLI tools.

There are several underlying issues that are mostly attributed to unrecognized TFM's.

• Wrong error message in some cases for TFMs without built-in support #663
• TargetFrameworkVersion gets lost on PCL targets #492
• Support additional target frameworks such as for Xamarin, UWP, etc #491
• https://github.com/dotnet/cli/issues/4847
• Pack target misses .pri files for Windows targets when multitargeting NuGet/Home#4136
• Pack command generates incorrect dependencies  NuGet/Home#4137

There's also an issue of files outside of a project scope not showing up in VS. There's a workaround that I think is good in an RC but is not good enough for an RTM.

• Including files outside the project cone don't show up in soln explorer project-system#1233

There's one about p2p refs:

• Netstandard 1.0 PCL (classic) cannot add P2P ref to cross-compiled CPS proj project-system#936

There's an issue with glob's from a parent dir not working correctly

• Excludes or removes in project folder don't apply to recursive includes from a parent folder msbuild#1576

 

[TheRealPiotrP]

@srivatsn @rrelyea

[rohit21agrawal]

i believe NuGet/Home#4137 has been fixed

[TheRealPiotrP]

Closing. We're tracking this meta-issue through the individual issues.