What Is New in .NET Framework 1.1
This release focused on enhancing ASP.NET for web development, improving security, and adding critical support for mobile devices. It also introduced side-by-side execution, allowing multiple framework versions to run on the same machine.
| Category | Key Changes |
|---|---|
| New Features | ASP.NET Mobile Controls, Side-by-Side Execution, Native Support for ODBC and Oracle Databases, Internet Protocol version 6 (IPv6) Support |
| Security | Code Access Security for ASP.NET Applications, Assembly Execution Changes |
| Improvements | ASP.NET Performance and Reliability, Windows Forms Updates |
| Deprecated | Some APIs and features from version 1.0 were made obsolete. |
How did ASP.NET improve in version 1.1?
The biggest advancement was the introduction of ASP.NET Mobile Controls, previously known as the Microsoft Mobile Internet Toolkit. This allowed developers to build a single web application that could automatically render appropriately for different mobile devices like phones and PDAs.
Beyond mobile, the update brought significant performance and reliability enhancements to the core ASP.NET engine. It also integrated Code Access Security, giving admins more granular control over the permissions of web applications.
What is side-by-side execution and why does it matter?
Side-by-side execution is the ability to run multiple versions of the .NET Framework on a single machine. This was a game-changer for deployment and application compatibility.
In practice, this meant an application built for .NET 1.0 could run on the 1.0 runtime, while another app built for 1.1 could run on its respective runtime, all on the same server. It eliminated versioning conflicts that could break applications during framework updates.
Were there any changes to data access?
Yes, data access received a major boost with the inclusion of native managed providers. The .NET Framework 1.1 added built-in support for ODBC (System.Data.Odbc) and Oracle databases (System.Data.OracleClient).
Before this, developers often relied on third-party libraries or OLEDB providers to connect to these common data sources. This native support simplified code and improved performance for these database connections.
How did security evolve in this release?
Security was tightened significantly, especially for ASP.NET. Code Access Security (CAS) policies were extended to apply to web applications, allowing administrators to restrict what a web app could do based on a trust level.
Assembly loading behavior was also modified. The runtime would now refuse to load an assembly if the required security permission demand failed during execution, making the security model more robust and predictable.
FAQ
Can .NET 1.1 applications run on the .NET 1.0 runtime?
No. Applications compiled specifically for the .NET Framework 1.1 require the 1.1 runtime to be installed. This is why the side-by-side feature was so critical.
Do I need to rewrite my 1.0 app to use the new mobile controls?
No. The ASP.NET Mobile Controls are an additive feature. Your existing 1.0 web forms applications will continue to work unchanged on the 1.1 framework.
What happened to the Microsoft Mobile Internet Toolkit (MMIT)?
It was integrated directly into the framework and renamed to ASP.NET Mobile Controls. If you were using MMIT, you were essentially using a preview of this 1.1 feature.
Is IPv6 support automatic?
The framework APIs were updated to recognize and handle IPv6 addresses, but its use still depends on the underlying operating system supporting and enabling IPv6 networking.
Were there breaking changes from 1.0 to 1.1?
Yes, though minimal. Some minor API changes and the stricter security policy for assembly execution could cause previously working code to fail if it was not fully trusted.