Should I Focus on Blazor or ASP.NET Core? 

You are welcome.

Thanks!

Thank you!

Hopefully I don't meet my Waterloo.

@@IAmTimCorey never!

@@IAmTimCorey Don't take care Wellington understand you much more then Napoleon and know nothing about independence day.

You are welcome.

You are welcome.

You're very welcome!

You are welcome.

Thank you!

You are welcome.

You are welcome!

You are welcome.

You are welcome.

You are welcome!

You are welcome.

You are welcome.

You are welcome.

Sounds like you are adding your vote to this suggestion: suggestions.iamtimcorey.com/Details/61e417e877661323eea88f4c

Thank you!

ASP.NET Core has hot reload when developing now, so you can see your changes immediately.

You could do that in just about any of the C# web project types. So it is up to you to evaluate all five and figure out which one is best for your specific situation.

Coming very soon, although the C# Mastercourse is the easiest path: www.iamtimcorey.com/courses/csharpmastercourse.html

The difference is how you are learning them. If you are learning them on your own and one at a time, that's the order to learn them in. The reason why is because you will get the most value out of your training in the quickest amount of time. If you only have time to learn one, you will learn the most valuable one (API). If you only have time to learn two, you will have learned the most valuable two (API and Blazor). With the C# Mastercourse, I designed it to give you a good overview of all of the major project types. Since we were covering all of them, I covered them in the order that was the most logical, where we could learn in a way that built upon what we had already learned.

@@IAmTimCorey Thank you for the clarification :)

I'm not sure what that means.

I like Blazor's ability to make a custom element like

@@IAmTimCorey I might have to redo the sight I am working on for my friend in blazor, is it more secured then MVC out the back?

Both are equally secure because they are both server-side project types and they both are built upon ASP.NET Core.

Thank you!

It could be, but there is a LOT to consider there.

@@IAmTimCorey My fear is for SignalR, but I'm very focused on Blazor. Seriously thought about taking a chance lol

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

It depends. Do you have a deep knowledge of C# and React and JavaScript? If so, then it can be a great option. If you know React and JavaScript ok, but not great, then it usually is not a great idea.

That's not really something that I can do. The reason why is because this is an advice video. It isn't on a specific learning path. For instance, you could have 20 years of experience in C#, but you might never have used ASP.NET Core. So, this video might be right for you, but you aren't a beginner. You could argue that it is for if you are a beginner in these technologies, but you might be an expert in ASP.NET Core MVC but you might never have used Blazor Server.

My suggestion site is powered by Blazor Server (suggestions.iamtimcorey.com) and I show you how to build it in the Suggestion Site App course here on RU-vid: ru-vid.com/group/PLLWMQd6PeGY0cZFMqx5ijmdaD87sJKCsU If you want the source code and don't want to follow along with every video to build it, I do sell this as a course as well: www.iamtimcorey.com/salespage.html?course=bi-ssa-01

We do that in the TimCo Retail Manager course near the end when we add Blazor. That would be a good option for a stand-alone video as well.

@@IAmTimCorey I'll Go check that out ❤😊👍

Actually he shared. You can check his old contents.

@@cemkaya4448 thanks.. ..if possible can you share the link pls?👍

One is coming. In the meantime, if you want to be a C# web developer, you need to know C#. If you are not fully confident in that, start with the C# Mastercourse. Either way, after that I would recommend the Foundation in Web Development course. After that, the Getting Started with ASP.NET Core course. Finally, pick the topics you want to go deeper in (Blazor Server, API, etc.) Here are the links for you: * C# Mastercourse: www.iamtimcorey.com/p/c-mastercourse * Foundation in Web Development: www.iamtimcorey.com/p/foundation-web-development * Getting Started with ASP.NET Core: www.iamtimcorey.com/p/getting-started-with-aspnetcore * Blazor Server In Depth: www.iamtimcorey.com/p/blazor-server-in-depth * API course coming soon If you aren't planning on taking the courses, you can use the course outlines to see what content is included so that you can get that content from other places in the right order.

@@IAmTimCorey thanks tim..I have already finished c# master course.. let me plan further as per your suggestions.. thank you very much..

@@IAmTimCorey i want to buy the Getting started with asp.net core but after the release of .net6 is your course out dated ? or there is no changes ?

The first time any web server launches, it has to do a lot of work. That's why one of the tasks that you should do after deploying a website is test the site. That way, you are the one that experiences that slow load. After that, the server is up and running and is set to respond quickly.

@@IAmTimCorey Dear Tim my biggest issue is the start up page it is too slow but once the app has loaded it's generally super fast for general use (e.g. navigating between pages), is it because the performance in Blazor WASM has always been slow when compared to a JavaScript app

No, not unless you have a REALLY slow internet connection. For instance, just loading this videos web page (the one you are on right now) and playing just the intro of the video, you will load about 70MB. A Blazor WebAssembly project will be 2MB or less unless you have a massive application. It could be how you are trying to load the initial data (or how much data you are loading). Open up the developer tools in your browser and watch what data downloads and what is the blocking action. Also, remember that WebAssembly is JavaScript. Blazor WebAssembly just downloads a small (less than 2MB) dll file to be run by WebAssembly.

@@youssefkassem9032 Hi, Youssef. IF your application is large, try breaking things down according to typical first usage, startup, etc., combine into separate assemblies, then mark all but those require for startup and priority functions for lazy loading per this MS doc: docs.microsoft.com/en-us/aspnet/core/blazor/webassembly-lazy-load-assemblies?view=aspnetcore-6.0

