Microsoft .Net Framework 2.0 Breaks Apps

By Darryl K. Taft  |  Posted 2005-05-25 Email Print this article Print
 
 
 
 
 
 
 

WEBINAR: Event Date: Tues, December 5, 2017 at 1:00 p.m. ET/10:00 a.m. PT

How Real-World Numbers Make the Case for SSDs in the Data Center REGISTER >

Microsoft has found situations where applications written to .Net Framework 1.1 break when run against 2.0 and so is recruiting users to have their apps tested for compatibility.

Microsoft Corp. is looking for a few good men … and women, and, ultimately, applications that can help the company check for compatibility between the current version of the .Net Framework and the version coming in Visual Studio 2005.

The software giant is in recruiting mode, looking for independent software vendors, enterprise customers, developers, end users and others who would like to have their .Net applications tested for compatibility with the upcoming version of the .Net Framework.

At issue is the notion of breaking applications. Microsoft has identified situations where applications written to the .Net Framework 1.1 break when run against the .Net Framework 2.0.

The issues arose with the release of Beta 2 of Visual Studio 2005, also known as Whidbey, which Microsoft released last month. Beta 2 introduces the .Net Framework 2.0.

Read the rest of this eWEEK story: "Microsoft .Net Framework 2.0 Breaks Apps"
 
 
 
 
Darryl K. Taft covers the development tools and developer-related issues beat from his office in Baltimore. He has more than 10 years of experience in the business and is always looking for the next scoop. Taft is a member of the Association for Computing Machinery (ACM) and was named 'one of the most active middleware reporters in the world' by The Middleware Co. He also has his own card in the 'Who's Who in Enterprise Java' deck.
 
 
 
 
 
























 
 
 
 
 
 

Submit a Comment

Loading Comments...
























 
 
 
 
 
 
 
 
 
Thanks for your registration, follow us on our social networks to keep up-to-date