.Net Hive

A blog about Microsoft .Net Platform & other industry happenings

Data Access with ADO.NET 3.5 – Extensions

In our last post, we looked into objectives of the ADO.NET 3.5 which get shipped with VS 2008 Service Pack1. To achieve those objectives, we have some very good language extensions for ADO.NET 3.5. in C# and VB.

  • LINQ extension for VB 9.0 and C# 3.0 language provides a set of standard query operators to query many different kind of data sources using SQL like syntax. This extension for VB and C# implements LINQ pattern.
  • LINQ to Object is the default implementation for LINQ. It enables the developer to execute queries against a data persisted in memory that implements IEnumerable or IQueryable interface.
  • LINQ to SQL extension to LINQ to Objects provide an O/RM tool to generate and manage classes for business objects and to persist their instances in SQL Server tables.
  • LinqDataSource server control introduced in ASP.NET 3.5 simplifies the headache to bind data enabled web controls to business objects created with LINQ to SQL.

Later on we will discuss each of the above mentioned extensions individually, to look under the hood of ADO.NET 3.5 and it’s working.

Until than happy reading 🙂

Waqas Ahmed

Filed under: .Net, , , ,

Data Access with ADO.NET 3.5 – Primary Objectives

Release of Service Pack 1 for Visual Studio 2008 brought us some of the major lift updates .Net Framework. One of those update is ADO.NET 3.5 along with whole set of new languages and methodologies for data access as compare to .Net Framework 2.0. Some of the primary objectives of these updates are:

  • Increase developers productivity with minimal code required to achieve certain database/data related tasks.
  • Allow strong-type checking of database query syntax for relational data and their resultsets.
  • Enhancements to DataSet integration with multi Tier application architecture.
  • Enabled data intensive Winform projects with a local, synchronizable data cache derived from SQL Server Compact Edition v3.5
  • Enabled data intensive Winform projects with a local, synchronizable data cache derived from SQL Server Compact Edition v3.5.
  • Eliminate often known as the resistant mismatch between the code for data management, which usually involves SQL and OOPs programming.

Next time we will talk about the introduction of different extensions to LINQ related components /frameworks.

Waqas Ahmed

Filed under: .Net, , , ,

CLR Optimizations In .NET Framework 3.5 SP1

A surprising amount of work went into the core of the Microsoft .NET Framework for the .NET Framework 3.5 SP1 released in August 2008. Here, I’ll provide in-depth information about the changes that we on the CLR team made to the common language runtime (CLR) and the improvements you can expect by simply running your existing CLR 2.0-based applications against this latest service pack. Most of our effort was centered on improving performance, security, and deployment of applications targeting the .NET platform.

.NET Versions and CLR Versions
.NET Framework Version Contains CLR Version
2.0 2.0
3.0 2.0, 3.0
3.5 2.0 SP1, 3.0 SP1, 3.5
3.5 SP1 2.0 SP2, 3.0 SP2, 3.5 SP1

Startup Performance Improvements

Improving the startup performance—in particular, the cold startup time of managed applications—was a primary focus of .NET Framework 3.5 SP1.

Managed assemblies in the .NET Framework are largely precompiled via NGen, and the layout of the code and data in the NGen images has a strong impact on the startup performance of applications that use the framework. In particular, since cold startup time is typically bound by the number of pages of the image that need to be read from disk, any effort to reduce it translates into an effort to better pack the image so that only a small subset of its pages are read during startup.

Further reading here

Filed under: .Net, ,

Pages

Categories

Archives

.Net Hive @ Twitter

Blog Directory by Blog Flux
Computers/Tech blogs