A directory of wonderful thoughts
If you’re using a application-wide FirstChanceException handler, this is great for covering lots of bases at once, it helps make sure that you can catch (and record) an exception even if it happens with a bit of code you didn’t expect. However, the scope of the handler is what it is, so accessing state, and […]
Retrieving state in a FirstChanceException in .NET — Network Programming in .NET
This is something I wrote for an application I’m developing. This is an implementation of INotifyPropertyChanged that requires no backing fields, just call Set(value) or Get(). Internally it uses a dictionary to store the state and even reuses ChangedEventArgs
The source code can be found at:
https://github.com/ebalynn/StatefulViewModel/
Here is the extract from the ViewModel class that does all the heavy lifting:
Note to myself – Excellent article on the worker services in .NET Core 3:
It’s a very rare requirement, but sometimes in .NET you have to create your own primitive and make it behave as close as possible to a native CTS (common type system) type. “That shouldn’t be hard” would be your first thought, until you start considering all the scenarios in which it could be used. Continue reading “Creating your own primitive type”
C# 7 provides a very powerful feature from the performance standpoint. This feature is returning by ref. Essentially this allows for value types to be returned without having to copy them.
The guidelines are normally that you shouldn’t use a struct with too many fields. Various sources quote various size guidelines. Whenever the struct was over the prescribed size it was recommended that you pass it by reference.
With the new syntax for returning types by reference, it’s now more convenient (no more methods returning via out parameter) to use structs.
In performance critical scenarios where you need to avoid polluting managed heap with too many Gen #0 objects using structs has now become more natural. In the past dealing with structs was somewhat cumbersome if you dealt with a large number of fields and needed to avoid copying of values.
I have worked on a large application at McLaren – Telemetry Acquisition System that is supplied to all teams. The performance of the application is very critical as it has to process gigabytes of telemetry data. We have used structs extensively to squeeze out every bit of performance from .NET runtime.
I think it’s my second favourite feature after value tuples.
The idea is very simple, you cherry-pick the applications, click on get installer and you get the installer with all the latest applications you selected as one file.
Next time you reinstalling Windows go to https://ninite.com/ and create yourself and installation package
Invoking event handlers in C# has always been a bit of a pain, because an event with no subscribers is usually represented as a null reference. This leads to code like this:
It’s important to use the handler local variable, as if instead you access the field twice, it’s possible that the last subscriber will unsubscribe between the check and the invocation:
Now this can be simplified slightly using an extension method:
Then in each event, you can write a single line:
However, this means having a different extension method for each delegate type. It’s not too bad if you’re using EventHandler but it’s still not ideal.
The null-conditional operator (?.) in C# 6 isn’t just for properties. It can also be used for method calls. The compiler does the right thing (evaluating the expression only once) so you can do…
View original post 407 more words
Here is an excellent article on how to write your own shell extensions in C#
http://www.codeproject.com/Articles/522665/NET-Shell-Extensions-Shell-Icon-Handlers
I’m amazed at how CSS has changed since the last time I looked into it. Something that previously required a tone of Javascript is now possible to implement by putting a single line of CSS code:
div {
transition: all 0.5s ease;
background: red;
padding: 10px;
}
div:hover {
background: green;
padding: 20px;
}
That’s all it takes to transform a div from red to green and back again!
Source: http://css-tricks.com/almanac/properties/t/transition/
I’m amazed at how CSS has changed since the last time I looked into it. Something that previously required a tone of Javascript is now possible to implement by putting a single line of CSS code:
div {
transition: all 0.5s ease;
background: red;
padding: 10px;
}
div:hover {
background: green;
padding: 20px;
}
That’s all it takes to transform a div from red to green and back again!
Source: http://css-tricks.com/almanac/properties/t/transition/
Elliot Balynn's Blog 