DISCLAIMER: This post is not about bashing SF that doesn't have WPF support right out of the box, but to see how we can leverage SF's power in developing 3-tier WPF apps.



Looking at several companies who are actively developing controls for VS2008 (Orcase) WPF and silverlight, I want to start looking into developing apps that Uses WPF UIs.



SF, has several great parts Business Objects, BO mapper, validations & business rules, Security, UI controls, Database Deployment, 3-tier SE and etc.

Now what parts of SF can we use to work with WPF?

a) Business Objects (for sure)

b) Server Enterprise (a must for me)

c) Validation and rules (can this be done if SF doesn't have hooks to the UI controls)

d) RBS (I'd love to, but can we use it)

e) BO Mapper (a must to create the DAL)

f) DDT (for sure)



I'd love to hear opinions of those who have experience in SF and also thinking about te new wave!



Thank you all!


..ßen

I also am very interested to hear how/when SF will start to support Orcas (especially LINQ). We are already developing against it for future products (in-house) without using SF, though I see customer work for us remaining in 2.0 for a while. Naturally we want to stick with SF and am interested to hear the time line and ideas how SF will integrate.



/wave




Keith Chisarik

As I had said in another thread, I've looking at LINQ lately and SF is way ahead of the LINQ game when it comes to features. There is a ton of stuff in SF that don't exist in LINQ. Once SF has the query part of the LINQ integrated, SF will be much more than what LINQ has to offer.

Based on my observation from the training and talking to Trent and Ben, I'm confident they'll do the right job!



What I want to do meanwhile, is to use the existing SF pipeline to hookup to WPF UI layer. Silverlight currently does not have data binding support yet, but WPF does.



So, I'm just trying to brainstorm with other candidates to see what areas we need to watch for?

So, who is jumping in the water????

..ßen