A new tool that enables you to create a single assembly shat can be shared by multiple .NET runtime environments, namely Silverlight, Windows Phone 7 and XBOX Gaming. Of course, you can target the desktop .NET runtime also when building class libraries but since the former ones include only a subset of the desktop .NET runtime, you only get the common denominator assemblies.
Some (official, not ripped or scanned) free e-books form MS Press: http://goo.gl/9GcD2
There are eight e-books ranging from development, IT and Office.
Microsoft’s version of dependency injection (DI) container, Unity (a.k.a., Unity Application Block) v1.1 is available for download. As you might remember 1.0 was released just back in April 2008. The documentation for v1.1 is here (VS 2005) and here (VS 2008)
To conceptually know more about DI container/IoC patterns:
- Martin Fowler: Inversion of Control Containers and the Dependency Injection pattern
- Wikipedia: Inversion of Control
The latest version of Microsoft Enterprise Library, v4.0, is finally here for download!
The most important additions in this release for me are VS 2008 support and integration of Unity dependency injection container (Unity Application Block). Go grab it!!
You know Visual Studio 2008 comes in many editions but ever wanted to know the features available with these editions? Microsoft has a comprehensive feature matrix (for quite some time) here. A downloadable copy is also available here.
If you are deciding which edition of VS 2008 to buy, then this should be your one-stop reference point.
Starting with Visual Studio 2005 (except Express ed.) you can create and modify classes using Class Designer tool with two-way synchronization between the diagrams and the code. And Designer-created class diagrams are stored in a file with .CD extension, in XML format. However, this .CD file is not a self-contained one, meaning, you cannot open the file without the associated class files. If you actually open the CD file in Notepad, you can see references to the source code files and other positioning coordinate details, etc required to render the classes in designer mode. So, the moral of the story is that you cannot send just a .CD file to your co-developer thinking he can see your class design. He needs the complete source code too. In other words, the Visual Studio Class Designer is more of a visualizing tool (or a tool to create classes visually) than a diagramming tool by itself.