2017: baby developer watching every single video of your channel to learn how to do stuff 2024: omg it seems like i cant debug thank you tim ❤ you never disappoint
Tim, you wizard! I've been using Visual Studio since VS 2008 and you just taught me stuff. I've used conditional breakpoints, but seemingly never explored the rest of those features.
Thanks for the vid. I've been already using about 50-60% of this. Recently I discovered the breakpoint groups and found them kind of helpful even though haven't used them anywhere yet :D Now I have a clearer picture of why they might be helpful and where to use them.
Function breakpoints are great when you want to break in an assembly that you haven't loaded the code for. Combined with Visual Studio built in decompile, very fast on huge projects.
Excellent video. I always name my Azure Functions 'Run'. A functional breakpoint working across solutions would be awesome for those. Not sure if that is possible without export/import, though.
This Is Really an Amazing Lesson And important As well , i only Use The Normal Breakpionts But Today i Learn That There A Lot To Solve Usng This Futures Of Multiple Breakpionts Thank You For This Amazing Video ✅✅ Iwill Save This Video For The Future scenarios because Right Now Im Still In The Entry-level
Hello Tim, While upgrading an app from .NET 5 to .NET 8 , I started getting errors in my code. Long story short, it ended up that I had script debugging turned on. When I turned it off, the app ran fine. The error occurred when it was trying to render a shtml page using pull down menus from a database. The breakpoints didn’t make it clear why this problem occurred.
This is embarrassing to admit, but I've been developing for decades and have just been using basic breakpoints. Thanks for the level up!
I am glad it was helpful.
Haha, same here. But basic breakpoints does the job. =)
2017: baby developer watching every single video of your channel to learn how to do stuff
2024: omg it seems like i cant debug
thank you tim ❤ you never disappoint
I'm glad it was helpful.
Tim, you wizard! I've been using Visual Studio since VS 2008 and you just taught me stuff. I've used conditional breakpoints, but seemingly never explored the rest of those features.
I am glad it was helpful.
Thanks for the vid. I've been already using about 50-60% of this.
Recently I discovered the breakpoint groups and found them kind of helpful even though haven't used them anywhere yet :D Now I have a clearer picture of why they might be helpful and where to use them.
I am glad it was helpful.
Thank you Tim.The import/export breakpoint feature is awesome. To be honest i was not aware of that feature ever exist in VS.
I am glad it was helpful.
I can't even count the hours that conditional breakpoints have saved me. It's something that everyone should know!
Agreed!
Tim, you are magician) Thank you for this tutorial
You are welcome.
Most useful for beginners🎉
Thanks!
This becomes even more powerful when is combined with DebuggerDisplay attributes
Thanks for sharing!
Function breakpoints are great when you want to break in an assembly that you haven't loaded the code for. Combined with Visual Studio built in decompile, very fast on huge projects.
Thanks for sharing!
A video on dependency injection, ioc containers, and the composition root would be very appreciated.
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/
Excellent video. I always name my Azure Functions 'Run'. A functional breakpoint working across solutions would be awesome for those. Not sure if that is possible without export/import, though.
That's an interesting idea. You would need to export and import them, though.
This Is Really an Amazing Lesson And important As well , i only Use The Normal Breakpionts But Today i Learn That There A Lot To Solve Usng This Futures Of Multiple Breakpionts Thank You For This Amazing Video ✅✅
Iwill Save This Video For The Future scenarios because Right Now Im Still In The Entry-level
I am glad it was helpful.
Hello Tim, While upgrading an app from .NET 5 to .NET 8 , I started getting errors in my code. Long story short, it ended up that I had script debugging turned on. When I turned it off, the app ran fine. The error occurred when it was trying to render a shtml page using pull down menus from a database. The breakpoints didn’t make it clear why this problem occurred.
Script debugging is tricky, because scripts often have bugs that are just passed over. The web can be a messy place.
Is the best practice to leave it on or off?
I'd leave it off typically until you need it.