Hi John

>However, SF.NET has lesser classes. Classes that I need such as picklist textbox/button/form, mover control/form, factory class, form manager, appconfig manager and etc are not there yet.

I'm not really sure what you are referring to. SF has its own subclasses of the checked listbox, button and several form classes. It also has an ever increasing number of widgets, controls and templates.

As to a specific "factory class", a factory class is based on a factory pattern and personally, I create object factories almost everyday. I am unsure what value a framework factory class would provide over and above rolling your own which is trivial.

VS2005 has fairly sophisticated configuration management straight out of the box so again, I see this as a non-issue.

As to a form manager, given that you are, I assume creating Winforms applications, most forms will be child forms of an MDI container form and as such, you can easily control your forms via the MDI children collection in the MDI parent form, or reference the MDI collection via the MDI parent property of the child form.

A number of the things to which you have referred as issues remind me of the kind of things I would have expected in a VFP framework that are not quite the same issue in .NET.

As to SF being more "static", again I am unsure what you mean exactly. I think that if you have a straight Winforms application requirement and you want to get the job done quickly, straight out of the box, which framework helps you get the job done more quickly? When you feel you have an answer to this question, then you have found the framework that suits your development style best.

HTH