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

> Terminology aside, I think from a end-user perspective it is hard to
explain
> that apparently .NET 3.5 SP1(Vista) is not equal to .NET 3.5 SP1(Win7)
since
> this app would run on .NET 3.5 SP1(Vista) but not on .NET 3.5
SP1(Win7).End-
> users see the similar framework version and assume it has to work but we,
as
> devs, know their builds numbers are not the same and that one *can* run
into
> problems like these.
> // Ryan

	exactly. 

	for breaking changes, developers and ISV's should use the major and
minor version number. If these are the same, the build should be considered
the same. 

		FB 

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