50 Things You've Been Doing Wrong in C# and .NET Core
Course
Online
Description
-
Type
Course
-
Methodology
Online
-
Start date
Different dates available
Avoid common C# mistakes to improve your apps' productivity.Professional software development involves many different skills. As a C# developer, you must be skilled in the C# language and the .NET Core runtime. With this course, you'll take your C# and .NET Core skills to the next level by avoiding common mistakes when coding, using design patterns, developing microservices, persisting your data, securing your application, and even debugging problems.Learning the basics of a language or platform can easily be done by following a course/book and with some hands-on practice. The path to becoming a software developer encounters many edge cases. During this course, you'll learn from my hard-earned experience, garnered from real-life situations, regarding the C# language and .NET platform. You can take this course as a vaccination against future coding infections!By the time you finish this course, you will have developed your skills to "sniff out" coding issues effectively and avoid mistakes. Whatever your issues, the aim of this course is to take you to the 'Bring it on!' point when it comes to solving your .NET and C# problems.Please note that this course assumes familiarity with C#, .NET Core, and ASP.NET Core, together with Visual Studio (2017 or 2019).About the AuthorOnur Gumus works as a lead software engineer in Dubai UAE. He has 15 years of experience in .NET and web development. He is a functional programming enthusiast and has completed many large projects with ASP.NET.
Facilities
Location
Start date
Start date
About this course
Deeply understand popular data structures (such as lists, arrays, LinkedList, HashSet, and dictionaries) and use the most efficient one depending on the problem you are trying to solve
Persist your data to a database properly by learning about efficiency and concurrency aspects when using the Entity framework
How to use HTTP verbs, and HttpClient properly, and classify your resources appropriately
Why circular dependencies are bad and how to avoid chatty traffic, eventually leading to more robust microservices
How to use SOLID principles the right way with improved code quality and readability
Identify and fix common programming problems with proven design patterns
Effectively debug, design, and secure your code
Navigate the complicated world of microservices and deliver robust RESTful APIs that follow the best industry standards
Reviews
This centre's achievements
All courses are up to date
The average rating is higher than 3.7
More than 50 reviews in the last 12 months
This centre has featured on Emagister for 4 years
Subjects
- ASP
- ASP training
- C language
- ASP net training
Course programme
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Understand how references are passed by
- Observe assigning a reference doesn't change the actual reference
- Use ref keyword to modify the original reference
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Create a disposable object
- Dispose it
- Observe if the object is still alive
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Override Equals properly
- Override GetHashCode properly
- Understand GetHashCode doesn't have to be unique
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Spot the exception location
- Move as high as possible in the call stack
- Add exception handling if necessary or consider not implementing handling at all
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Create a virtual method
- Override in the derived method
- Observe regardless the reference type the actual object's method is called
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Always observe the warnings
- Either suppress or fix them
- Without existing warnings new warnings will easily take your attention
- Understand SOLID is append only
- Show examples of violation
- Move the change to outer layers
Additional information
50 Things You've Been Doing Wrong in C# and .NET Core