AppScan not loading assemblies correctly/completely?

[Ian]

I've been having a problem with an extension I'm working on, and I
suspect that it has to do with the way that AppScan is loading
assemblies relating to the extension.

The extension that I'm working on has a set of persistent data that is
represented as a simple collection of classes, which is then
serialized using the .NET BinaryFormatter, and stored either in the
registry or in a file. This functionality works fine in a test
environment (i.e. I set up a test harness in Visual Studio that allows
me to test some of its basic functionality without having to import
the extension into AppScan every time).

The problem is that when I load the extension into AppScan,
deserialization of the data fails with the following message:

"Unable to find Assembly: <Assembly Info>"

After some searching around on the internet, it appears that this
error might have to do with the way that .NET assemblies are loaded in
AppScan. The way that I understand it is that when a stream is
deserialized, the deserializer reads some meta-data in the stream that
specifies what assembly, class, etc. the stream represents, and then
loads the required assembly to create the original object graph. For
some reason AppScan is unable to locate the required assembly, and
throws that error.

Has anyone seen this kind of thing before, and is it possible that
AppScan is not loading the required assembly correctly, or is only
loading a part of the assembly?

If not, can anyone think of a possible workaround for this?

Thanks in advance- Let me know if I can supply any more details or
clarification of what exactly I'm trying to do here.

--Ian

[Ian]

Update: After a whole bunch of digging, I found that I was having the
problem described here: http://www.west-wind.com/weblog/posts/29558.aspx

That post supplies a workaround which is a bit ugly, but it worked for
me.

--Ian