If you get the latest version of RTM.net RTM and the Update 3 VS toolkit, everything will be a little better than in the RC period. However, there are no simple links to projects from csproj referencing xproj, but you can get it to talk by collecting the output of xproj into a nuget package and then using the package manager to install this package. In addition, you do not need to import a framework or dependency on netstandard.library, at least I do not. Here is how I did it:
Create a .cmd file that will pack the nuget files and two copy the output files to the folder in which the package manager expects them. Here is what the script, I call it makeNuget.cmd:
IF "% 1" == "% 2" (
dotnet pack --no-build --configuration% 1 -o ../% 3
xcopy% 4 "... \% 3 \ lib \% 5 \" / Y
)
Add postbuild script to project.json from xproj to run the script
"scripts": {
"postcompile": ["makeNuget.cmd% compile: Configuration% Release Packs \% project: Name %% compilation: OutputDir %% compile: TargetFramework%"
]}
This should leave you in the nuget package in the \ [projectName] \ folder at the root of your solution, with the binaries in the packages \ [projectName] \ lib \ [targetFramwork] \ folder
- Now you need to add the package folder as the package source, so first open the package manager console, then click the small gear to add the package source (or Ctrl + Q, package sources, Enter). Then click the Add button, name this source, browse or enter the package directory and click OK.

- In the Package Manager console, make sure that both the source and the package project are selected in the drop-down lists at the top.
- install-package [name of your package]
AFAIK, which is as good as it is now.
Erikest
source share