Welcome to MSDN Blogs Sign in | Join | Help

Smart Client Software Factory – April 2008 Release is available on MSDN

The April 2008 release of the Smart Client Software Factory is now available at http://msdn2.microsoft.com/en-us/library/aa480482.aspx. 

This is a port of the last release (May 2007, if I recall correctly) to VS2008.  No new features were added.  A few bugs were fixed, and a number of work items from CodePlex were closed.

This release supports Enterprise Library 3.1.  It does not support Enterprise Library 4.0.  If you want EntLib 4.0 (once it is released) you have the source code, and should be able to get it to work, if you really need to.  I would not recommend it, as you will end up with two containers (Unity and the CAB container), which means code bloat and challenges deciding where objects should go.

 

Published Friday, April 25, 2008 5:25 PM by mpuleio

Comments

# Smart Client Software Factory - April 2008 Release for Visual Studio 2008 is now available on MSDN

As Mike announced in his blog yesterday, we released an updated version of the Smart Client Software

Saturday, April 26, 2008 10:33 AM by Blaine Wastell - patterns & practices client architecture guidance

# Smart Client Software Factory (SCSF) April 2008 for Visual Studio 2008 Released

After publishing an alpha version , a beta version and a RC 1 version I'm glad to announce that the final

Saturday, April 26, 2008 1:07 PM by Ezequiel Jadib

# Smart Client Software Factory (SCSF) April 2008 for Visual Studio 2008 Released

After publishing an alpha version , a beta version and a RC 1 version I'm glad to announce that the final

Saturday, April 26, 2008 1:09 PM by Ezequiel Jadib

# SCSF 2008 - go get it!

After many months of promising , the wait is over. Smart Client Software Factory for Visual Studio 2008

Saturday, April 26, 2008 7:06 PM by My Technobabble

# re: Smart Client Software Factory – April 2008 Release is available on MSDN

Hi,

Just reading this comment from you..

"I would not recommend it, as you will end up with two containers (Unity and the CAB container), which means code bloat and challenges deciding where objects should go." Don't you think Enterprise team blocked people of are using CAB in thier application. Here is an example we have 3-4 products based on CAB and using EntLib 3.1. Now we are stuck, we can't move on to EntLib 4.0 due to Unity and the CAB container. Do you guys have any plan to move CAB to Unity base container.

Thanks

Sushil

Monday, August 04, 2008 7:10 PM by sushilsrivastava
Anonymous comments are disabled
 
Page view tracker