BTJ is talking about the nasty tricksey XML serializer bug our team discovered yesterday.

In order to reproduce this, do the following:

·         Make sure you’re running 1.0 of the framework (this has been fixed in 1.1).

·         Define an enum and decorate it with the [Flags] attribute (non-[Flags] enums seem to work ok).

·         Inside of this enum, define more than 16 values.

·         Expose this enum over a web service.

·         Try to consume this web service.

If you run into the same bug we found, you’ll get a exception back that says “The assembly xsd fskj.dll, or one of its dependencies, could not be found” the first time you try to instantiate the service proxy. The name of the assembly will vary, because the exception is being thrown trying to locate the dynamically-generated assembly the XML Serializer creates to serialize the enum into XML.

Weird stuff -- Anybody else seen this?