Customer is having trouble getting binding rules to work,
this is what he said:

"When deploying a .net application compiled with
iAnywhere.Data.SQLAnywhere 11.0.1.20522 to Win2008/64 running
iAnywhere.Data.SQLAnywhere 11.0.1.23242 , we get problems running the
application.

..Net seems to ignore the binding rule in mscorcfg 10.0.0.0-11.0.1.23242
-> 11.0.1.23242 and complains that it cannot load 11.0.1.20522

When tested on a Win2003/32 running iAnywhere.Data.SQLAnywhere
11.0.1.22992 with mscorcfg rule 10.0.0.0-11.0.1.22992 -> 11.0.1.22992 it
works fine.

When tested on Win2008/64 running 20552 (with matching version) it also
works fine.

This is our first experience with Win2008/64 deployment. It's even
stranger because we are using Win2008/64 Visual Studio 2008 development
platform."

The customer also tried other versions of 11.0.1, but had the same
results of 64 bit, ignores the binding rules. He doesn't have a problem
on the 32 bit.

As a workaround right now, he is keeping the assembly version on 64-bit
server the same as his development machine.

Anyone know why the binding rules won't work on 64 bit?

Thanks