Net Core it is actually highlighted that the mixure is viable That is kind of odd: if this was not meant to be allowed, why is it still possible in VS and why in all pics/posts related to. I'm still able to create a "mixed" solution (with xproj and csproj), the solution builds in VS but not via MSBUILD. It seems that also with the final release of ASP.NET Core 1.0 the situation remains unchanged. So, for my example, the restore.dg file for dncClassLibrary1.xproj would be in /src/dncClassLibrary1 and its content would be vs/restore.dg pertaining to that project. The best way to handle it for me was to put a restore.dg in each dotnet core project's directory. The restore.dg is a bit trickier since the paths in it are absolute. But, as long as you keep your in your repository, that shouldn't be an issue. I figure the export file is the that VS generates. Lock file .LockFile contains msbuild projects but there is no export file That however only generates a, and if we try to dotnet build we get the error \src\dncClassLibrary1\dncClassLibrary1.xproj|\ClassLibrary1\ClassLibrary1.csproj #:\src\dncClassLibrary1\dncClassLibrary1.xproj
0 Comments
Leave a Reply. |