I created an installer back in 2010 and used some .NET Installer Class Actions to install some Windows Event Log sources. I need to add a similar action for a new installer I'm currently putting together, so I'm looking back at this older installer for how to do it.
Thank you for the interesting link. I opened the compiled MSI in Orca and examined the tables mentioned in the article. The record in the File table for the Advantage.Application.dll file had the expected value for the Version field of "1.9.0.0" ( screenshot ). The Version record in the ...
The primary purpose for the installer is to install the assembly for consumption by a website running on Classic ASP using COM interop. Since the COM registrations are system wide, I want the assembly to be available system wide.
In the future I might want to use the same installer to ...
I originally observed the behaviour on my development machine, I reproduced the behaviour on a VM (also running Windows XP SP3) I use for testing which I consider relatively clean - it is configured as a standard desktop for users in our organisation. I don't have ready access to any ...
I have a fairly straight forward installer which installs an assembly (targeting .NET Framework 4) in the Global Assembly Cache and registers the assembly for COM interop.
Everything works as expected apart from when the product is uninstalled. The directory created in the GAC for the assembly, and ...
FOLLOW US
Get the latest news in Application Packaging