I've never been a Java programmer. I don't particularly like Eclipse and the 50 million plug-ins that I am not familiar enough to know why I need them. I've come to respect Maven, but that's led me to a much deeper understanding of Nuget and how to use it in a similar fashion with my .Net projects. My learning progress with JBoss has led me to a deeper understanding of some of the decisions Microsoft has made regarding .Net and how to implement the technologies using more reliable techniques. I was recently introduced to IntelliJ, and I feel it shows a lot more promise for implementing the types of back end services projects that we implement.
Which brings me to the point of this blog post (thankfully):
Rob Conery has published a simple, but very useful introduction to using Entity Framework with PostgreSQL. Along the way, he also manages to drag in some useful node.js utilities for creating tables in PostgreSQL and the amazing thing is that the tutorial actually works as advertised, is easy to modify and actually teaches the uninitiated a few useful nuggets of wisdom along the way.
If you are a .Net programmer and you are intrigued by this title, by all means go read it and implement it. You'll be glad you did, and I bet you'll save a bookmark to the page.
Using Entity Framework 6 with PostgreSQL
I do have to add one tip to this post: My company maps the "My Documents" directory to a network drive, which means under the hood, everything is addressed as a network path. The section in Rob's blog regarding node.js will not work correctly with this setup. Node.js does not support network paths, e.g. \\someMachine\someShar\temp\blah\bleh. Simply copy the program to a location on your local hard driver and rerun the node.js commands, such as db-migrate. Everything should function correctly at this point.