|
I really like the new keyword async[^], though it is only available in Delphi Prism. The concept of futures[^] is just as nice. I hope both will make it into C# 4.
Here's a list of neat features[^] that are available in .NET 3.5, but tricky to use in C#.
I never would have thought I'd says that one day, but ... I'm beginning to like Prism... ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
This statement is false.
|
|
|
|
|
You can, obviously you must set your "language version" to 3, but you can.
Sometimes you have to include a little something though, such as for Extension Methods you need somewhere in your code:
namespace System.Runtime.CompilerServices
{
[AttributeUsage(AttributeTargets.Method | AttributeTargets.Class | AttributeTargets.Assembly)]
public sealed class ExtensionAttribute : Attribute
{
public ExtensionAttribute() { }
}
}
And then it will work.
|
|
|
|
|
And what will that give you? Does that simply allow you to mark methods as Extension Methods, compile with the C# 2.0 compiler, and run it against the .net 3.5 runtime?
If so, I'm all for it; I think that's the way Extension Methods should have been implemented, there was no need to alter the language.
|
|
|
|
|
It (also) allows to C#3 compiler to insert that attribute itself and then allows you to run it with the .NET 2.0 runtime and library.
|
|
|
|
|
Including that snippet and compiling with CSC 3.5 results in:
warning CS1685: The predefined type 'System.Runtime.CompilerServices.ExtensionAttribute' is defined in multiple assemblies in the global alias; using definition from 'c:\xt.cs'
and
xt.cs(26,42): warning CS0436: The type 'System.Runtime.CompilerServices.ExtensionAttribute' in 'c:\xt.cs' conflicts with the imported type 'System.Runtime.CompilerServices.ExtensionAttribute' in 'c:\Program Files\Reference<br />
Assemblies\Microsoft\Framework\v3.5\System.Core.dll'. Using the type defined in 'c:\xt.cs'.
and
xt.cs(26,10): error CS1112: Do not use 'System.Runtime.CompilerServices.ExtensionAttribute'. Use the 'this' keyword instead.
|
|
|
|
|
Well it would. You don't need this if you're already using the 3.5 assemblies. The whole point of this snippet is avoiding the 100MB download for your client while using Extension Methods anyway
|
|
|
|
|
You deliver code that compiles with warnings? 
Extension Methods are unnecessary syntactic sugar and I see no reason to "avoid" .net 3.5, I simply install it on the systems that run my code.
|
|
|
|
|
It doesn't give warnings when you don't use the 3.5 libs
The reason to "avoid" it is that people generally don't want to download yet an other huge framework, it's usually hard enough to get people to agree to install 2.0
|
|
|
|
|
harold aptroot wrote: It doesn't give warnings when you don't use the 3.5 libs
How do you manage that?
|
|
|
|
|
Hm well, put your "language version" on 3, set your .NET target to 2.0, and just use an extension method (regular syntax)
I'm afraid the compiler doesn't want you to use the attribute yourself
|
|
|
|
|
At our office, we're still using .NET 2.0. I'm sure we'll upgrade to 3.0 sometime this year, but we're doing fine without it.
|
|
|
|
|
Jason Barry wrote: .NET 2.0
You should feel better. A few in my region (Chennai, India) are to support clients still clinging onto 1.0 (not 1.1 even) framework.
Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips
The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!
|
|
|
|
|
I don't use any of them so would like an option to say none.
|
|
|
|
|
|
I do not use .NET so the answer is none.
John
|
|
|
|
|
|
|
Evil peopleses don't know what it missessess!
|
|
|
|
|
|
I wish my company would move up to .NET we are still developing our internationally used product in C++ using Visual Studio 6.
So, sadly, its none for me too.
|
|
|
|
|
|
Isn't that like having an option on the Pizza hut menu 'No pizza' for $0.00? 
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
|
|
|
|
|
No. The question here presupposes that you are using 3.5 what about an option to say we haven't felt the need to use any of the features so the survey can reflect that it's not being used and help MS focus on what features people are using, i.e. features from 3.0 and 2.0.
|
|
|
|
|
If you're not using .net 3.5 I don't know why you would want to vote on a survey specifically aimed at those that are using .net 3.5.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
|
|
|
|
|
People love to see their post count Rise. So do I! 
To the point: You don't know what your'e missing...
I use all the features that are availabe in C#....
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
