Month: September 2009

If you want to create a customeventlog during setup, in a custom action. You can open a App.config file containing the log4net configuration and read the settings from that file at runtime.
You also can add appenders or remove appenders at runtime, but in this case I just wanted to read the configuration and create a custom eventlog:

       private string _productInstallationFolder = null;
/// <summary>
/// Returns C:\Program Files\MyCompany\MyProduct or C:\Program Files (x86)\MyCompany\MyProduct depending on the platform.
/// </summary>
public string ProductInstallationFolder
{
get
{
if (string.IsNullOrEmpty(_productInstallationFolder))
{
var programFilesFolder = System.Environment.GetFolderPath(System.Environment.SpecialFolder.ProgramFiles);
_productInstallationFolder = Path.Combine(programFilesFolder, @"MyCompany\MyProduct");
}
return _productInstallationFolder;
}
set
{
_productInstallationFolder = value;
}
}
public void CreateCustomEventLog()
{
XmlConfigurator.Configure(new FileInfo(string.Format("{0}.config", this.ProductInstallationFolder))); 
           var repository = LogManager.GetRepository() as Hierarchy;
if (repository != null)
{
var appenders = repository.GetAppenders();
if (appenders != null)
{
foreach (var appender in appenders)
{
if (appender is EventLogAppender)
{
var eventLogAppender = appender as EventLogAppender;
EventLog.CreateEventSource(eventLogAppender.ApplicationName, eventLogAppender.LogName);
// Close application to allow the Windows eventlog service to refresh.
// When applcation is restarted the first log event will create the log file.
}
}
}
}
}

If you use the XmlConfigurator.Configure() . log4net function in a setup custom action to initialize the log4net logging, you can get the error:

Could not load file or assembly ‘log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=1b44e1d426115821’ or one of its dependencies. The system cannot find the file specified.

This is because the msi package installs the assembly containing the custom action that uses the log4net assembly in a folder: C:\Program Files\MyCompany\MyProduct, but when the setup is started from a folder C:\Temp, the current working folder is C:\Windows\SysWOW64 on a x64 windows. The folder C:\Program Files\MyCompany\MyProduct is there for not included in the standard .NET assembly search path. To add the folder C:\Program Files\MyCompany\MyProduct to the .NET assemlby search path use the following class:

By the way this will also occur when you use custom configuration sections in you’re the App.config of you’re program (exe) and want to use the custom configuration sections during you’re msi installation with a custom setup action.

public class AssemblyLoader
{
private string _productInstallationFolder = null;
/// <summary>
/// Returns C:\Program Files\MyCompany\MyProduct or C:\Program Files (x86)\MyCompany\MyProduct depending on the platform.
/// </summary>
public string ProductInstallationFolder
{
get
{
if (string.IsNullOrEmpty(_productInstallationFolder))
{
var programFilesFolder = System.Environment.GetFolderPath(System.Environment.SpecialFolder.ProgramFiles);
_productInstallationFolder = Path.Combine(programFilesFolder, @"MyCompany\MyProduct");
}
return _productInstallationFolder;
}
set
{
_productInstallationFolder = value;
}
}
/// <summary>
/// Add an evenhandler for adding a folder to the .NET assemlby search path.
/// </summary>
public void BindAssemblyResolveEventHandler()
{
var currentDomain = AppDomain.CurrentDomain;
currentDomain.AssemblyResolve += this.LoadAssemlbyFromProductInstallationFolder;
}
/// <summary>
/// This function is called when the .NET runtime searches for an assemlby to load and can't find that assembly in the current search path.
/// The current search path includes "bin folder application", the global assemlby cache, system32 folder etc.
///
/// This function adds a folder to the current search path at runtime.
///
/// An assembly can be a dll or exe, the ResolveEventArgs argument does not cotain this information.
/// The code will first check if a dll exist in the given folder, if found it loads the dll.
/// If the dll is not found, the code checks if an executable exists in the given folder, if found it loads the exe.
/// </summary>
/// <param name="sender"></param>
/// <param name="args"></param>
/// <returns></returns>
public Assembly LoadAssemlbyFromProductInstallationFolder(object sender, ResolveEventArgs args)
{
Assembly result = null;
if (args != null && !string.IsNullOrEmpty(args.Name))
{
var folderPath = (new FileInfo(this.ProductInstallationFolder)).DirectoryName;
var assemblyName = args.Name.Split(new string[] { "," }, StringSplitOptions.None)[0];
var assemblyExtension = "dll";
var assemblyPath = Path.Combine(folderPath, string.Format("{0}.{1}", assemblyName, assemblyExtension));
if (!File.Exists(assemblyPath))
{
assemblyExtension = "exe";
assemblyPath = Path.Combine(folderPath, string.Format("{0}.{1}", assemblyName, assemblyExtension));
}
result = Assembly.LoadFrom(assemblyPath);
}
return result;
}
}

If you want to start the debugger after installation of you’re product with a Microsoft Visual Studio 2008 setup msi package, use a Installer class and custom actions and then add a Debugger.Break() on the AfterInstall event:

[RunInstaller(true)]
public partial class ProjectInstaller : Installer
{
public ProjectInstaller()
{
InitializeComponent();
}
/// <summary>
/// Event fires after installation
/// </summary>
/// <param name="sender"></param>
/// <param name="e"></param>
private void AfterInstallation(object sender, InstallEventArgs e)
{
Debugger.Break();
}
/// <summary>
/// Event fires before uninstallation
/// </summary>
/// <param name="sender"></param>
/// <param name="e"></param>
private void BeforeUninstallation(object sender, InstallEventArgs e)
{
}
}