I did not try to use Blazor yet, but I did use Razor pages with .Net 4.x, and I will definitely try Blazor. Currently forced to use Angular, which is just OK, but the idea of getting finally rid of the javascript sounds like a real dropping of shackles. The phrases "made my day": 36:32 - Life is too short to wait for the NPM to restore. 37:42 - Takes a second for the Angular dev server to wake up... (45 seconds later) 38:27 - Let's see if it's gonna render... Here it comes.
He IS the human Blazor! A very good presentation! In the past I used to dread .net, but after watching this video, I am so intrigued in learning and dwelling into it.
when i finally compromised and dig our head to javascript and spa, here it said there is a .net solution which capable of doing most of the eye catching things
Actually it depends on how you are using this languages , The anwsor is .NET Core. But it can be slower if you used blazor with it becouse avery client will have to download in minimale 3.2 mb , it steel new in the game (in this moment). but if you used .NET for server side it will be much much MUCH faster than php . But The Cool Thing in Blazor is that you can use c# with all its capibiletis ( Like Unity Game Engine ) Its so awsome
Hey Microsoft! Thank you for new updates in .NET Core helping us improve in .NET development. I was confused to choose a web development, but now I believe I should do .NET for at least a year before switching to any other platform. Until then I will continue sharing how I felt about learnt interesting on #DevOTram
@Solve Everything Yes, I hope it will be better and better. Open source, cross-platform, high performance, clean code and great features - these are what we need.
This guys knows how to host a presentation!! I really like the concept, but would like to see dll bundeling, to reduce the amount of file, which are downloaded.
I don't have any plan to move to Blazor because I'm developing my application with asp.net mvc core 2.2. But I think Blazor is a great idea from Microsoft team to improve asp.net core community and keep anyone want to changes from .NET to other platform.
Where can I find the "Blazor (ASP.NET Core hosted)" project template? After installing VS2019 Preview all I see is "Blazor server App". EDIT: got the template by running dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.0.0-preview7.19365.7
I'm trying to setup a "Blazor (ASP.NET Core hosted)" Web Application. However my visual studio community preview just shows me a "Blazor Server App"... What do I need to do, to get the ASP.NET Core hosted one???
Daniel Roth, Just a few question, with regards to queue based system which would run a portion in memory and have a persistence portion. In terms of power outage and there being limited power, in which a system is required to shutdown, before it dies. Has there been any work put into place with os, hooks that can manage the amount of resource that all the queues in a system in memory can use and how large the can grow, to ensure that the queues can be flushed to persistence storage in the event of a power outage. This is quite critical, when running in environments, where there is limited back power available, especially if you think of wanting to run more devices closer to the edge of the network. One is going to have to strike a balance between the server, returning errors not accepting any more work and flush and saving the current work and taking an appropriate action in time before power loss, such as canceling an order, because a hot pizza being deliver late when the power comes back on, is not going to fly. So there need to be different types of actions requested for signal power outage, in which queue needs take few different action, persist to resume later, or inform up or downstream urgently, that service has failed! Communicating to the up and downstream entities that service is going down, I don't think would be reliable, because so many things that can go wrong there. I think one would need to implement a contract, were by the queue is suppose to provided feedback, to confirm that the system will be left in a consistent state. Which would be similar to bitcoin, having to have carried out the work, before certain constraints, otherwise, assumed that work load failed. blockchain contracts. What are you thoughts on this matter. I know depending on were the persistence is located that other machines can resume the work, more centralised database system, provide that those service don't go down. Internal queue based communication system should be ok with contracts that can die, however, those were I have place and order and left the site, would need to be process and actions taken in time before the system goes down. Otherwise that clients will never know till much later he has lost what every it is he looses.
I've just spent months rebuilding my site from WebForms to Razor pages. Now. . . I mean, at what point do I step off the merry-go-round of new technologies and invest time in developing a full project using a single technology?
It's not about the technology you use. It's about your website's requirements. If your website is a simple static page, Webforms would be sufficient lol. Here at my company we are still using webforms. :)
I'd imagine that the browser would cache the runtimes on the first hit, so subsequent hits would only need to download the application dll when it changes. That said, Dan did mention that they're working on shrinking it down. I imagine it will be better by the time it ships.
nordy2010 can’t remember what he said exactly, but I think he mentioned 5MB? That’s too large for anything outside an internal business app. I’m excited by the tech but an entire site (plus runtime) will need to be under 500KB
@@macwilko Oh, agreed, they have a ways to go. And it'll be a while, if ever, before this tech is a true competitor to React/Angular/Vue. That said, there's an effort being done right now to tree shake the .NET framework, similar to how Webpack tree shakes. If they can get that in place, then we might have a truly useful platform in Blazor.
I love the idea behind the project, but I could imagine that you could quickly get performance problems with it. As far as I understand it, the actual application is interpreted by a .NET interpreter, which is interpreted by the browser in webassembly.
Lets say I have a website that has 50+ unique pages for various tasks, does the client browser download the .wasm for the 50+ page? or does the client only what pages it download?
Very nice Daniel. You may be able, however to help with the hard time I am having discussing these concepts with fellow developers when the terminology is still being thrown around inconsistantly. You are calling the server side "Razor Components" and the client side, still in preview "Blazor". This is a contradiction when a developer sets out to create a new project in the 3.0 release of this current week and finds themself having to choose "Blazor (server side)" in order to create a new solution. Should that not say "Razor Components (server side)"?
It reminds me of the fullstack JS frameworks like Meteor... But with more cruft. I'm unlikely to switch as it doesn't offer anything to people who haven't already heavily invested in C#/.NET. But it's good to see the interop is increasing so if I ever have to deal with this stuff it won't be the end of the world. For those who only/heavily use Microsoft stuff this could be quite useful, especially for RAD of organisation-specific tools. This is waaay better than Silverlight especially in the modern age where mobile devices are super popular and nobody is gonna go install your dumbass runtime. Lots of the comments below are jumping to conclusions so I'd encourage people to do their own research.
With server-side Blazor, how many concurrent connections can SignalR handle? In the past, I've read multiple servers facilitating a backplane is necessary to handle thousands of concurrent SignalR connects. Will there be the same limitations and workaround with server-side Blazor?
So, you are telling me that I will send each UI change occuring on client side to my server? otherwise I will have to build the other solution that would force all my clients to download my .NET code over to their side in the cache memory? Why?
I think what is sent to the server are the events/messages. The server makes a dif of the DOM and then sends only the changes to the DOM. I would think of this like a Terminal Server.
