Andreas Färber wrote: > (Not sure though what you mean by creating icons almost > automagically, it just specifies the icon to be displayed.)
Typo, read as "shortcuts". >> MS.NET is installed on the machine. Otherwise the MSI engine >> won't be able to execute the custom actions implemented >> by your assemblies. > > Why would that be the case? A replacement would not require > Microsoft .NET but rather Mono. So having determined that Mono is > installed I should be able to run managed code using Mono either way! > In that case it would in theory seem possible for the Mono Project to > provide a native Windows DLL that loads Mono as outlined on the > Embedding page, reflects on the assembly's classes and runs an > Installer class. I was wrong. MS.NET's InstallUtilLib.dll is actually the *unmanaged* DLL implementing the custom action, thus MSI doesn't depend on MS.NET. It should be possible to develop a MSI custom action which mediates between MSI and System.Configuration.Installer. Robert _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
