Blazor 0.9.0 experimental release now available

Daniel Roth

Blazor 0.9.0 is now available! This release updates Blazor with the Razor Components improvements in .NET Core 3.0 Preview 3.

New Razor Component improvements now available to Blazor apps:

  • Improved event handling
  • Forms & validation

Checkout the ASP.NET Core 3.0 Preview 3 announcement for details on these improvements. See also the Blazor 0.9.0 release notes for additional details.

Note: The Blazor templates have not been updated to use the new .razor file extension for Razor Components in this release. This update will be done in a future release.

Get Blazor 0.9.0

To get started with Blazor 0.9.0 install the following:

  1. .NET Core 3.0 Preview 3 SDK (3.0.100-preview3-010431)
  2. Visual Studio 2019 (Preview 4 or later) with the ASP.NET and web development workload selected.
  3. The latest Blazor extension from the Visual Studio Marketplace.
  4. The Blazor templates on the command-line:

    dotnet new -i Microsoft.AspNetCore.Blazor.Templates::0.9.0-preview3-19154-02
    

You can find getting started instructions, docs, and tutorials for Blazor at https://blazor.net.

Upgrade to Blazor 0.9.0

To upgrade your existing Blazor apps to Blazor 0.9.0 first make sure you’ve installed the prerequisites listed above.

To upgrade a Blazor 0.8.0 project to 0.9.0:

  • Update the Blazor packages and .NET CLI tool references to 0.9.0-preview3-19154-02.
  • Update the remaining Microsoft.AspNetCore.* packages to 3.0.0-preview3-19153-02.
  • Remove any usage of JSRuntime.Current and instead use dependency injection to get the current IJSRuntime instance and pass it through to where it is needed.

Give feedback

We hope you enjoy this latest preview release of Blazor. As with previous releases, your feedback is important to us. If you run into issues or have questions while trying out Blazor, file issues on GitHub. You can also chat with us and the Blazor community on Gitter if you get stuck or to share how Blazor is working for you. After you’ve tried out Blazor for a while please let us know what you think by taking our in-product survey. Click the survey link shown on the app home page when running one of the Blazor project templates:

Blazor survey

Thanks for trying out Blazor!

34 comments

Discussion is closed. Login to edit/delete existing comments.

  • David Bond 0

    We have been using the experimental Blazor builds for a while and we are now ready to start work on our new UI using Blazor in parallel with our production UI.  Very excited to be able to develop full stack using C#.
    Thank you all, and do keep up the great work!

  • Jan Hjørdie 0

    Will Blazor end up as a real project ?It looks very promising, but will not invest time in it if it just stay in as experimental

  • Colin Mills 0

    Template app crashes on startup. What am I doing wrong? Can see this in event viewer:
    “Could not find inprocess request handler. Captured output from invoking hostfxr: No executable found matching command “dotnet-blazor”. ”
    I can see the blazor nugets are installed on the project. Do I need something else?

  • Carl Philipp Bickmeier 0

    I had some smal problems proting my 0.7 project to 0.8… but when I try to port 0.8 to 0.9 it does not work at all… I have to use a controller to load some data adhoc and until 0.8 I was able to add the aspnet.core.mvc nuget. When adding this nuget to a 0.9 project it does not start and reports “rcz generate exited with code 1″… what am I doing wrong? Is it still possible to use controllers in 0.9? And if yes, how can I do that?

  • Carl Philipp Bickmeier 0

    In Blazor 0.8 the wwwRoot folder moved from the app project to the server project… when I create a new project with blazorhostet template under blazor 0.9 the wwroot folder is back in the client… is that correct?

  • almir tuca 0

    With this new version, do we need to restart the app each time html is changed in order to see the changes?

  • Ben Hayat 0

    Hi Dan;

    Since Blazor’s status (the client side technlogy running in WA) is still considered as “Experimental”, my question is, what hurdle does Microsoft need to pass [successfully] to change the status to “Go” status, that we know we are going to be getting the real client Blazor?

    Thanks!
    ..Ben

  • Christian Andersen 0

    I am quite new to Microsoft web development and therefore my problem might be a problem that is not a problem for others. Anyway, after I upgraded to version 0.9 from version 0.8 I got at a weird error which took me quite some time to solve. I have made a rest crud interface to use Elasticsearch as “data storage” and search engine for the application. When I call the “GetAll()” function and the list which I return it worked fine with version 0.8 but now i have to limit the size of the list to a limited amount. I am not sure where this error lies if it’s a .Net Core 3.0 error, me having to configure the server correct or a Blazor problem.I get this error in the browser when the call is done: Failed to load resource: the server responded with a status of 500 (Internal Server Error)
    When I call the URL directly I get some kind of binary result on the browser screens something like this:
    !�������@�Q��j�dxF��{��GD�WV
    I had problems finding this bug, during my many years of software development I experienced “too long lists” problems but I did not expect this could happen during a release. Is there’s something I can configure in order to be able to receive lager lists?
     
    I am using the Client Server solution template from visual studio and it seems that after the upgrade the size of the list which I return to 

  • Christian Andersen 0

    I am quite new to Microsoft web development and therefore my problem might be a problem that is not a problem for others. Anyway, after I upgraded to version 0.9 from version 0.8 I got at a weird error which took me quite some time to solve. I have made a rest crud interface to use Elasticsearch as “data storage” and search engine for the application. When I call the “GetAll()” function to return the list, it worked fine with version 0.8 but now I have to limit the size of the list to a limited amount to avoid this problem. I am not sure where this error lies if it’s a .Net Core 3.0 error, me having to configure the server correct or a Blazor problem.I get this error in the browser when the call is done: Failed to load resource: the server responded with a status of 500 (Internal Server Error)
    When I call the URL directly I get some kind of binary result on the browser screens something like this:
    !�������@�Q��j�dxF��{��GD�WV
    I had problems finding this bug, during my many years of software development I experienced “too long lists” problems but I did not expect this could happen during a release. Is there’s something I can configure in order to be able to receive lager lists?
     
    I am using the Client Server solution template from visual studio and it seems that after the upgrade the size of the list which I return to 

  • Ben Hayat 0

    Is there a plan to “sort of” bypass the current Mono VM and compile C#/.Net directly to Wasm code, so we won’t have Mono VM running inside of Wasm VM? Having the legacy Mono in this solution, will hurt the acceptance of Blazor. Mono needs to be put to sleep. 🙂

Feedback usabilla icon