Some teams organize project items  per tpye: a folder with the enums, another folder with the exceptions, another with the classes and so on…

I think that this is not the right way if you want a mantainable project, I think that should be better organize items based on context or application area that they belongs to. For example you should put all the items (class, enum, …) that are part of Order management in one folder (aka namespace) and in another folder the items that belongs to Invoicing.

This way the project is more modular and is quite easy extract a module in a separate assembly if it becomes necessary.

Since two month I became a memeber of Solid Quality Mentors. A big opportunity that Solid gives me and I get without hesitation.

Even if SolidQ is specialized in SQL Server consultancy, my area is (obviusly) the .NET Framework.

I read a post of Ayende  that talk about a post of Fowler.
The post is about Microsoft against Open Source Communities.

Have a look at the posts, I agree with them.

Microsoft had build fantastic tools (the .NET Platform is really good) but what arrive in these days is not so good.

The open source communty have a lot good tools and library that MS can use and can support but it seems that MS is against these tools. MS tend to rewrite these tool in his way and the result is not always good as the open tools.

The Entity Framework, even it is not an official release, is not comparable to NHibernate for example.