My name is Ryan and I have been a software developer for almost 20 years now. I started learning programming when I was in grade school, using BASIC to get my feet wet. From there I’ve branched out across several different platforms and languages, and would generally classify myself as a jack of all trades. I tend to stick with Microsoft based platforms but that is mostly due to the volume and types of work available in my area.
I started with .NET programming shortly after .NET 1.0 was released. I have continued to use .NET in various positions and in work I’ve done for fun. I think the platform is quite robust and it helps with overall productivity and I think helps to improve the quality of the code. I am now using features of the .NET 4.5 Framework, including the latest releases of Entity, as well as the new async and parallel task features provided by it.
I put this site up in the hopes of sharing some of the knowledge I’ve gained and will tend to focus on the solutions to problems that really made me work to diagnose and resolve. I’d like to say I’m a very proficient problem solver, but would have to grant some of my effectiveness to the explosive growth of information that is available on various industry websites these days. I hope that putting some of this info in an available, online resource will help more than just me remember how I figured out some of the thornier problems I’ve come across.
If you have any questions, comments or concerns, please feel free to email me @ ryan at dotnetbits.com. Thanks for stopping by!
One Comment
Thank you for this article. I am using Julia Lerman’s most recent book on EF but that is way back with EF4. I am actually using VS2013/EF6. It was interesting to find I had the option of generating “Legacy ObjectContext” which led me to question what the difference was which led me to your post. Excellent! Should I inherit EF code prior to EF6, you have given me a lead on handling the issues you encountered. Good job!