InfoPath Dev

Also if we get better integration with WCF is of interest...

http://www.youtube.com/watch?v=wOPJTgSoFCQ

Cool interesting areas I can see after 4 days digging in the product is  1) Support for more fancy UI things like adding Ajax, Silverlight or WPF components, compare Silverlight for Sharepoint...  2) The Business logic concept  3) Future: Will InfoPath meet Entity Framework or where will InfoPath be in the Astoria(Oslo ...

TCO is important and easy to create the next form.... MOSS will be a key coimponent and I like what I have seen with Document Information panels etc... It would be nice to see where the next version of InfoPath will go... I was at ODC2008 in SF and didn't see any stories about InfoPath and the future...

We have not selected how to create forms yet. Infopath could be one way forward but it looks like we should implement more than 60 processes for external users to initiate ==> means that intenally we will have much more so to have the business rules at one place could be a time saver and a maintenance saver...  I think the Infopath client ...

Random does it mean that the same person gets it or different persons ... I read today a nice chapter in the book "Designing Forms for Microsoft Office InfoPath and Forms Services 2007" http://safari.informit.com/0321410599 and the security set up in InfoPath is not trivial some links to start ...

Found this approach which from an user perspective is not to preffer as you need to do a round trip to the server. The validation should I think be in the client to give a good user experience... "On submittal, send the data to a Web service and perform all possible validations on the server side. For example, if you have a condition that ...

Just out of curiosity Does it take 8 minutes to just populate or does it take also time retrieving the items ....

For me best practice is regarding Business logic Separate presentation and business logic in different layers http://msdn2.microsoft.com/en-us/library/aa581779.aspx "Reuse" Validation and Business rules ==> you write it once and it is used in ASP.NET, services etc. Exampel is the Enterprise Lib Validation Block where you have a ...

We are building a layered solution where we will have a "Domain layer" where we have all the business logic etc. Is there any design patterns how to use this logic from InfoPath so when a rule change in the Domain layer it automaticly is used by the InfoPath form..  Compare Enterprise lib Validation Application ...