We are adopting an architecture completely based on WCF Services, thereby allowing us to decouple our presentation layer from our Business Logic layer. However, everything that we currently know about traditional Web Forms seems to go out the door by adopting this model since traditional Web Forms assumes direct access to the database and to the Business Logic tier.
As a first step, we would like to figure out how to provide a default serialization mechanism for our SiteMap data so that it can be consumed by the SiteMapDataSource on the ASP.Net client side code, but eventually we would like to be able to serialize all of our ASP.Net providers such as our MembershipProviders, Personalization and Profile Providers so that they are all available via our WCF Services.
Are there any samples/examples anyone can provide on how to serialize all of our existing Provider classes over WCF Services so that they can be appropriately consumed by our ASP.Net web forms clients? Is it supposed to work as simply as marking all of our classes with System.Runtime.Serialization and the appropriate serialization attributes or is it significantly more involved than that?
View Complete Post