.NET Core 1.0 release – what you need to know to get started

https://raygun.com/blog/2016/08/net-core-1-0-release-get-started/

by yurt_ • 10 years ago

64 40 10 years ago

raygun.com

spriggan3• 10 years ago

Finally ! Goodbye php,ruby and go ! can't get rid of Python though, simply the best language for analytics.

JoelBennett• 10 years ago

Just out of curiosity, have you looked at F#?

(I use Python at my day job, and C# on my own side projects at home. F# seems... interesting).

nxh• 10 years ago

What are the biggest benefits of using NET Core in comparison with Go, Ruby, Python?

gnaritas11• 10 years ago

Speed of course, and a huge standard library that works with multiple languages, Ruby and Python are dog slow compared to C#; can't speak to Go, haven't used it.

snaky• 10 years ago

F# with all the .NET libraries.

gnaritas11• 10 years ago

Getting to use C# on a fast runtime, none of those things you mention allow me C#.

jsmith02953• 10 years ago

I really wanted to give this a try, but the lack of first-class MySQL support makes it a non-starter for me at this point. There are third party drivers, but they don't seem to work with many Entity Framework features.

cdmckay• 10 years ago

Isn't this a first-party driver? https://dev.mysql.com/downloads/connector/net/6.9.html

jsmith02953• 10 years ago

That's for EF6, which only runs on Windows. Can't use Windows servers where I work.

justinmk2• 10 years ago

Trust me, you don't want EF--no matter how many times they say "vNext is gonna be great!!1 for real this time." Consider a micro-ORM like dapper[1].

[1] https://github.com/StackExchange/dapper-dot-net

gnaritas11• 10 years ago

Yes yes yes, but better yet, write your own. Micro ORM's are "micro", it's pretty trivial to create something better than Dapper and there's no framework in the world better than your own, to you, because there won't ever be anything to complain about, just mold it to work exactly how you like.

Dapper..

    var dogs = connection.Query<Dog>("select Age = @Age, Id = @Id", 
        new { Age = (int?)null, Id = guid });

yuk, I prefer

    var dogs = Dog.FindAll(And(IsNull("Age"), Equal("Id", guid)));

A touch of generics done properly, a bit of reflection, a static import, and you can do much better than onnection.Query<Dog>. Write the API you want, implementing what is basically an active record without relationships is not terribly difficult and will pay off for years to come in your own code.

Edit: Dappers API is ugly as fuck, that's an immediate non-starter for me, and the cost of reflection on loading objects is the wrong problem to be optimizing and would only show up in an absurd micro benchmark intended to show off speed that doesn't matter, it's small compared to the execution time of the queries. If you like it, use it, but lets not pretend it's so much effort it isn't worth redoing. It's certainly not the end all be all of ORMs.

taspeotis• 10 years ago

Pick the right tool for the job. EF works great for us for OLTP workloads. OLAP workloads: choose something else.

jsmith02953• 10 years ago

I tend to prefer things which are more lightweight, but my coworkers don't. I'm mostly wanting to pitch this as a better alternative to Spring Boot and JPA.

meira• 10 years ago

Now is the time, Microsoft. Go for it!

dblooman• 10 years ago

Are there any guides for OSX/Linux that don't end with printing hello world. A lot of what seems to be out there is very basic or starts talking about Windows when it starts to get interesting

mjgoeke• 10 years ago

Too bad the tooling (e.g. restore, build, package) and (I think) the project files format is still preview.

So far, my experience has been that small isolated project seem to work fine, but as soon as I try to break a more complex solution out into separate nuget dependencies things start to get hairy.

Nuget dependency versions don't support npm-like syntax, so you can forget about the "^1.0.0.0" notation. Syntax like "[1.0.0.0-2.0.0.0)" might be supported, but honestly I've been fighting with other issues enough that I can't recall for sure if making the version syntax ugly makes it happy.

Another surprise to those from javascript/npm land is multiple versions of the same library in your dependency tree isn't supported. So you basically need to support redirecting to a commonly supported version (which, without examples showing version ranges, you're back at the version range syntax pains).

If anyone's tackled these pain points I'd love to hear.

soulnothing• 10 years ago

I'm new to the CLR build system myself, and have sort of gotten stuck on project formatting. The F# side seems to have some newer build systems, and are trying to go towards a simpler build/project system.

For dependencies see Paket[1]. It allows versioning, and only the parent dependencies not the entire dependency tree.

For building much like Gradle there is FAKE [2]. It's an F# DSL for build tasks, and has type safety etc. But I've seen examples with C# project as well.

[1] https://fsprojects.github.io/Paket/getting-started.html [2] http://fsharp.github.io/FAKE/

cylo• 10 years ago

I haven't been able to reliably/easily get a project to compile on Linux into a self contained executable similar to Go.

At one point this was advertised in blog posts as something that would be possible. Has this changed?

I think it's one of the killer features that help ease the burden of deployment for a lot of folks.

.NET Core 1.0 release – what you need to know to get started

Related Stories