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

So, you're suggesting that the final version of the .NET framework that will ship with Windows 7 RTM should remove this new overload and add a method with a unique name?


On Tue, 26 May 2009 13:07:35 -0300, Fernando Tubio <[email protected]> wrote:

>Not in the sense that their API is wrong. In other words, I'm not saying
>that this is a problem of framework design. But yes, I do think that if
>Windows 7 ships with .NET 3.5 SP1, then applications that previously worked
>correctly with this version of the framework on other platforms should
>continue to do so. I don't believe this to be an unreasonable expectation.
>Do you?
>
>----- Original Message -----
>From: "Peter Ritchie" <[email protected]>
>To: <[email protected]>
>Sent: Tuesday, May 26, 2009 12:53 PM
>Subject: Re: [ADVANCED-DOTNET] Forcing an application to load assemblies
>from a specific path
>
>
>>"If the framework designers thought like you, "...
>>
>>Come on. You are being extremely unfair. I've already said that as a
>>developer I agreed with you. Let me quote this line from my original
>>message
>>again.
>
>By using wording like "breaking change" in the framework, and "how does this
>help an end-user" you're implying that the framework designers have done
>something wrong.
>
>===================================
>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

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