Feature Flags is useful method to integrate rapidly new functionality, finished or unfinished, into the product. But there are also some traps.
There is good reason to create NuGet packages automated. This will eliminate the difficult and error-prone manual process. Creating and publishing of NuGet packages isn’t hard by the Team Foundation Server (TFS) build, except of prerelease versions.
Last week I evaluated couple of State Machines. It wasn’t some structural evaluation, rather quick overview what is today in the market. I was just about to have something lightweight and easy to use so I have looked into Appccelerate and Stateless from Nicolas Blumhard. As I went through my sample I asked myself: Why we don’t use State Machines frequently? I asked couple of colleagues if they do. They don’t. Do I? No.
Sometimes you would like to start IIS Express without hitting the F5 or Shift F5 in Visual Studio. This is especially helpful when you would like to run integration, performance or load tests continuously on your own machine. To enable this scenario you need to start IIS Express as a background process, otherwise the load or performance test will hang. One of the possibilities to achieve this is PowerShell.
Normally when you create AutoMapper profile, it is you responsibility to register them. However with the dependency injection container (DI) you have great possibility to automate this.
One of products I’m working on is using Telerik’s Kendo UI. It is nice, but sometimes not so intuitive and not very well documented, product suite.
Before I show you the cooperation between the Autofac and Microsoft Extensibility Framework (MEF) I want bring you in short my opinion why is there the place for both of them. If you are try to search around, you will find lot of posts which describes the differences between the MEF or Autofac, also, you will find lot of posts which advocates to use MEF as IoC Container, or, on other side, to use Autofac as replacement of the MEF.