The Entity Framework is a fantastic tool that reduces development time on new projects. While it used to take a significant amount of time to write a data access layer, the Entity Framework now handles much of this for you. There are many good reasons to use the Entity Framework, but it requires some care to use properly; poor use can result in substantial performance degradation. I’ve been able to distil the majority of what a developer needs to know about EF performance down to three concepts.
If you would like to learn how to use the version control system Git and you’re currently a Subversion user, this guide is for you. I’ve recently started using Git myself, and coming from Subversion there are several basic concepts and ideas that need to be understood.
Developers who simply lack skill or experience often produce bad code which can become a maintenance nightmare. What’s less often understood is that average or even skilled developers can also easily end up writing bad code if they’re not careful, and there are several key reasons why.
A useful extension method that c# .NET provides is Distinct(). Sometimes you need to get distinct objects by a property of those objects, however, and there is no overload of Distinct() that accepts a lambda expression. Luckily, it’s easy enough to create our own.
The exception message is: This collection already contains an address with scheme http
If you’re like me, when deploying a WCF service to a production site and seeing this error… you’re thinking WTF? Especially knowing it worked in your testing environment.
We’re excited to announce that ElevenWinds has joined the WEtech Alliance.