| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Black is white in Longhorn compatibility land | |
|
||
| Time: 10:45 EST/15:45 GMT | News Source: The Register | Posted By: Chris Hedlund | ||
|
Microsoft has visited the Bizzaro World of application compatibility to explain which software will break once Longhorn's .NET Framework 2.0 is unleashed on Windows. And the answer shouldn't be too surprising: applications written for the new stuff, in this case .NET Framework 2.0, are unlikely to run on the older stuff - that is, versions of Windows running the .NET Framework 1.0 like Windows Server 2003. Customers will need either Longhorn or up-coming Windows Server Release 2 which will run .NET Framework 2.0, to use applications that are written for the .NET Framework 2.0. | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 150 Last | Next |
The time now is
12:13:31 AM
ET.
Any comment problems? E-mail us |
| #1 By 61 (65.32.175.192) at 6/3/2005 3:27:23 PM |
| .NET framework 2.0 NEEDS to be available for at LEAST 2003, and should be available for XP as well... if they don't it will be such a mess. |
| #2 By 2459 (69.22.124.157) at 6/3/2005 7:06:46 PM |
|
After reading the blurb, I didn't feel like reading the article, however, it sounds as if the Reg watched the FX 2.0 compatibility vid on Channel 9 and made a lot of wrong conclusions.
I can't see what's wierd about FX 2.0 apps not running unless you have FX 2.0 or higher installed. Functionality such as Generics and Partial Types that was added in 2.0 are simply not available on earlier FX versions, thus 2.0 apps shouldn't be expected to run on earlier versions. As stated by quux, FX 2.0 will be available for current Windows versions and will not require upgrading to "Longhorn" or Server R2. Those platforms will, however, include FX 2.0 by default. Backwards and Forwards compatibility as used by MS is not the opposite of what they should be and is consistent with how the rest of the industry (game consoles is an example most people can relate to) uses the terms. Backward Compatibility: I have 2.0. I can go back and run older code on the newer runtime. I have XBOX360. I can go back and play older XBOX games on my new platform. Forward Compatibility: I have 1.0. Using 1.0 runtime, I can go forward and run newer (1.1) code on the older runtime. I have XBOX. If it were forward compatible, going forward, I could play XBOX 360 games on my XBOX. XBOX, like .NET 1.x, is not forward compatible w/ their respective new platforms. .NET 1.1 and 2.0 are backward compatible w/ older runtimes. .NET 1.0 is forward compatible w/ 1.1 but neither 1.x runtime is forward compatible w/ 2.0. Windows is backward compatible w/ DOS DOS is not forward compatible w/ Windows |
|
Write Comment
Return to News |
Displaying 1 through 25 of 150 Last | Next |
The time now is
12:13:31 AM
ET.
Any comment problems? E-mail us |
