In short, no, you can’t. Long answer, extension methods are just syntactic sugar. IE: If you have an extension method on string let’s say: public static string SomeStringExtension(this string s) { //whatever.. } When you then call it: myString.SomeStringExtension(); The compiler just turns it into: ExtensionClass.SomeStringExtension(myString); So as you can see, there’s no way to … Read more
A couple points: First off, the proposed feature (implicit “this.” on an extension method call) is unnecessary. Extension methods were necessary for LINQ query comprehensions to work the way we wanted; the receiver is always stated in the query so it is not necessary to support implicit this to make LINQ work. Second, the feature … Read more
Java does not support extension methods. Instead, you can make a regular static method, or write your own class.
You should create Begin and End extension methods as well. And if you use generics, you can make the call look a little nicer. public static class ControlExtensions { public static void InvokeEx<T>(this T @this, Action<T> action) where T : Control { if (@this.InvokeRequired) { @this.Invoke(action, new object[] { @this }); } else { if … Read more
First, here’s a very quick tutorial on extensions for those learning c#/Unity for anyone googling here: Make a new text file HandyExtensions.cs like this … (note that somewhat confusingly, you can use any name at all for the class which “holds” your extensions – the actual name of the class is never used at all, … Read more
In .NET 4 you can do this: String.Concat(Enumerable.Repeat(“Hello”, 4))
The only advantage of extension methods is code readability. That’s it. Extension methods allow you to do this: foo.bar(); instead of this: Util.bar(foo); Now there are a lot of things in C# that are like this. In other words there are many features in C# that seem trivial and don’t have great benefit in and … Read more
That will work fine (no exception). Extension methods don’t use virtual calls (i.e. it uses the “call” il instruction, not “callvirt”) so there is no null check unless you write it yourself in the extension method. This is actually useful in a few cases: public static bool IsNullOrEmpty(this string value) { return string.IsNullOrEmpty(value); } public … Read more
This post clearly describes when Include does and doesn’t have effect. The critical part is the shape of the query, i.e. the selected columns. If anything changes the shape after an Include, the Include not longer works. In your query the shape changes four times, in these statement parts: from q in _context.Cars: the query … Read more
Basically you’re talking about aborting an action which (as far as we know) has no graceful way of aborting. That means there’s going to be no safe way of aborting it. Thread.Abort is just not a nice thing to do – there are various race conditions and ugly situations you can get into (see the … Read more