- ASP.NET 5 web apps and services - see: https://github.com/aspnet/home - Native executables - see: https://github.com/dotnet/corert/blob/master/Documentation/i...
What do you think?
Disclosure: .NET Core team member
- ASP.NET 5 web apps and services - see: https://github.com/aspnet/home - Native executables - see: https://github.com/dotnet/corert/blob/master/Documentation/i...
What do you think?
Disclosure: .NET Core team member
I've been building in MVC3/4 for the last few years so have quite a bit of experience with how MS has been evolving in this space. From "BundleTransformers" through "Web Essentials" and now suddely all the way to GULP
I started building a weekend and evenings project in EF7+MVC6 at Beta6 and have suffered through breaking changes in beta7 & 8 but each stage of the way I've enjoyed myself.
Some of the things that I have recently struggled with is getting the project working on linux VMs and docker.
While I can get boilerplate projects working, this "bigger" project struggles to compile on docker.
Part of it may be my own fault since I've split the solution into multiple projects ("WEB", "API", "MODEL") where MVC6 seems to have a paradigm of keeping everything in the same project, but it does seem to work OK on a windows 10 host (I keep wanting to test it on azure but that's another story)
There isn't any clear path as of yet from "building something that runs locally in VS" to getting it hosted in a "massively scalable cloud of containers"
I'm exploring docker and kubernetes at the moment - but progress is slow :)
Additionally - in terms of development - I'd like to see some more scaffolding, like I see with (for example) strongloop/loopback in node.js I'm finding that my API breaks down in .NET when I try and use an EF entity around since we get into circular JSON references.
Anyways, I'm starting to get off on a tangent. I really do like what I see in .NET5 though feel there are some pains in places. Specifically around containerizing & rapid application development.
That way I can try the latest and greatest of rc2 without having to rebuild my container every time new packages go up on myget.
It's a pretty minor ask... I'm probably one of a very small number of people that are stubborn enough to be on the bleeding edge (using rc2 when rc1 is the latest release, etc)
I am interested in finding out how it compares right now to Java for building web apps and services - in terms of DB access, various ORM stuff etc.
You can follow their progress: https://github.com/Microsoft/visualfsharp/pulls?utf8=&q=is%3...
http://www.hanselman.com/blog/OmniSharpMakingCrossplatformNE...
And assuming I can, is anybody else doing this? In the past it seems like production Mono makes no sense when Python and Node just work without additional libraries to make it work.
Edit : Not talking about Visual Studio Code, but the -original- Visual Studio IDE.
Maybe not project templates, they seem to be targeting Yeoman as the use case for "getting started".
But autocomplete and git integration are definitely there. In some ways better than how VS does it.
It may still be a while before is "surpasses" true VS - but - with support for sublime and textmate snippets it may be about to catch up to those two.
Has the ASP.NET request processing pipeline changed significantly in v5? Last time I checked, our fork of Nancy only really cares about _Init, _BeginRequest, and the unhandled exception handler.
ASP.NET 5 is essentially based on OWIN as a pipeline which uses a pipeline of async Func calls (that can be wrapped up into "middleware" components). NancyFX, actually implements an OWIN middleware which I think would be easy to tie into ASP.NET 5, but I haven't tried yet.
IIS also has too many knobs that can get fiddled and frig things up. Before we switched, I'd always be on support calls to help a customer fix one of our products after their sysadmin tweaked something in a way to break us, or installed some other piece of software that stomped on us.
IIS also has a very conservative set of defaults if you naively install it. Seriously, I've seen a lot of instances where customers install IIS, and CSS doesn't get served - you have to install an additional Static Content module. People don't read instructions, or bother to run required setup scripts. So you have to do a bunch of additional work with less-than-friendly installer authoring programs to make sure that features that any self-respecting web server ought to have out of the box are available.
[0]: http://scriptcs.net
https://docs.asp.net/en/latest/tutorials/your-first-mac-aspn...