Re: Forcing an application to load assemblies from a specific path

Programming "by coincidence" [1] should not put the onus on the framework to ensure all poorly written code works in a new framework.

If the framework designers thought like you, their only option would be to never add overloads; they'd have to always add only new method names.  This would make for an entirely unusable framework over time.  By the same logic, they wouldn't be able to add any methods with new names because someone my be relying on the null return from GetMethod, or relying on a specific array length from GetMethods.

That doesn't help the end-user; but realistically, poorly written code never does.  The application developers have to accept the onus of writing good code for their users; something the framework designers have no control over.

If anything, the framework designers should deprecate GetMethod(string).

[1] http://www.pragprog.com/the-pragmatic-programmer/extracts/coincidence
===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives