Announcing .NET Core 1.0
221–230 of 327 posts
Re: Announcing .NET Core 1.0
#222Earlier quoted context omitted.
You can go ahead with PostreSQL if you use Entity Framework and Code First approach. I used it many times and I was able to quickly jump from PostreSQL to MS SQL and back. It just works. With EF I don't see any reason why I should tie to any particular SQL database
Personally, I prefer writing SQL by hand. That way I know exactly what will happen in a query. A database really is an important component of a system and shouldn't be treated like a dumb data store where you just throw in any stuff you like through an ORM and hope it sticks there somehow.
Re: Announcing .NET Core 1.0
#223Do we officially have better-than-Java on all platforms now?
Yeah but so what. If the "best" language always won, why isn't the entire world running on Haskell and Rust or whatever? Java's eco-system is ginormous and it's deeply entrenched as the "corporate stack" in non-MS shops, with more than 15 years of history. I'm afraid this is just too late to make a big dent. C# is nicer than Java, but not that much nicer to warrant switching over or rewriting your stuff in a very imm…
Especially as the tooling for micro-services and docker (or similar) gain traction moving forward. C# is pretty well supported, and at least here in Phoenix is about as common as Java is... can't speak for other metro areas.
I've been a pretty big node.js fan, and haven't used C# as much the last few years, but I wouldn't count it out. Two years ago, C# wouldn't have been on my radar for a new project, now it's entirely possible, given the opportunity for better cross platform deployments.
Re: Announcing .NET Core 1.0
#224FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…
Re: Announcing .NET Core 1.0
#225What happened to the so called promised "dynamic compilation"? There was supposed to be a great improvement in compilation times...which is still quite long on the default sample. I don't feel like Microsoft has improved enough for me to make the switch from .NET 4.x.
Re: Announcing .NET Core 1.0
#226Any ideas how to do GUI development with .NET Core? Is there a version of Xamarin? Are there plans to port Windows.Forms, WPF? There is this massive thread about it http://forums.dotnetfoundation.org/t/cross-platform-wpf/421/... and an issue here https://github.com/dotnet/corefx/issues/5766
CatLight is one of the apps that do that - https://catlight.io
Re: Announcing .NET Core 1.0
#227Earlier quoted context omitted.
So it is bad when Microsoft asks to do it, but ok when Eclipse, Netbeans or InteliJ do it? They are being quite open about it and how to turn it off.
Yes. It's bad when Microsoft does it this way because it's opt-out. IntelliJ/Android Studio prompts you and asks you your preference first. I think Eclipse is opt-in but could be mistaken.
Re: Announcing .NET Core 1.0
#228Earlier quoted context omitted.
> a button was removed from File Explorer Would that be the "Go up to the parent directory" button that was removed in 7 by any chance?
Easily my favorite button in file explorer.
Re: Announcing .NET Core 1.0
#229Earlier quoted context omitted.
The naming is really confusing, but then naming things is hard. As Phil Karlton famously said: There are only two hard things in Computer Science: cache invalidation and naming things.
I don't know where it came from, but I've always preferred this variant: There are only two hard things in Computer Science: cache invalidation, naming things, and off-by-1 errors.
Re: Announcing .NET Core 1.0
#230F# doesnt work ootb with sdk preview2. Work ok with preview1 of SDK (win/ubuntu/osx/docker), but preview2 has a bug, the fix is in progress ( ref https://github.com/dotnet/netcorecli-fsc/issues/12 ) and will be published a nuget package with fix soon.
Known issues will also be updated, as will documentation on how to use F# on .NET Core.