Announcing .NET Core 1.0

Re:Announcing .NET Core 1.0 by knocte on Monday June 27, 2016 @11:55AM (#11987002)

I was expecting they would fix the Uri class on Unix (https://github.com/dotnet/corefx/issues/1745) before releasing 1.0 :( Now I fear their backwards compatibility policies will prevent to fix it later. So much for crossplatformness...

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by jsingleton on Monday June 27, 2016 @12:14PM (#11987142)

They've renamed some packages, so this might possibly be fixed in another one? I found the Ping class didn't work on any non-Windows OS, but it was fixed in a later package with a new name.

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by tacos on Monday June 27, 2016 @12:14PM (#11987141)

Way too many compatibility issues unaddressed by that PR to have a hope of getting anything changed there. Also it looks like what you (?) are trying to do could easily be solved with the Path.* and Directory.* path manipulation functions. No need to put a million apps at risk when you can wrap your call to Uri() with a three line helper.

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by knocte on Monday June 27, 2016 @12:55PM (#11987494)

3line helper? facepalm...

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by triangleman on Monday June 27, 2016 @01:29PM (#11987768)

Care to enlighten us?

[ Parent | on HN ]

Re:Announcing .NET Core 1.0 by recursive on Monday June 27, 2016 @02:01PM (#11988033)

How many lines would be acceptable? Your frustration is inscrutable.

[ Parent | on HN ]