How to create Blazor webassembly and server apps in visual studio code

Painful memories of ActiveX controls, java applets, Silverlight, Flash and the other attempts at portable code are all being revenged by WebAssembly. I don't care how good someone is at JavaScript. They will make more mistakes (especially subtle, hard-to-find bugs) in JavaScript than they would doing the same task in C#. Every time. Blazor with WebAssembly is mature now to the point of being very useful. The great thing about WebAssembly is that it is a standard, unlike ActiveX or Silverlight.

 Here are the steps to create either a Blazor WebAssembly or a Blazor Server app in Visual Studio Code:

From a command shell:

dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.2.0-preview1.20073.1

1. Install Visual Studio Code, if not already installed.
2. Install the latest C# for Visual Studio Code extension.
3. For a Blazor WebAssembly experience, execute the following command in a command shell:

dotnet new blazorwasm -o WebApplication1

You can do the above from a command shell at the C:\ location. WebApplication1 will be the name of the project folder created.

For a Blazor Server experience, execute the following command in a command shell:

dotnet new blazorserver -o WebApplication1

 Open the WebApplication1 folder in Visual Studio Code.

For a Blazor Server project, the IDE requests that you add assets to build and debug the project. Select Yes.

If using a Blazor Server app, run the app using the Visual Studio Code debugger. If using a Blazor WebAssembly app, execute dotnet run from the app's project folder.

In a browser, navigate to https://localhost:5001.

That's it. From here you can add services, model classes, and custom assets. The "Stock" Project that is created with the above will have several features that you can examine to get off to a good start.



Comments

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

IE7 - Vista: "Internet Explorer has stopped Working"

Image
This one was a bitch. All of a sudden for no reason at all, out of the blue, I get this dialog "internet Explorer has stopped working". I didn't install any new software, crap- I didn't do anything! So here I am using FIREFART to go on the internet and find out what to do! Damn! Good thing I've got the sucker on the same machine (I'm not "anti-Firefox", i just don't use it that much except to check my page renderings). The Fix The fix (at least for me): 1) Go into Control Panel, and choose "Internet Options". 2) Under the "Advanced" tab, press the "RESET" button at the lower right: Don't ask me why this happens, or why the fix works. That's a BUG, D00D - I don't care how you slice it!
Read more

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more