Ilove-it.com Website Review

UNITTEST: TYPE IS NOT RESOLVED FOR MEMBER 'LOG4NET.UTIL.PROPERTIESDICTIONARY. I am using log4net as logging framework in the projects I am working on. Every thing seems fine untill I used the LogicalThreadContext of 'log4net.Util.PropertiesDictionary,log4net, Version=1.2.13.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a' What's happening here? Well my code look something like this:     public clas* CreateLogRequestId: ActionFilterAttribute     {         public override void OnActionExecuting(HttpActionContext actionContext)         { This Action filter add's a Guid to every request which can be used during logging like so: In the conversionPattern the %property{requestid} gets filled with the value that is set during the requests. I think it's super nice to use features like this to add some more logic to the logging.  But when I created unit tests for the ActionFilterAttribute above the unit test will fail with the exception. Apparently this can be fixed with the following code in your unit tests clas* that uses the LogicalThreadContext.             CallContext.FreeNamedDataSlot(log4net.Util.LogicalThreadContextProperties);         } If you are a Front-end developer you may have worked with several command windows open. I always have a minimal of 3 or 4 command windows open. One for Git, one for npm start (building projects), one for npm test (testing projects) and most of the time also one for some other stuff I am doing. So, most of the time one of my desktops look something like this. I like to have all the console windows visible to be able to see live updates when watching files. That why I like to use the Windows On very annoying thing about several windows is that when you have some other windows (like a browser) temporarily on the desktop with the consoles is that when using Alt + Tab only focus one of the command windows. The other thing I don't like is the face of having contains Tabs and Splitpanes! Yes.. That what I need. Default it looks like below.