background preloader

Home - NHibernate Forge

Home - NHibernate Forge

Fluent NHibernate Tales from the Evil Empire Asking questions is a skill If you’re going to get into any sort of technical job, you’re going to have to ask questions. A lot of questions. Unfortunately, too few people understand how to ask questions properly. Here are a few of the most common mistakes I see people make every day on Stack Overflow, or on other technical forums… 1. “I installed Orchard, and it doesn’t work. Put yourself in the shoes of someone trying to answer this. How does it not work? Ask yourself: is there enough information for anybody who’s not you to figure out what the problem is? Notice how asking a question that is too vague will only get you more questions in return. 2. “[wall of text explaining your setup with a luxury of irrelevant details…] Why does the screen flash blue when I click the green button?” The people who are likely to be able to answer your question can’t invest a lot of their time understanding all the specifics of your business, nor should they have to. 3. 4. “Where is the green button? 5.

MS Israel Community Code Contracts Sign in to write a review Sort by: Build performance degradation kills all the good things in this solution. Hi, CC should work with VS2013 without any problem.Try to uninstall and reinstall? It's Dec. 12, 2013. I'd like to use Code Contracts so I'm trying to install the dll that is meant for 2010/4.0 that EVERWHERE I read it says it will work with VS 2008. All links I find lead back to this page. Thanks, dlk Great tools! I previously used Code Contracts back in 2010 and 2011 (with Pex). Great concept, decent implementation. It does have a few bugs I've had to work around, it isn't open-sourced, and it significantly slows down build time (by 10x or more), even with static analysis disabled. I've found the static analysis to not be worthwhile - it might be worthwhile for new projects starting from the ground up, but it takes a lot of extra work to satisfy in my experience. After a while, one is wondering, how one could write projects without this tool. by Vrane | September 05 2013 David

James Gregory » I think you mean a many-to-one sir This is a question that crops up a lot, in various forms, on the Fluent NHibernate and NHibernate Users mailing lists. My one-to-one mapping isn’t working, what’s wrong? aka Incorrectly using a one-to-one relationship when you actually need a many-to-one. There’s a common misunderstanding where people try to use a one-to-one relationship where a many-to-one is appropriate. I believe this is because people tend to get tunnel vision when designing their entities, which leads them to make incorrect assumptions. They focus on one entity at a time, and when that has a single entity related to it, they jump to the conclusion it’s a one-to-one they need; after all, there’s their current entity (one) and the related entity (to-one). Many-to-one Lets have a look at what actually is a many-to-one. This is a standard many-to-one relationship, many Customers to one Address; the tables are linked by the AddressId key in the Customer table. One-to-one

RestSharp NHibernate Best Practices with ASP.NET, 1.2nd Ed. Author's note added June 11, 2008 - Announcement of S#arp Architecture Thankfully, technologies evolve over the years. Accordingly, Microsoft has introduced ASP.NET MVC as an alternative to classic ASP.NET. I have developed a new architecture which uses many of the design principles of this article for this newer platform called S#arp Architecture. Preface to the 1.2nd Edition In March of 2006 I published my initial thoughts on NHibernate best practices with ASP.NET, generics and unit tests. Quite simply, NHibernate is awesome. A quick thanks goes out to those who have implemented my ideas in their own work and have given plenty of ideas for improvement and consideration! Article Contents Introduction Why Use an ORM? [Author's Note: The following is an excerpt taken from a book I tinker with in my "spare" time.] "As we look to the horizon of a decade hence, we see no silver bullet. The most common dissenters of ORM technologies, in general, are developers using Microsoft technologies.

NuGet Impact - HTML5 Canvas & JavaScript Game Engine

Related: