As expected, NHibernate 2.0 went gold yesterday and is available for download. This is official release 2.0.0 GA. Please ensure you review this list of breaking changes from the release notes. Linq to NHibernate is available for now only via the NHibernate Contrib project and is not included in this NHibernate release.

The Linq to Financial Markets provider An easier way to consume, visualize, understand and quantify just about any information you can imagine from the world of global financial services. Real-Time stock quotes to Complex Analytics of Multi-Asset Class Portfolios Monte-Carlo simulation with Optional Quantitative Add-Ins Efficient frontier Optimization based on Constraints you Set User defined heuristics from strategic rebalancing to day-trading

ReSharper 4.01 RC1 released...Here is how the recent builds have looked. Just click on one to download it:

Ask yourself personally your opinion on the genesis for a software process/method. What made waterfall become a shared mental belief system in millions of minds yet fail so consistently, and indeed provide the only level of 'predictability' in software at that time (an expectation of predictable disaster). I could continue on the facts above for a few pages but it merely is an example of our need to carefully choose a belief system that actually has the added value of being correct. Ask yourself personally your opinion on the genesis for a software process/method. What made waterfall become a shared mental belief system in millions of minds yet fail so consistently, and indeed provide the only level of 'predictability' in software at that time (an expectation of predictable disaster). I could continue on the facts above for a few pages but it merely is an example of our need to carefully choose a belief system that actually has the added value of being correct.

There are a few changes (one you absolutely need to know about yet I’ve never seen officially from MSFT) in the just released SP1 for .NET 3.5 . Again, these are completely undocumented. Cast breaking change: Cast was not correctly behaving in all scenarios do it was silently fixed for SP1. This does break you code in some situations! If you’ve been using Cast for example to perform generic collection type conversions well that was not so good. Here are the two assumptions that we used to get away with not following: The elements in the object based collections need some additional step (specifically an un-box or a reference conversion) The starting point is only non-generic types (think ICollection, IEnumerable, etc) you call Cast on.

Click here to download the new EAP post 4.0 beta 1 release of 4.01 (a maintenance focused release). On the heels of their 4.0 release which further cemented their utter dominance as the must have Visual Studio 2008 augmentation for true enterprise development, their not resting in the least.Click here to download the new EAP post 4.0 beta 1 release of 4.01 (a maintenance focused release). Please participate by providing your experiences to JetBrains so they can evolve this work into another solid must have upgrade. Click here to join their issue tracker as well as newsgroups.

Do not implement IQueryable without understanding all the performance tradeoffs. · Building and parsing expression trees is expensive and many queries can actually get slower when IQueryable is implemented. · The trade-off is acceptable in the LINQ to SQL case, since the alternative overhead of performing queries in memory would have been far greater than the transformation of the expression to an SQL statement and the delegation of the query processing to the database server.

Here is the first of many resources we will be posting on the must know aspects for .NET 3.5 and C# 3.0 best practices using Linq. We will covering Linq to NHibernate shortly in great detail for example.