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

I could write code that used reflection to access a private field of a
framework object. If the internal implementation of that object changed but
the contract stayed the same would that be a breaking change?

My guess is you should file something with their support. There is always
virtual XP :)

Greg

On Tue, May 26, 2009 at 10:55 AM, Fernando Tubio <[email protected]> wrote:

> I agree with everything you say as a developer. But how does this help an
> end user? The application is still broken <=> breaking change.
>
> - Fernando
>
> ----- Original Message ----- From: "Peter Ritchie" <
> [email protected]>
> To: <[email protected]>
> Sent: Tuesday, May 26, 2009 11:21 AM
> Subject: Re: [ADVANCED-DOTNET] Forcing an application to load assemblies
> from a specific path
>
>
> Agreed.  Just because the 3rd party code may be reflecting soley by method
> name (which will work if there are no overloads) does not make adding an
> overload a breaking change.  For example, they're looking for trouble with
> code like this:
>
> methodInfo =
> typeof (FrameworkClass).GetMethod("Method", BindingFlags.Instance |
> BindingFlags.Public);
>
> They should have something more like this:
>
> methodInfo =
> typeof (FrameworkClass).GetMethod("Method", BindingFlags.Instance |
> BindingFlags.Public, null, new Type[] {}, null);
> There's all sorts of good reasons to reflect on types that could be
> staticall linked...
>
> Can you detail what 3rd party application this is, so we can avoid using
> it?
>
> -- Peter
>
> ===================================
> View archives and manage your subscription(s) at
> http://peach.ease.lsoft.com/archives
>
> ===================================
> View archives and manage your subscription(s) at
> http://peach.ease.lsoft.com/archives
>



-- 
It is the mark of an educated mind to be able to entertain a thought without
accepting it.

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