Hi All;



I'm trying to finalize my tools before starting the app. The App. will be partly Windows and partly ASP.Net sharing data.



I like to get some thoughts and experiences from SF team and those how have chosen one v.s. the other and why?



a) SF comes with a limited number of Windows components that are nicely tied with SF framework and also takes advantage of SF theme system. This helps building a uniform application, but the components are limited, especially when it comes to the ASP.Net part (I mean for grid and new Web gadgets that IG offer).



b) Infragistics (IG), offer a very nice and complete components, with a powerful "Application Stylist" design for Windows and web. This gives you a wide range of designs, BUT you loose the SF themes (like the navigation tool bar, application header and etc.) and also we loose some of the SF integrations that are already in SF components.



Due to my lack of experience (being new to SF and IG), I really would like from those who have gone through this road to share their suggestions.



Thank you in advance!

..ßen

Paul,

I agree you should use whatever controls that provide the features you want and are comfortable using.  The SF source code provides a plethora of samples on how to plumb a new or third party control.  Paul, I do not agree with your characterization of SF moving from one control base to another.  I may remind you it was our desire to use Ingragistics initially but we could not obtain the necessary legal release to include a wrapper in our code.  It was only at the insistence of Larry Caylor that Infragistics caved-in. 

We included Dev-Express and Infragistics because they are the most commonly used.  Beyond these two products trying to create a wrapper for all third party controls is beyond any benefit we would receive.

Steve,

Last year after you released the Dev-Express wrapper Trent stated the you guys were using Dev-Express in your medical system. This statement weighed quite a bit on my decision to use Dev-Express as I figured if you are using it in your medical system chances are that you guys will run into issues etc and be familiar with that set of controls.

Now Trent say's

The point I am trying to make is that the decision to purchase and use a 3rd party UI control set should not be based on what you guys are using rather on which control set you believe has the best features etc. You guys do an excellent job of providing the wrappers as well as the interfaces and the selection of a 3rd party UI control shouldnt matter.

Paul