On a positive note - I didnt realize how well supported Mono's implementation of the .net framework is. At least in time we'll all have a home on linux!
I see a lot of very simple one page Blazor examples. How would someone architect a large application that has 50+ displays whereas each display would present itself on a tabbed (MDI style) layout? Oh, and switching between already open tabs would not require rebuilding the content on the tab. In an old WebForms app, we just open each page as a new web page and the build in browser tabs do their job. In this single page world, how does someone mimic that style?
Explain to me how any of that is 'better' than Webforms? It seemed to me like you just showed us how to move one thing over to another thing with no actual 'gain'. 1-1. In fact, it's gone backwards. Since now I'm expected to recreate functionality that just worked out of the box previously. I understand the need for MS to try and stay relevant by coming out with new shinny things. But, at least show us some big leaps forward. Migrating from WebForms to Blazor is a waste of time for anyone trying to actually get work done and solve customer problems.
Oh thank you I thought it was just me. What a mess. It’s fucking mysticism figuring out what will run on server and what runs on client. My current theory that if you make a method return a task it goes to the server, is that right?
On a positive note - I didnt realize how well supported Mono's implementation of the .net framework is. At least in time we'll all have a home on linux!
sweet blazor. I want one
I see a lot of very simple one page Blazor examples. How would someone architect a large application that has 50+ displays whereas each display would present itself on a tabbed (MDI style) layout? Oh, and switching between already open tabs would not require rebuilding the content on the tab. In an old WebForms app, we just open each page as a new web page and the build in browser tabs do their job. In this single page world, how does someone mimic that style?
this dude streams on twitch and has done work on several multipage apps.
Explain to me how any of that is 'better' than Webforms? It seemed to me like you just showed us how to move one thing over to another thing with no actual 'gain'. 1-1. In fact, it's gone backwards. Since now I'm expected to recreate functionality that just worked out of the box previously. I understand the need for MS to try and stay relevant by coming out with new shinny things. But, at least show us some big leaps forward. Migrating from WebForms to Blazor is a waste of time for anyone trying to actually get work done and solve customer problems.
Oh thank you I thought it was just me. What a mess. It’s fucking mysticism figuring out what will run on server and what runs on client. My current theory that if you make a method return a task it goes to the server, is that right?