Recently we moved our main WPF project to .net framework 4.5 and Visual Studio 2012. Then when I tried to preview some of basic views in Visual Studio designer I faced some strange problems. We have several user controls that we use in our views.
In the previous post we saw how to use the built in Trace class for logging facilities. However the Trace class is not the latest Microsoft’s recommended way for logging your application. In this post I will try to present the quickest way of configuring TraceSource and use it for logging purposes.
I’ve used a few version control systems: visual source safe, subversion, git, mercurial and tfs. My current favourite – git. It it’s the most popular one at the moment, but to be honest there’s a good reason for that. It has a gigantic learning curve, but once you grok the concept, everything falls into place. My second choice – subversion. I’ve used it for a long time and it got the job done. The one I am using at the moment – tfs and here’s where the story starts.
Recently we have decided to replace the logging framework we used, because of its not necessary complexity and a bunch of features we did not use and even did not know anything about. The goal was to use the built in System.Diagnostic.Trace facility and cover some of basic requirements we had.
CSS has been around for a while and will stay for a while longer and although I think it’s a good and working ‘language’ it has a few pitfalls – the biggest one being the lack of ability to reuse certain parts. Take colors for example, when you want to style a site you need to repeat the color declaration everywhere you want to set it, so when you change your mind, the only way to implement the changes is search and replace. Now that’s not that bad when you have a small site and one css file, but when the number of files grows, that problem grows along. So what can we do?