Whats new in asp.net 3.5
What is new in asp.net 3.5
1. Support for Ajax enabled websites
2. Support for LINQ
3. Object oriented client script library
4. Full intelligence support for java script
5. New server controls( List view , LINQ data source)
6. New merge tool(Aspnet_merge.exe)
Asp.net Enhancements
• We can use Asp.net services like forms authentication, caching for all content types Because NET Framework version is integrated with IIS 7.0. Both request pipelines are integrated together. In IIS 6.0 there will be two request pipelines. One for ISAPI filters and extension components etc and the other one for managed-code application components such as ASP.NET. We can enable or disable managed code components for all requests. Managed-code modules can be invoked at any stage in the pipeline. This includes before any server processing occurs for the request, after all server processing has occurred, or anywhere in between. we can register and enable or disable modules through an application’s Web.config file
• All requests can be configured to take advantage of ASP.NET functionality, because that functionality is encapsulated in managed-code modules that have access to the request pipeline. For example, even though the .htm file-name extension is not explicitly mapped to ASP.NET, a request for an HTML page still invokes ASP.NET modules. This enables you to take advantage of ASP.NET authentication and authorization for all resources.
1. Support for Ajax enabled websites
2. Support for LINQ
3. Object oriented client script library
4. Full intelligence support for java script
5. New server controls( List view , LINQ data source)
6. New merge tool(Aspnet_merge.exe)
Asp.net Enhancements
• We can use Asp.net services like forms authentication, caching for all content types Because NET Framework version is integrated with IIS 7.0. Both request pipelines are integrated together. In IIS 6.0 there will be two request pipelines. One for ISAPI filters and extension components etc and the other one for managed-code application components such as ASP.NET. We can enable or disable managed code components for all requests. Managed-code modules can be invoked at any stage in the pipeline. This includes before any server processing occurs for the request, after all server processing has occurred, or anywhere in between. we can register and enable or disable modules through an application’s Web.config file
• All requests can be configured to take advantage of ASP.NET functionality, because that functionality is encapsulated in managed-code modules that have access to the request pipeline. For example, even though the .htm file-name extension is not explicitly mapped to ASP.NET, a request for an HTML page still invokes ASP.NET modules. This enables you to take advantage of ASP.NET authentication and authorization for all resources.
Comments