This is pretty cool and I was excited to hear about it.<p>But this release also changes the way unit testing integrates with the tooling, so now my suite of 1000+ nunit tests won't run via the 'dotnet test' command, nor in visual studio 2017.<p>If not for that, we would have upgraded today. Eventually the nUnit team will release a test runner that works with the new tooling, but in the meantime, we will stay on preview2 of the tooling & vs2015 where our tests work.
I'm done with endless refactoring of .NET Core updates.<p>The reality is they shipped RCs with 1.x version numbers.<p>I will be back to reassess after Core 2.0 gets a minor update.<p>Microsoft suck at versioning. Progress is great, but we feel tricked.
Is there any reason that I should care about .Net Core yet over .Net 4.6 if I'm a Windows only developer or should I just wait for things to settle down?
Still dont get it at all. I installed VS2017 today, dotnet --version = 1.0.0<p>I go to the dotnet core website, download a new sdk and install. dotnet --version = 1.0.1<p>Oh and the file is called "dotnet-1.1.1-sdk-win-x64.exe"
Notice yet another version number.<p>Same thing on Linux. tar.gz has 1.1.1 in the name, installed version is 1.0.1
Tried installing the Ubuntu 16.10 deb, but getting this error:<p><pre><code> $ sudo dpkg -i dotnet-sdk-ubuntu.16.10-x64.1.0.1.deb
(Reading database ... 408184 files and directories currently installed.)
Preparing to unpack dotnet-sdk-ubuntu.16.10-x64.1.0.1.deb ...
Unpacking dotnet-dev-1.0.1 (1.0.1-1) over (1.0.1-1) ...
dpkg: dependency problems prevent configuration of dotnet-dev-1.0.1:
dotnet-dev-1.0.1 depends on dotnet-sharedframework-microsoft.netcore.app-1.1.1; however:
Package dotnet-sharedframework-microsoft.netcore.app-1.1.1 is not installed.
dpkg: error processing package dotnet-dev-1.0.1 (--install):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
dotnet-dev-1.0.1</code></pre>