.NET 6 Startup Changes - Handling Program.cs Without Startup.cs

preview_player
Показать описание


Рекомендации по теме
Комментарии
Автор

Tim, I just wanted to mention that you are an absolute blessing to this community. You're making it so much easier for me and everyone else to get into the new technologies. I only used to do Console and Forms Application, but now I can do (and actually understand!) stuff that I never would have dreamed off. If YouTube never recommended you to me, it would have been very likely that I would have left Software Development a while ago and went somewhere else. Please, never stop what you're doing!

Gramr
Автор

Hi, Tim! Thanks a lot for your videos. Even I'm not an English native speaker, I can understand everything. Your content is very valuable, clear, and well produced.

rodrigo_sparlock
Автор

Even if you are not a native english, you can undrestand videos of Tim with x2 speed, Tim is a legend ! Thank you

aimene_.
Автор

Thanks Tim. I'm grateful when your topics begin with 'let's open Visual Studio and get started.' Being able to demo a topic as close to the default templates as possible means I can follow along from the same starting point. Often times, I find other videos that start right in the middle of something. Sure, the presenter knows their project and topic very well, but often times overlooks something foundational and it's just harder to follow along. So I, for one, always appreciate your format, no matter how large or small the topic.

codefoxtrot
Автор

If i had money, I would send you some, with all this information you are giving us for free. We really love you and pray for you Corey.

codmn
Автор

Thank you Tim. You explain very simply and clearly ❤

sprtybi
Автор

Excellent. Just what I was looking for! 👏👏

davidjnevin
Автор

You are amazing. Thanks for giving us so much knowledge. Greetings from Brazil!

wellingtonsantos
Автор

In dotnet 5 you could omit Main method. In 6.0 it got promoted to be the default way.

guriysamarin
Автор

Hi Tim, Thanks a lot. it was so helpful.

mahsasadat
Автор

OHHHH I was looking for hours for the answer to the Endpoint question ( 13:12 ).. No app.UseEndPoints() wrap necessary in 6.0... THANKS!!!

josephh
Автор

Yes, I really dislike this change, since I just started learning ASP NET Core and this change was annoying, both due to it being a decent change, but also I dislike the new program.cs files. I love my namespaces, classes and methods. Thanks for the video.

rattlehead
Автор

I really like Microsoft's products. However, in my opinion, there's a real challenging (mainly for begginners) to make a project with c# because of this changes. Many tutorials on youtube ended up being outdated. I think this is very annoying and confusing sometimes. Anyway, thank you Tim for all your videos, they are really great.

julionunes
Автор

Hi Tim, will you also start posting your videos to Rumble? I would much rather watch them there.

TysonGibby
Автор

Hi Tim. Great vid, as always. Very informative!

I don't like the way where it is going... what's next? Implicit projects? /:P

Sad-Lemon
Автор

If you already started a project in .net 5 that created startup and program and then upgraded to .net 6. It still keeps those files and runs them like .net5. I guess you would have to manually remove startup and change program.cs then in this case? Is there any benefit or point of doing this other then "this is the new way of doing it" when you upgrade.

chrisjohansson
Автор

Love this vid! Tim, have you done a video on easing the pain of upgrading dotnet versions? If so, share your ways! We're on 3.1 and going to leap all the way to 6.0. The nuget package dependency hell is real.

StephenOwen
Автор

I have this question. I have a Web API at which I want to add a library that makes payments. That library has to call another api, that is the payments api. So that library has to implement HttpClient. The right way to do it is through DI, but DI can only be done at the Startup of the main project which is the Web API but then it's like taking something that belongs to the library and putting it at the Web API. Is it wrong to do it like this, maybe the HttpClient should be at the main project and not the library. Note that other than that the main project does not need to implement HttpClient.

georgevlassis
Автор

Hey Tim, following along your paid C# course and up to mongoDB for the most part up until now I've been just omiting "public/private" etc statements from methods which seem to still allow me to create methods within the program.cs class but the mongodb part is where it became all unstuck for me. So would it be easier if I just create a new class "Controls.cs" and call that straight away from this main program.cs and then put everything else into controls i would otherwise put into main() had I been using .Net 5.
Also side note, my version of VS2022 community (new install) doesn't allow the option of changing down to .Net5 and lower. (unless I select .Net Framework) all core classes are Net6 and the dropdown shows no other options.

GarrattCampton
Автор

Hi Tim thanks for the incredible work you're doing for the community. I wonder if you've ever considered covering .Net MAUI THANKS AGAIN

runtimeterror