>Is there anybody here who has experienced using either of the following frameworks: Infragistics, ComponentOne, and MereMortals.Net?

I'm not in a position to recommend any of the three, Jess, but I'd like to caution you about what you can expect from any framework for an Object Oriented language.

My experience is that you cannot shortcut the learning curve for a technology like .NET.

To make effective use of an application framework you need to have a good understanding of the underlying technology. With that understanding, you will be able (with a good framework) to construct applications more quickly and with higher quality. The reason for this is that you need to work with a framework, and learn how not to work at cross-purposes to it. Usually you can accomplish (within reason) anything you need to do with any framework. But you have to know how a particular framework does things - its "style" if you will. When you want to modify its behavior, you need to know how to take advantage of the hooks and decorators and wrappers built into the class. No matter how well its documented, you will find yourself "code diving" the framework repeatedly, trying to learn how it accomplishes a particular task so you can understand how to properly modify it. This takes a fair degree of comfort with the underlying language and technology.

>We are in the process of looking for a framework to help rapidly migrate to .Net Technology and we are really very cautious in choosing one.

Again, your migration won't be made much more rapid by adoption of a framework. The framework will make you more productive once you've climbed the curve, but will only make the curve slightly easier to climb, through the examples that the code provides. You are right in being cautious about making the selection, but don't skimp on the time and effort you invest in making the decision. My recommendation would be to purchase a single copy of each framework, and select a small team of at least three people that would evaluate the products then brainstorm to compare the perceived strengths and weaknesses of each. Have each team member spend at least a solid week with each product to avoid the tendency to recommend what they've just spent a week learning <s>. Be sure to take advantage of both peer-to-peer support forums as well as the vendor's technical support, to factor that into the equation.