Thanks SafariTECH - the issue here is that I might have a
version of a .dll that is not guaranteed to be backwards
compatible. In the .NET world, I could have two separate
applications access different versions of an assembly by specifying
application level assembly binding information. Is there a way to
do the same using two separate CF applications and the .NET
integration service? I haven't found a way, even using a CF
multiserver configuration, as there's still only one .NET
integration service in that case. With only one .NET integration
service, it seems like only one version of an assembly can be
accessed.
Thanks!