Petition for WCF4: No ServiceContract or OperationContract attributes!
-
With the .NET 4.0 looming on the horizon, and my current war with WCF trying to make it compatible with my POCO/POCI (Plain Old CLR Interface ;P ) architecture, it seems time to petition Microsoft to eliminate the need for those pesky
ServiceContractandOperationContractattributes on service interfaces. To compensate, they need to add the ability to define service and operation contracts through configuration, so we don't completely loose the ability to configure messages, provide versioning, define service namespaces, etc. Who else here loathes theServiceContractAttributeandOperationContractAttributeas much as I do, and wishes Microsoft would remove them as a requirement, and provide an alternative configuration-based approach to defining contract metadata? Voice your vote here! (And perhaps, if there are enough votes, the CodeProject staff could get the Microsoft .NET 4.0 guys to come take a look.)