Acord Standard for Insurance. Has anybody dealt with this mess?
c#, wcf, xsd
Solution
It sounds like you are heading down the right path but are lost in the forest. The ACORD Standard is huge and intentionally so, as it provides support for hundreds of different messages. Just as you do not download all of Wikipedia to get just a few articles, you do not need all of the classes in the ACORD Standard to support an implementation of a few messages. If you know what messages you need to support then you can generate a subset of the full XSD that will be quite manageable.
As mentioned in Hugh’s response, for any one message only a fraction of the full XSD is used. How you go about doing that will depend on the specifics of your project. If you are looking for ideas on how generate a subset of the full XSD try reaching out to the ACORD staff for help at PCS@acord.org. They should be able to offer you some help in getting started.
Problem
We need to implement a WCF Webservice using the ACORD Standard. However, I don't know where to start with this since this standard is HUMONGOUS and very convoluted. A total chaos to my eyes. I am trying to use WSCF.Blue to extract the classes from the multiple XSD I have but so far all I get is a bunch of crap: A .cs file with 50,000+ lines of code that freezes my VS2010 all the time. Has anybody walked already thru the Valley of Death (ACORD Standard) and made it? I really would appreciate some help.