BT

LINQ to SQL Changes in .NET 4.0

by Jonathan Allen on  Jun 02, 2009

Damien Guard of Microsoft’s Data Programmability has posted a rather long list of the changes to LINQ to SQL. While they are still committed to Entity Framework over the long run, this will do much to alleviate the fear LINQ to SQL will be completely neglected in the mean time.

What Is .NET 4.0 Beta 1 Going to Bring to PLINQ?

by Abel Avram on  Apr 30, 2009

Ed Essey, a Program Manager on the Microsoft Parallel Computing team, wrote on the latest enhancements to PLINQ that are to appear in .NET 4.0 Beta 1 that is to be released soon. Some of them are: “With” Operators Pattern, Execution Mode, Cancellation, Refactoring, Performance Improvements.

Disabling View-State Made Simpler in ASP.NET 4.0

by Jon Arild Tørresdal on  Jan 30, 2009

ASP.NET 4.0 offers a new mechanism to enable/disable the view-state, controlling it becoming much easier than before. To store their state, ASP.NET controls have used view-state, enabled by default until now. This behavior resulted sometimes in large amounts of data being transferred between the client and the server.

.NET and Dynamic Languages

by Jonathan Allen on  Oct 31, 2008 6

In the months and years ahead, dynamic languages are going to take on an increasing important role in the .NET platform. To support this Microsoft is heavily investing in integration between the dynamic languages and the CLR.

.NET 4.0 CTP, Visual Studio 2010 CTP and Azure Tools CTP Are Available

by Abel Avram on  Oct 28, 2008

Microsoft has announced the availability of the next generation of .NET Framework 4.0 CTP, Visual Studio 2010 CTP and the new Windows Azure Tools for VS CTP during PDC 2008.

C# Feature Focus: Co- and Contra-variance

by Jonathan Allen on  Oct 27, 2008 1

With .NET 4, C# 4 will be able to support co- and contra-variance in generic interfaces. If you are not familiar with them, think of it as the reason why you can't pass an IEnumerable to a function expecting an IEnumerable.

.NET 4 Feature Focus: Type Embedding and Equivalence

by Jonathan Allen on  Oct 27, 2008

In .NET 4 types will no longer be restricted to a single assembly. A single type, or part of a type, can be extracted from one assembly and placed into another. Why would you do this? Well first off all, to reduce the cost of including the Office Primary Interopt Assemblies from several megabytes to about 2KB by only including what you actually need.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2013 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT