M
m_jones
Background: I have an add-in for Outlook developed in C#. The add-in
uses the Microsoft Updater Application Block (and the Enterprise
Library) to download and install updates for itself. By default the
updater uses the BITS downloader to download updates. Our client
wanted to avoid having to deploy BITS to all their customers. The
solution was to develop a custom HTTP Downloader. The HTTP Downloader
was developed and runs successfully on my development machine.
Problem: In order to create the custom downloader it was necessary to
add a reference in our project to
Microsoft.Practices.EnterpriseLibrary.Configuration.dll. For some
reason, adding this single reference prevents the add-in from
installing properly in my test environment and therefore preventing it
from loading in Outlook (Test Environment is a Virtual PC running WinXP
SP2, .NET Framework 1.1, Office 2003).
During my investigation into this issue I looked at the contents of the
..msi file generated by Visual Studio and used to install the add-in.
For some reason, when I add the reference to
Microsoft.Practices.EnterpriseLibrary.Configuration.dll the .msi no
longer contains any of the registry entries necessary for loading the
add-in. If I remove the reference, all of those registry entries
return. The only change made to the project was to add a single
reference.
Has anyone seen this? Any suggestions would be greatly appreciated.
Thanks,
Mark
uses the Microsoft Updater Application Block (and the Enterprise
Library) to download and install updates for itself. By default the
updater uses the BITS downloader to download updates. Our client
wanted to avoid having to deploy BITS to all their customers. The
solution was to develop a custom HTTP Downloader. The HTTP Downloader
was developed and runs successfully on my development machine.
Problem: In order to create the custom downloader it was necessary to
add a reference in our project to
Microsoft.Practices.EnterpriseLibrary.Configuration.dll. For some
reason, adding this single reference prevents the add-in from
installing properly in my test environment and therefore preventing it
from loading in Outlook (Test Environment is a Virtual PC running WinXP
SP2, .NET Framework 1.1, Office 2003).
During my investigation into this issue I looked at the contents of the
..msi file generated by Visual Studio and used to install the add-in.
For some reason, when I add the reference to
Microsoft.Practices.EnterpriseLibrary.Configuration.dll the .msi no
longer contains any of the registry entries necessary for loading the
add-in. If I remove the reference, all of those registry entries
return. The only change made to the project was to add a single
reference.
Has anyone seen this? Any suggestions would be greatly appreciated.
Thanks,
Mark