They are. You just can't concentrate on two things at the same time. You have to prioritize learning one and then move on to the next. There are actually five web project types in ASP.NET Core to learn.

@@IAmTimCorey Which ones?

I'm not seeing it, but thanks for the heads up.

@@IAmTimCorey Is small !

Of course. If you are using Blazor, you don't need MVC.

Yep, they can be confusing.

Sounds good.

does wasm have service workers? slow internet -> bad experience either way

@@johnsuckher3037 Yes it does. You can also enable PWA on it

That's going to be tricky no matter what you choose. If you choose Blazor WASM, you will have a larger page load at the beginning, which might be disrupted or timeout because of connectivity issues. You will need to play around with different options and see what works best for your situation. Maybe Razor Pages is the best option for you. You don't get the client-side interactivity, but you get fast page loads, which means less possible disruptions. I would be interested in if you have tested Blazor side by side with other page types, though. You mentioned load delays and slow UI. That isn't a problem with Blazor. That's an issue with slow connectivity. A Blazor-specific issue would be if the SignalR connection was dropped and not re-connected. A slow page load means you are having trouble getting data from the server. That's going to happen no matter what web project type you choose. Even a PWA will have slowness in that case. In fact, it will actually be a bit slower than Blazor Server, since a PWA asks for JSON data, which is larger than the data transmitted over SignalR. The only difference is that the PWA can work offline, but that only matters if you are truly offline and not just slow.

By time your application is ready, maybe the internet connection has improved. Be optimistic. You put a rush on enforcing a faster internet, by building apps needing a faster internet. Users need to complain about the internet, in order to force phone companies or the gov. to improve it. Just be sure they don't complain about your app ;-)

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

Thanks!

It has its place, but that place has been greatly reduced with all of the other options we have now.

Great!

Thanks.

In theory, that's true, but in practice I disagree. If you ask the same question repeatedly even after getting the answer, that is probably a stupid question. You didn't learn from the first few times you asked and asking it again will get people frustrated at you.

Close. I just pulled it all out debugging my own code.

Glad you got value out of the video.

ehh mvc, blazor/front-end frameworks, razor have different thoughts behind it. you learn asp net core by building with any of those... razor is the most beginner friendly if you don't start behind the scenes talk with backend with ajax... you can't learn to drive a car without sitting in one

That doesn't seem like a very good analogy. It seems like you are under the impression that in order to learn something, it needs to be "big" (I'm assuming that means that lots of companies are asking for developers in that subject). By that measure, your best bet would be to learn PHP. It's huge! It isn't the future, but there are hundreds of thousands of jobs for it. Blazor is relatively new, so you won't see it mentioned as much. However, it is the better choice for a lot of situations for new web development. That's what we are discussing here. Not what was chosen ten years ago by companies who are now looking for new employees. We are talking about what you should focus on when building a new application and for building up your new skills. You should learn all five web project types. You mentioned that you should learn ASP.NET Core. Did you know that both Blazors run on ASP.NET Core? No matter which one you learn first, you are learning the foundation for all of them. With your illustration, it sounds like you are looking at a toolbox and saying "Why should I have a screwdriver? I already have a hammer." and then throwing out the screwdriver.

Oh boy, have you actually written anything with Blazor? It's pretty amazing really...

what? why? theres no limits for .net / C#

I'm not sure you understand C#. For example, it seems like you are implying that C# is limited to Microsoft products. That is not true and hasn't been true for years. For instance, just with the templates provided by Microsoft, we can write applications for Windows, Mac, Linux, iOS, Android, the web, any cloud, Tizen, IoT, Xbox, and more. The biggest area where Microsoft templates don't take you is the Linux desktop. For that, you can use the free library Uno to do so. On the web, there are client-side applications, server-side applications, and even an application type that has the best of both worlds (something I'm not sure anyone else does - have a server-side app that also acts like a client-side app without being two different projects). With the same code, I can write an app for any platform, natively or with a wrapper (like Electron does). How exactly is C# limited? Oh, you also mentioned "price limits". I'm assuming you mean that everything isn't free. Visual Studio, the main IDE for C#, is free for everyone without limitations as long as your company makes less than $1 million per year. If you work for a company that does more than that, you have to pay, but only if you are doing company work. If you are doing personal work, that $1 million cap would be for your salary. That version is basically the same as the Professional edition. It isn't cut-rate or less than. It is what I use for both professional development and for all of my demos here on RU-vid. That works both on Windows and Mac. If you don't like that, you can use VSCode (provided for free by Microsoft) on any platform (including the web). Just to round out this conversation, since it seems you might have not been tracking Microsoft for a while, here are some other things that Microsoft provides: * Private repos on GitHub - this is something Microsoft added when they bought GitHub and then expanded on. They also provide GitHub Actions for CI/CD in a limited capacity. * 12 Azure Services for life - for example, you can host 10 websites, 1 NoSQL database, tons of Azure Functions (up to 1 million calls per month), and a lot more for free plus for the first year, you get even more for free. * Private repos on Azure DevOps with free CI/CD, Boards (issues, Kanban, etc.), package hosting (private hosting, plus replication for NPM, NuGet, and more), and lots more * Open-Source contributions - all of .NET Core, VSCode, major contributions in git, and a lot more To summarize, you can create commercial apps, host them on GitHub, have an automated build and deploy process, and you can deploy your app to any platform in the world all for free. So let me ask you - do you still have the same opinion? If so, why?

wow, completely wrong here...

Please tell us you read Tim's reply.

Wow dude you are so wrong, epicly wrong here... Also java is cancer comapre to c#.