![]() ![]() ![]() ![]() We only need the one DLL from the toolkit, so use WinZip or similar to extract the wixca.dll file from the download.ġ) Now establish what the exact command is you wish to run. If you don't already have it you can download the full WiX tookit from this link The method devised makes use of wixca.dll, a DLL supplied in the WiX toolset. This article outlines a method that can be used to invoke the executable to run under the Windows subsystem and not the Command subsystem and thereby avoids the appearance of the command window. ![]() The problem with commands like these is that when the Custom Action executes, a command window usually appears on the screen and, besides generally looking untidy, may cause confusion to the end user during installation. The custom action might, for example, call NET.EXE as follows : One example might be to call the NET.EXE executable to stop a service (OK, I know it's not a great example as you should be using the ServiceControl table here ) It is geared towards InstallShield users, but can easily be adapted for WISE &c.įrom time to time it is convenient to create a custom action that calls (say) an executable that is already part of the Operating System but which runs in the COMMAND subsystem. Seems like a good time to post and article I wrote on this subject some time ago. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |