just did a project with .netCore 1.1, with a few .netstandard 1.6.1 dependent dll’s. I have the same project running under .net4.6.1. Using VS2017RC, used the new .csproj file format (its great to be able to drop files in explorer and see them appear in the project in Visual Studio). I had to comment out all the AssemblyInfo.cs file content; system was complaining about duplications. Is AssemblyInfo.cs passé in the new .netCore/.netstandard world?
So I ran this the .netCore program (a utility that dumps info from a structured storage (OLE) file) both on Ubuntu 16 and MacOS Sierra, and it actually ran! I noticed that the startup of the program is slow (even when it has compiled) [using dotnet run], compared to the .net 4.6.1 running on windows. I will try to measure the actual performance of the program on Linux/Mac .net Core vs Windows .net 4.6.1.
Is there a reason why dotnet build cannot build a native .exe file for the local environment? It feels weird having an .exe project outputting a .dll.
Also, it would be good to be able to load the new .csproj file format into VisualStudio on the Mac. I’m sure that tooling will come at some point in time.