Entity Framework Core code samples for moving away from conventional data operations

Spending years in various forums answering questions what is surprising is Windows Form developers (both newcomers and season coders) are still using TableAdapter, DataAdapter or connection and command objects to interact with databases. A case may be made for each of these but they are not going to work well when considering cross platform, web solutions and in general rich user interfaces.

When the chance presents itself I will suggest trying EF or EF Core and the response typically is something along the lines of "I'm just building a simple application" or similar response then sometime later that simple application has grown considerably and now warrants looking at EF or EF Core. In many cases it's too late or they just want to get the application done quickly.

So over the past year I've been writing code samples to target Windows Forms developers. The downside is limited time to have a well rounded set of code samples. The goal is to start out simple with common operations covered then move to various design patterns which can then offer moving to WPF and cross platform solutions.

The following GitHub repository is the home of these C# code samples, as mentioned this is just the start. Also have another repository which is part of the goal to work developers into EF Core.

The database used is a updated version of Microsoft NorthWind database which over time will be modified as needed while currently the tables are broken out more then the original and several important keys and indexes have been added.




Comments

Post a Comment

Popular posts from this blog

VB.NET Working with Delegate and Events

Introduction From hobbyist to seasoned developers delegates are avoided or attempts are made to understand them, which in many cases is met with frustration. I see questions on various forums where code could be refactored by using delegates and when making suggestions to use delegates generally the response is something like “that is over my head, what I have works!”. Well just because code works does not mean there is room for refactoring. Search the Internet for VB.NET delegates and find out there are an abundance of post while the majority are not fully working examples and may be untested which can lead back to frustration. The first mistake some coders make is not reading Microsoft documentation on delegates or think outside the box and study C# code samples and a decent C# to Visual Basic converter as there are more code samples in C# than Visual Basic. One must understand that there are cases like with MulticastDelegate class there is syntactic difference on how to use them ...
Read more

Coders asking questions in online forums

 Something I've noticed over the years answering questions on various forums is They want someone to adjust their code which is in many cases complete off-base They want simple where simple is not always the case or that what they believe is hard in regards to me supplying a code solution that I see as simple. My solution usually will become simple only if they invest time to study the code rather than look at it and say jess that is over my head. What can be done?  There needs to be for instance a better way to direct these coders to content on the web starting with Microsoft code examples e.g. for C# for instance , Pluralsight, Microsoft TechNet. Where to place this? Perhaps on startup pages for Visual Studio and Visual Studio Code. Coders need to have an incentive to be better and that can only happen with placing learning pages where they are easy to locate and for community leaders e.g. MVP's for instance to stop providing code that works with things like one character va...
Read more

Sometimes VB.NET coders make me wonder (or crazy)

 The following was taken from a die hard VB.NET coder. I believe C# promotes bloated, slow, inefficient, and buggy code, largely in part because people care more about the cosmetics of their code than they do its actual functionality, efficiency, and reusability. Wow, that is one broad stereotype while I've seen more VB.NET write really poor code more than I've seen C# developer and I'm a proponent for VB.NET coders but not for those who think the way as the above person. No matter what language a person works with there are both bad and good coders while from what I've seen between VB.NET and C# from non professionals VB.NET coders are those who tend to write unclean and loose code while for the most part C# coders that are not working professionally really can write sloppy code as a VB.NET coders does simply because a VB.NET coder can turn Option Strict Off or actually never turn it on. Then there is this "Minimization is heard more with coders using VB.NET then ...
Read more