Log4Net is a fairly old framework for logging, but it still serves it's purpose well! A couple of years back I wrote a tutorial on how to use Log4Net, today I stumbled across it, and I am quite pusseled that it is still as relevant today as it was back then. For those looking for a quick tutorial on how to use Log4Net, enjoy:
A sudden freeze in an application can in some cases be a rather cumbersome problem to solve. Many times we don't have any indications why the application freezes no matter if is a Java, C# or C++ application, web site or dll. In some cases we might have a log file to help us look for the source of the hang or freeze, but in many cases we don't have any indications of problem until we suddenly run in Release mode and far from our dev env!
Here I will try to give some guidelines on how to attack this problem.
With the introduction of ReSharper 6, JetBrains proves once again that they are able to surprise us with new and exciting features we just got to have! Lets look at some of the new functionality that's available in ReSharper 6.
Ever had the need to update a release with a minor change to one dll? These steps allow you to update a single dll in a installation from msi etc. Note that all steps are necessary to avoid problems with mismatch in dll references, manifests etc. Trying to update a single dll without these steps normally results in the following error:
Could not load file or assembly MyAssembly, Version=220.127.116.11, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
To avoid these kind of problems you have to make sure your dll's have the correct versions, and that all references are to the correct versions of all the assemblies (Normal problem whene using "1.0.*" as AssemblyVersion"
- Open you Visual Studio solution for the point of the release or todays date if there are no or few changes in the dll you want to update.
- Add you fix or change to your source code
- Go to references in the project you want to update (called project A)
- Delete all the references to projects in your solution (remember the names)
- Copy the same dll's from step 3 som programfiles or wherever you have the release installed. Copy the dll's to the bin/release folder of project A.
In my speech I tried to sum up some of the advantages of using a robust framwork when doing developing in Silverlight or WPF, framworks like: MVVM Light, Caliburn or Caliburn.Micro.
The source code from my speech can be found at filehub.iserialized.com. The example is a fairly simple WPF application, and the GUI it selves sucks, as my focus has been:
- Core Caliburn functionality
- The simplicity of using IoC in the combination WPF and Caliburn
Struggled with following error yesterday:
The request failed with HTTP status 407: Proxy Authentication Required (The ISA Server requires authorization to fulfill the request. Access to th Web Proxy filter is denied)
I guess I am not the only one annoyed by the fact that I could not open Visual Studio by double-clicking a solution file. Finally I looked into this problem and first found a simple, but not satisfying solution:
By setting Visual Studio to not run as an administrator. But if you ever tried running Visual Studio on Windows 7 without admin rights, you know this is not a satisfying solution!