.NET Framework 3.5


Daniel Moth has a good post describing .NET Framework 3.5… I though i’d share part of it here as it is likely better than one I could do… thanks Daniel.

 

Our goal with the .NET Framework 3.5 was to make it very easy for customers to adopt while providing some really interesting new value.  The “easy to adopt” comes from what we call the “Redbits”.. There we are using the same core bits as .NET Framework 2.0 and 3.0 (we just rolled in an SP1 to fix customer reported issues and such)… there should be no breaking changes there and these SPs will be made available on windows update for everyone with 2.0 and\or 3.0… 

The new value comes from the “greenbits” that are brand new assemblies. 

 

Daniel also has a good list of the new stuff in .NET Framework 3.5

1. System.Data.Linq.dll – The implementation for LINQ to SQL.
2. System.Xml.Linq.dll – The implementation for LINQ to XML.
3. System.AddIn.dll, System.AddIn.Contract.dll – New AddIn (plug-in) model.
4. System.Net.dll – Peer to Peer APIs.
5. System.DirectoryServices.AccountManagement.dll – Wrapper for Active Directory APIs.
6. System.Management.Instrumentation.dll – WMI 2.0 managed provider (combined with System.Management namespace in System.Core.dll).
7. System.WorkflowServices.dll and System.ServiceModel.Web.dll – WF and WCF enhancements (for more on WF + WCF in v3.5 follow links from here).
8. System.Web.Extensions.dll – The implementation for ASP.NET AJAX (for more web enhancements, follow links from here) plus also the implementation of Client Application Services.
9. System.Core.dll – In addition to the LINQ to Objects implementation, this assembly includes the following: HashSet, TimeZoneInfo, Pipes, ReaderWriteLockSlim, System.Security.*, System.Diagnostics.Eventing.* and System.Diagnostics.PerformanceData.

In addition we are adding System.Web.Extensions.dll with the LinqDataSource, Asp.NET Ajax support and asp:ListView

 

Read the full post for more details.

Comments (8)

  1. Tom says:

    Why did they call it "HashSet" – why not "Set"? I thought one of the principles in FDG is that the name of a class should reflect its purpose, not its implementation.

  2. Tom,

    We would have liked to use Set but "set" is a keyword in both C# and VB.  So we chose to name it HashSet instead.  More information on this is available in the comments of the following blog post: http://blogs.msdn.com/bclteam/archive/2006/11/09/introducing-hashset-t-kim-hamilton.aspx

    Thanks,

    Justin Van Patten

    CLR Program Manager

  3. Sam Gentile says:

    Temps near 100 F and 100% humidity make for some pretty uncomfortable days Windows Workflow Sometimes

  4. Juan Ignacio Gelos says:

    "…there should be no breaking changes there and these SPs will be made available on windows update for everyone with 2.0 andor 3.0…  "

    How about this for a breaking change?

    http://community.devexpress.com/blogs/ctodx/archive/2007/07/31/system-data-breaking-changes-in-latest-net-framework-update.aspx

    Or is it considered a bug-fix?…

    Cheers

  5. Piyush says:

    i want answer on my question so let me ask how i can get my answer in microsoft corporation people

    regard

    Piyush

  6. Microsoft released the .NET Framework 3.5 on Monday, November 19.2007. We have installed and tested SpeedTrace dot.NET Profiler against the new .NET Framework 3.5. During preliminary tests, SpeedTrace performed properly and no errors were detected. W

  7. Sam Gentile says:

    Temps near 100 F and 100% humidity make for some pretty uncomfortable days Windows Workflow Sometimes

  8. Temps near 100 F and 100% humidity make for some pretty uncomfortable days Windows Workflow Sometimes you have to go beyond the two root models of WF which are Sequential and State. We needed to and ended up using a hybrid of rules driven and state. Matt

Skip to main content