July 2007
Intermediate to advanced
224 pages
4h 31m
English
One of the most important things that anyone can learn about a new piece of software is how to pick it apart and see what it is really doing. There are two main methods for doing that with CAB. The first, shown next, is with classic debugger tracing. The CAB libraries have been written to output debugger traces in strategic points. All you have to do is turn it on by making the entries shown below in your app.config file. The source name is the name of the class, such as the ModuleLoaderService shown here:
<system.diagnostics> <switches> <add name="MySwitch1" value="all" /> </switches> <sources> <source name="Microsoft.Practices.CompositeUI.Services.ModuleLoaderService" switchName ="MySwitch1"/> </sources> </system.diagnostics> ...
Read now
Unlock full access