@@francescomantovanelli8774 Thanks, I haven't used it but I'm deciding whether to upgrade a previous webforms project to a new technology. I've used MVC/Razor and it was decent but I can't say MVC was superior in any shape or form, just different. For Blazor, I see a lot of conventions being used in the configuration - MVC is also convention-based and it can be annoying for a developer to figure out what's going as a view automagically matches the controller name. All these settings make it more of a mechanic's job than an engineer's job imo. There's so much markup, and so much plumbing code within markup and I believe I've even seen anonymous inline functions in markup which was pretty impressive and makes you wonder what Microsoft was thinking there :-). Also, the pagelets,controls, partial views, components or whatever name you want to give a razor file, seem very similar to Classic ASP where all the markup and C# code resides on a single page. Is it possible to link a code-behind page to separate the code from the html markup and get dropdowns for handlers etc like webforms did? Do I need to search the entire page to find every handler? Is this the 1990s? :-) Wait, there's a piece of code at the end of the page that clearly affects what's done in the middle of the page. Spaghetti code is back :-) My main issue is that the Blazor developers clearly had a deep-seated dislike for webforms and instead of taking all the good features from webforms and merging them into Blazor to create a state-of-the-art web development platform which webforms deserved as an evolution, they decided to just create a classic ASP/MVC franken-framework. Anyway, it's funny that we've come full circle and revived Classic ASP! From what I've seen, Blazor is a cool retro remaster of Classic ASP.
WOW, migrate web form control into razor is like Philosopher's stone of code
Yeah, it makes you immortal - at least that seems to be how they're selling Blazor :-) Have you used it?
@@techsamurai11 I'm studing Blazor for new project or migrate partial of old webform code. I have dev simple test page, and it seem great.
@@francescomantovanelli8774 Thanks, I haven't used it but I'm deciding whether to upgrade a previous webforms project to a new technology. I've used MVC/Razor and it was decent but I can't say MVC was superior in any shape or form, just different.
For Blazor, I see a lot of conventions being used in the configuration - MVC is also convention-based and it can be annoying for a developer to figure out what's going as a view automagically matches the controller name.
All these settings make it more of a mechanic's job than an engineer's job imo. There's so much markup, and so much plumbing code within markup and I believe I've even seen anonymous inline functions in markup which was pretty impressive and makes you wonder what Microsoft was thinking there :-).
Also, the pagelets,controls, partial views, components or whatever name you want to give a razor file, seem very similar to Classic ASP where all the markup and C# code resides on a single page. Is it possible to link a code-behind page to separate the code from the html markup and get dropdowns for handlers etc like webforms did? Do I need to search the entire page to find every handler? Is this the 1990s? :-) Wait, there's a piece of code at the end of the page that clearly affects what's done in the middle of the page. Spaghetti code is back :-)
My main issue is that the Blazor developers clearly had a deep-seated dislike for webforms and instead of taking all the good features from webforms and merging them into Blazor to create a state-of-the-art web development platform which webforms deserved as an evolution, they decided to just create a classic ASP/MVC franken-framework.
Anyway, it's funny that we've come full circle and revived Classic ASP! From what I've seen, Blazor is a cool retro remaster of Classic ASP.
Why in my IDE not have this option "Migration to Blazor"?
Can i do migration with blazor client ?