Our existing ASP.NET application needs to support a new asynchronous
processing model.  Basically, a user interaction will cause an activity to
happen...the ASP.NET page returns immediately to the user while this
activity runs off in the background on the server.

I know one way to do this is Queued Components through Enterprise Services.
I'm trying to setup a little test sample but am running into an issue.  I'm
reading that assemblies that support being used through Enterprise Services
must be strongly named.  This is fine, except I didn't realize that every
assembly a strongly named assembly depends on must also be strongly named.
This is turning into a nightmare.  This impacts three of our other class
libraries.  We also use the new Enterprise Library blocks from Microsoft;
they need to be strongly named.  We use NMock, it needs to be strongly
named.

Am I missing something here?  Or is this turning into as much of a pain as I
think it is?

Thanks
-joe