NHibernate FAQ

If you're in need of NHibernate braindumps, check out hibernatingrhinos

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

Using AutoMapper for MVVM implementations

Being Clean Code Developers, whenever we start developing a new application, we try to improve our code quality, right? As a part of that, we librarify what can be librarified and use 3rd Party and Open Source assemblies wherever possible so we can concentrate on the really dirty work. OK, here's one thing Stefan Lieser brought to my attention in the course a Google Group discussion. It's called AutoMapper , and as the name gives away is a great deal of help when you have to map instances of Type A to instances of type B (very simply put, really). Sounds rather boring at first glance, but me and my buddy Maik decided we'd take a look at it for our nhibernate based MVVM implementations, in which (up to now) the viewmodels were wrappers / proxies for the models. Apart from that, it does great Conversions from one list type to another, which was a numb piece of loop-through-source-store-in-destination. The Gloria : Stickiness of memory addresses Having worked with NHibernate,...
Mehr anzeigen

Getting the Crisp back into your WPF Apps

Bild
WPF has a lot of advantages, it's perfectly sane data binding mechanism being one of the most outstanding ones.On the flipside, many people (meaning companies, mostly) have refused to switch from WinForms to WPF because of the "blurry" looks of applications written in WPF. This blurryness goes back to two mechanisms: 1)Text Smoothing Instead of relying on the system's ClearType mechanism, WPF does it's own thing-a-magic, which is blatantly inferior to the aforesaid. In fact, WPF smoothed fonts are a definite way to headaches, if read for some time. Note : The image is from a website that compares various Microsoft.Net Font-Smoothing implementations. They might be useful to integrate text in images, though.For business applications (displaying data grids etc.) this is a K.O. criterion. Nobody wants to have to take their glasses off in order to achieve readability, and nobody wants their software deployed along with a pack of aspirins. 2)SubPix...
Mehr anzeigen

Current and future Microsoft (Expression) Blend Versions

Bild
Any Developer working in the XAML Environment must have stumbled across Microsoft Blend, a.k.a. Expression Blend at some time. Blend is a Software aimed to support developers and designers of XAML based UIs create designs and animations, apply behaviors and so forth. As of 2010 (talking VS Versions), Microsoft has made the licensing of Blend a real mess, if you're a WPF Developer: The only way to purchase Blend is buying the entire Expression Studio Ultimate for somewhere around 500 Euros. Smaller development teams are made to bleed unnecessarily, since the VS 2010 XAML editor had serious issues before SP1. We're talking 2012 now - seems MS have learned their lesson: Blend is free for Windows 8 Store Apps and comes along with the correlating Visual Studio Express Edition. But what about WPF or the already zombified Silverlight? Good news first: Blend will continue to support WPF. But what are the licensing terms? Looking things up on the Blend Insider Blog , I fo...
Mehr anzeigen