Topics: Data Access Application Block
Sep 26, 2007 at 7:06 PM
Perhaps a dumb question but, I was reading through the documenation and came across "Updating Shared Assemblies" (under Deployment and Operations - Updating the DAAB) and I couldn't help but wonder if the following statement was actually true.

"By default, the common language runtime tries to load the assembly that has the latest build and revision numbers but the same major and minor version numbers as the assembly the application was built with."

I had though Fusion was initially designed to behave as indicated above, but I also thought that that behavior was removed some time before the final release. I was thinking Fusion now only attempts to bind to the exact version of an assembly that an application was built with. The following link seems to support my thinking:

The only way I know to change that behavior is to apply policy (publisher, app, or machine).

Any insight you can offer would be greatly appreciated.