https://i.imgur.com/2uLUNH1.png Why is Microsoft serving Panasonic.jp SSL certificate ?
Vault7 at work :-)
Announcing .NET Core Tools 1.0
11–20 of 44 posts
Re: Announcing .NET Core Tools 1.0
#12Hopefully this will be the much-awaited end of all of the tooling confusion around the project.json to csproj change.
Re: Announcing .NET Core Tools 1.0
#13I'm done with endless refactoring of .NET Core updates.
The reality is they shipped RCs with 1.x version numbers.
I will be back to reassess after Core 2.0 gets a minor update.
Microsoft suck at versioning. Progress is great, but we feel tricked.
Re: Announcing .NET Core Tools 1.0
#14Tried installing the Ubuntu 16.10 deb, but getting this error:
$ 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.1Re: Announcing .NET Core Tools 1.0
#15Tried installing the Ubuntu 16.10 deb, but getting this error: $ 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-sharedfra…
You are clearly missing other dotnet dependencies. Apt output is mentioning dotnet-sharedframework-microsoft.netcore.app-1.1.1. Anyway I personally would go with docker image, so you won't mess up your system. I've tried microsoft/docker image om example from that arcticle and was successful.
Re: Announcing .NET Core Tools 1.0
#16I'm done with endless refactoring of .NET Core updates. The reality is they shipped RCs with 1.x version numbers. I will be back to reassess after Core 2.0 gets a minor update. Microsoft suck at versioning. Progress is great, but we feel tricked.
They were pretty clear from the early days that this was WIP, did you never watch a MS presentation?!
Re: Announcing .NET Core Tools 1.0
#17This is pretty cool and I was excited to hear about it. 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. 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…
Is the change documented anywhere? I looked through all the release notes and couldn't find it.
It looks like it wasn't this release that changed the testing. The comments about nUnit not working are from November / January / February:
https://github.com/nunit/dotnet-test-nunit/issues/91
Re: Announcing .NET Core Tools 1.0
#18I saw CONSOLE and ASP profiles .NET Core profiles. Can .NET Core also be used to develop GUI apps?
Re: Announcing .NET Core Tools 1.0
#19I saw CONSOLE and ASP profiles .NET Core profiles. Can .NET Core also be used to develop GUI apps?
Not at this stage, if you don't want some sort of pre-beta 1-man project.
Microsoft is not investing so it will have to be community managed.
Re: Announcing .NET Core Tools 1.0
#20I saw CONSOLE and ASP profiles .NET Core profiles. Can .NET Core also be used to develop GUI apps?
Through P/Invoke, sure. But WinForms, WPF, and UWP (and Silverlight, and XNA) are not part of .NET Core by-design. Though I assume someone will port Xamarin over, if they haven't done already.
I'd love to see SDL support so OpenRA can have another build target.