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

On Tue, May 26, 2009 at 8:12 AM, Peter Ritchie <
[email protected]> wrote:

>
> 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.


I think we can all agree that the developer of the third-party application
has done something wrong here and that it should be possible to add
overloads to the core libraries in .NET. But we're not talking about a new
release of the framework or even a "service pack" -- it's "just a new build"
of the same version as what's already been released. They're usually a bit
more conservative than that over in building 42; my experience is that I
can't get any Reflection bugs fixed because "it might break existing
programs". :(

--
Curt Hagenlocher
[email protected]

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives