Imagine that we want to be notified if a directory files changed. In general, when we use files, we don’t need to have a real time application. Moreover, if we change many files in same time, we perhaps don’t need to have many notification and one notification at the end could be enough.   For this case, Rx and particularly Throttle method is very useful. In our case, I create a FileChangedEvent which can contain notification information we may need. public class FileChangedEvent { }  

I already made two videos on WCF Async Queryable Services architecture and tooling . I just published a new one to present WAQS features . WCF Async Queryable Services Features Now you can enjoy with WAQS! Give me your feedbacks please

Using WAQS tooling is not something very intuitive. So I made a video to explain you how to do. Now you can enjoy with WAQS!

In my video on WCF Async Queryable Services tooling, I talked about a snippet. You can download it here .

If you use Roslyn and you want to simplify the code rewriter, I recommend you to install my NuGet package RoslynHelper .

I published a POC using Roslyn to improve C# compiler. Enjoy! :)

If you follow me on twitter, you probably know that I’m working on a project named WCF Async Queryable Services. I made my first video on WCF Async Queryable Services to explain my architecture. WCF Async Queryable Services - Architecture Thanks for your feedbacks

When we use Collection initializers, we can’t write many instructions in the initialization: public class C { public int MyProperty { get ; set ; } } var test = new   List < C >() { new   C { MyProperty = { int i = 1; i += 1 ; return i; } } }; This code does not compile.   But, using LINQ Expressions, it does! var v = Expression .Variable( typeof ( int )); var test = Expression .Lambda< Func < List < C >>>(     Expression .ListInit(        

I recently blogged to explain why I found that Include method is an anti-pattern IMHO. EF: Why Include method is an anti-pattern IMHO? EF: Why Include method is an anti-pattern IMHO even with many to one navigation properties? 2/3 EF: Why Include method is an anti-pattern IMHO? 3/3 EF- Why Include method is an anti-pattern IMHO- Conclusion But I didn’t show how to do it with many to many relationships. I will do on this post. This is my model: I have 1000 products, 100 categories and 4497 associations

Two days ago, I spoke at Microsoft TechDays in Paris, France on Roslyn. I made several demos including one where I build my own C# compiler that allows me to add features on C#.   This compiler supports AOP in order to implement INotifyPropertyChanged. So with this code: [NotifyPropertyChanged] public   class   TestNotifyPropertyChanged {     public   int P1 { get ; set ; }       private   string _p2;     public   string