Blazor is a new experimental web UI framework from the ASP.NET team that aims to brings .NET applications into all browsers (including mobile) via WebAssembly. It allows you to build true full-stack .NET applications, sharing code across server and client, with no need for transpilation or plugins.
why Microsoft does not keep nomenclature same as previous versions ??? like why main.cshtml instead of _layout.cshtml, why @inject instead of using, why typescript has different signature to declare variables than the c#, why not mvc like structure instead of new 3 projects in Blazor ??? fade up with new rules and syntaxes, structures every time...
It would be great if Microsoft could maintain similarity from its previous successful technologies so that one should not spend time learning structure, syntax every time Microsoft comes up with new thing.. Thanks
Microsoft, if you read this, please bring this out of experimental and to a full committed project. This is the most amazing thing coming from Microsoft in years. Finally we can completely commit to MS tech stack and be free from the front end stupidity of a new JS library every week. Do this please and give it all you've got. Help your loyalists army. I'll happily rewrite my entire front end if I have this. Blazor! maybe a better name wouldn't hurt by the way. And this is the ultimate answer to JS security (or complete lack of). OMG I hope we have something in 2019.
I believe the JS file is there simply to enable fallback to ASM.js. When more people start updating their browsers and we're sure that pretty much everyone has WebAssembly support in their browser, we can scrap the JS fallback, and as such, get rid of the JS file. So it's either serve a 1MB JS file to access a wider audience, or limit it to users who have WebAssembly support.
Yes please keep developing Blazor and make it production ready. I can see this massively increasing productivity in developing web applications, using the same tech on the front and back end, sharing libraries between the front and back and so on. This is exciting, I believe it is the future. Also longer term is there is a nifty way to compile precisely the same app into a native phone and native desktop app without the bloat of Electron / Cordova etc. that would help small teams who want to branch out into different platforms who don't have the resources to do it all.
noones used MS for web tech since the 2002 when anyone sensible avoided webforms like the plague for obvious reasons, why on earth would anyone use this now, when it does less than angular and the likes, its typical MS, coming to the game late, and offering less.
This is very powerful. Please make it a shipping product. Silverlight was an addon and that why it did not work out, blazor is a seamless integration through WebAssembly. It's a brilliant and amazing idea. Please ship it !!!!
Apple is NOT going to like this! This is a new way to deliver applications over the web to any device. From within that single page, you can have a multi-page app, you can render anything you desire... this is Silverlight without WPF/e.
Next stop after this matures is to deliver additional markup, i.e. XAML, which would give developers HTML, XAML or Razor to work with... choose your poison :)
While it won't destroy the App Store concept, it should give it some serious competition. Heck, developers may even be able to finally make some money off of their apps.
Erhmmm.. really like Blazor, but I dislike the fact the entire assembly for the web application itself is served in a shiny golden tray right to the client's hand... and then someone gets DnSpy opens it up and he/she has the entire source code, of course, a little different and unorthodox from the "regular" desktop assembly, but for my understanding, Blazor provides no security at all to aid the protection of company trade secrets and private assets, else I would love someone to prove me wrong here.
Just found this out, from Sandersons Blog: http://blog.stevensanderson.com/2018/02/06/blazor-intro/
In interpreted mode, the Mono runtime itself is compiled to WebAssembly, but your .NET assembly files are not.
In AOT mode, your application’s .NET assemblies are transformed to pure WebAssembly binaries at build time. At runtime, there’s no interpretation
If you want to see one of the state libraries Steve mentioned then take a look at this project. The samples convert the built-in samples to a Flux/Redux type pattern, but without any boilerplate code (no switch statements in reducers, no having to create state/reducer maps, etc) - https://mrpmorris.github.io/blazor-fluxor/
C# is definitely better than the jumbled mess of JS, but the feasibility of a truly good web app is performance (in terms of responsible DOM updates and rendering, not file size). If Blazor can intuitively utilize the really modern techniques done in JS with requestAnimationFrame(), ShadowDOMs for rendering, and Worker threads for processing, then there would be every reason to use it.
If Microsoft made a product like VS Code (an outstanding web-based app) using Blazor, I'd be completely sold.
Blazor is the best thing that MS is doing in the web space, better even that Typescript, because it allows C# to run from cloud to web-server (if any) to browser. So, we can finally share business domain logic across those layers, plus taking full advantage of the .NET standard features.
I loved Silverlight [which became officially Windows 8/10] but this Blazor is going to top SL.
[MSFT] Please make it an official product, so we can build advance apps.
Also, give us Lazy page loading, so if the app has 100 pages, it doesn't load ALL the pages up front. And once a page is loaded, it should stay in an internal Page cache for future calls.
1) armoring against browser and JS ecosystem is nonsense
2) Blazor has 5 years of big development to go, before it can be usable.. Browser is not desktop, they are totally different environments.. JS SPA's frameworks are developer by 50+ members team (community) and for several years... they headed so many problems they have already solved and Blazor has to solve too - like server rendering, code minification, effective change detection, shadow/virtual dom...
In the last few years, Microsoft has made good decisions.
When we were switching to Node.js, they created ASP.NET Core.
Now, we have to choose the SPA JS Framework, they create Blazor.
I want it.
Yet I do have some questions about it.
- Is there (or will there be) a way to extract C# declarations (for example methods) from the .cshtml ?
- What version of C# can we use ?
- When is the blazor library downloaded ? First page or first call ?
Nah. You ignore all the bad things MS came up with and how they threw rocks into the gears of better projects. Bad or dropped tech: Silverlight. Windows Mobile. Visual Basic. VB Script. I could go on.. and you know it's true. And many other products are just layers upon layers built upon a rotten core. Take Windows for example.
Blazor allows you to manipulate the DOM using Blazor components - they render a UI tree that is compared to the previous version, and the changes are then applied to the DOM.
You also can still use any JS library and call them from Blazor - documentation for that isn't quite there, but examples of JS interop for Blazor are out there.
C# 7.3 Is what they're currently using.
The other questions I don't yet know the answer to.
Mineral purifiers naturally sanitize the water while keeping the amount of chemical additives to a minimum, saving time and money.
Chlorine - most common type of cleaning system Frog - Mineral based system that helps reduce amount of needed chlorine Nature 2 - Mineral based system that can be combined with salt water systems Salt System - creates chlorine from salt for a less chemical swimming experience Baquacil - Chlorine-free system that is less irritating to eyes and easier on pool liners.
Rising Sun Pools also offers a number of private-label cleaning supplies to keep your pool sparkling. Stop by one of our showrooms for details.
Rising Sun Pools is proud to carry Sundance Spas in-ground hot tubs. See our Hot Tubs section for more information.
Privacy is usually a concern and should incorporate various design elements such as trees, walls, fences, screen, shrubs, gardens or whatever you like that accomplishes your goal.