Base types, Collections, Diagnostics, IO, RegEx…
The Visual Studio 2010 and .NET Framework 4.0 CTP is available for download as of last week. The CTP contains new functionality throughout the .NET Framework, including several new BCL features and improvements:
We’re also evaluating a number of potential new features and improvements for .NET 4.0 beta:
There are also a bunch of improvements to the CLR in .NET 4.0. Here’s a high-level summary:
You can learn more about the next version of the CLR in Joshua Goodman’s PDC session on Microsoft .NET Framework: CLR Futures.
Over the next couple of weeks we’ll be posting more about the new functionality that’s available in the CTP. Do note that we’re working on many other improvements for 4.0 that we’re not quite ready to announce just yet.
As always, we’d love to hear what you think of the CTP and announcements so far.
> Does this mean that it may be possible to (safely) write shell extensions in .NET starting with 4.0?
... and MSI custom actions?
jQuery/ASP.NET/ASP.NET AJAX/ASP.NET MVC Visual Studio patched for better jQuery IntelliSense . Yes! Steven
>>>>> Does this mean that it may be possible to (safely) write shell extensions in .NET starting with 4.0?
Right now, we only support in-proc SxS for CLR v2 and v4. So unfortunately it is still not safe to write shell extensions in .NET since you could have a .NET v1.1 app calling a v4 shell extension (which wouldn't work). We're evaluating whether or not we can enable in-proc SxS with 1.0 and 1.1, but have no firm plans at the moment.
>>>>> ... and MSI custom actions?
It may be possible to write a managed MSI custom action with 4.0, but to what extent is currently TBD. In general, the guidance is to avoid custom actions as much as possible (managed or unmanaged), because most installation failures today are attributed to failures inside custom actions. Along those lines, we're actually working to reduce the number of custom actions in the .NET Framework installation as much as we can for 4.0.
Great! But, i have a question:
"In Process Side-by-Side: support for multiple CLR versions running in the same process.". It means on scenarios that have a project in CLR 2.0 and a component (dll) in CLR 1.x, for example (in this case, i can reference the component in my project)?
And about dynamic code in C# and VBx? The CTP has some features?
>>>>> And about dynamic code in C# and VBx? The CTP has some features?
My post is just about what's new in the BCL and CLR in the CTP, but there's lots of other new stuff throughout the .NET Framework and .NET languages.
You may be interested in the following two sessions from the PDC that discuss more about the new enhancements to the next versions of C# and VB:
The VB team also has a nice blog post on the new features in VB 2010:
Hope this helps!
This blog post is to provide a bit more detail about the Code Contracts feature that was recently announced
Can I hope for the following issues?
- Zip packer (I know one from Sharp Develop, but better is included in framework
- CAST crypto algorithm
- SNMP support
And also collection for all controls on the form (recursive)? Not only first level for container.
First showed at the PDC as a part of this Pex session was support for contracts , if you have seen the
I fully applaud the breaking changes in String, but can you REALLY still justify NOT fixing the IsValid method any longer? Sheesh.
"...most installation failures today are attributed to failures inside custom actions."
I've seen this same statement made a couple of times before. I think this is comparable to saying 99% of car accidents occur within 10 miles of home. Since 99% of the time you're within 10 miles of home, of course most accidents are going to occur there.
I don't see how custom actions can be eliminated unless they become standard actions and I haven't seen any major features added to the Windows Installer in a long time, v2.0 maybe. How do you plan on dealing with this for .NET 4?
Previously, when covering some of the additions to the .NET 4.0 Framework such as optional and named
I'm glad to hear that covariance may be showing up. I seem to recall thinking that XmlSerializer would be able to serialize IList<> (instead of just IList and List<>) if it had that feature, but I'm not positive (led to an interesting debate on the MSDN forums)
Couple of questions on assembly refactoring: in 4.0, is Cache still in System.Web, or has it been moved to an assembly that WinForms/WPF apps normally reference? Also, will XAML be getting moved out of WPF and into a more general-purpose serialization assembly? I had read somewhere both were being considered, but I can't find mention of either with regards to 4.0