Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Announcing .NET Core Tools 1.0

blogs.msdn.microsoft.com

Post reply on HN
Print view View original

21–30 of 44 posts

Re: Announcing .NET Core Tools 1.0

#21

Post by AwesomeBean »

replete wrote: post #13

I'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.

You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear.

While I would love a simpler, more readable project file, I understand that the tooling already out there relying csproj format, probably makes it not worthwhile changing.

Re: Announcing .NET Core Tools 1.0

#22

Post by josteink »

debacle wrote: post #3

The only thing that has really bothered me about .NET Core is I haven't been able to figure out how to get NuGet to run properly on Linux.

> I haven't been able to figure out how to get NuGet to run properly on Linux.

Use the "dotnet" binary and just run "dotnet restore"? This will restore whatever packages your project references-

Or are you thinking about pakage-management, as in searching for and installing new packages?

Re: Announcing .NET Core Tools 1.0

#23

Post by DaiPlusPlus »

ubercow wrote: post #12

Hopefully this will be the much-awaited end of all of the tooling confusion around the project.json to csproj change.

There's still a bunch of fundamental changes to how the XML-based MSBuild files work, such as the addition of wildcards and recursive includes, so expect a wait for the rest of the ecosystem to catch-up.

Note that the move back to MSBuild from Project.json was prompted by pragmatism rather than ideology - I suspect the JSON-camp are biding their time before putting forward another proposal.

Re: Announcing .NET Core Tools 1.0

#24

Post by insertnickname »

finchisko wrote: post #15
insertnickname wrote: post #14

Tried 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.

Yes, I understand that I am missing a dependency. What I don't understand is how I am supposed to get that dependency.

Re: Announcing .NET Core Tools 1.0

#25

Post by rubber_duck »

AwesomeBean wrote: post #21
replete wrote: post #13

I'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.

You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. While I would love a simpler, more readable project file, I understand that the tooling already out there relying csproj format, probably makes it not worthwhile changing.

>You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear.

Great and in those 10 months there was no alternative but to use the soon to be deprecated projects. And they released a 1.0 product like that.

Someone from Microsoft commented unofficially that there was pressure from partners who were using .NET Core in production to release a stable - which was very obvious and they put them self in a spot where they had to support a deprecated project.json system since people are using it in production while also developing the new system. Whoever decided on the release timelines dropped the ball.

Re: Announcing .NET Core Tools 1.0

#26

Post by tonyedgecombe »

DaiPlusPlus wrote: post #20
finchisko wrote: post #18

I 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.

It would be nice to see Winforms and WPF pulled out into their own projects on top of .Net core. Both could do with some cross platform open source love.

Re: Announcing .NET Core Tools 1.0

#27

Post by pantalaimon »

insertnickname wrote: post #14

Tried 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…

    sudo apt-get install dotnet-dev-1.0.1
works if you have the partners repository enabled.

Re: Announcing .NET Core Tools 1.0

#28

Post by AwesomeBean »

rubber_duck wrote: post #25
AwesomeBean wrote: post #21

Earlier quoted context omitted.

You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. While I would love a simpler, more readable project file, I understand that the tooling already out there relying csproj format, probably makes it not worthwhile changing.

>You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. Great and in those 10 months there was no alternative but to use the soon to be deprecated projects. And they released a 1.0 product like that. Someone from Microsoft commented unofficially that there was pressure fr…

Well for the last 4 months, MSBuild alpha has been out with the option to use "dotnet migrate" to migrate a project.json to a project.csproj file.

The other 6 months I agree has left people in a limbo. Only people following the discussions closely would have an idea of which direction they were going.

Re: Announcing .NET Core Tools 1.0

#29

Post by philliphaydon »

oblio wrote: post #19
finchisko wrote: post #18

I 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.

There is already a community driven WPF type library. I can't find it on my phone. It was posted on NH like 6 months ago.

Re: Announcing .NET Core Tools 1.0

#30

Post by hubert123 »

Still dont get it at all. I installed VS2017 today, dotnet --version = 1.0.0

I go to the dotnet core website, download a new sdk and install. dotnet --version = 1.0.1

Oh and the file is called "dotnet-1.1.1-sdk-win-x64.exe" Notice yet another version number.

Same thing on Linux. tar.gz has 1.1.1 in the name, installed version is 1.0.1

Post reply on HN