custom-action

I have an installer that needs to access the registry and copy and remove files using custom actions. In Windows XP the installer works just fine, but in Vista and 7, the installer shows an error because it cannot access a folder, but if I run the installer as administrator everything works. So, I need the installer to be able to run the custom action as administrator even if the MSI wasnt run this way (need the installer to be run by regular users). I tried using an EXE at the beginning of my installation to modify the registry and allow the MSI to run normally but I dont think that's a very

For a custom action, I'm setting to Name to XmlPreprocess.exe (a CodePlex utility) and arguments to: /x:"[SETTINGSFILE]" /i:"[TARGETDIR]web.config" /e:[ENVIRONMENTBUTTON] [CUSTOMSETTINGS] >[TARGETDIR]XmlPreProcess.log SETTINGSFILE is supposed to be coming from a custom form page I added, and ENVIRONMENTBUTTON is the value of one of my radio buttons. Is there any way to get the redirect to work? It's not creating the .log file. Is there any other way to see the results of the custom action? How can I even confirm if it ran? What if I would like to see what parms were sent to it? Update 3: - For

I want to achieve following custom view over UIViewController . What is the best way to acheive it rather then using addSubview I want to use some thing better. I previously use following but i want to use some thing better now [self.view addSubview:NotConnected.view]; [self.view removeFromSuperview]; I have implemented code using https://github.com/wimagguc/ios-custom-alertview . I didn't prefer to use library so how is it possible to customise UIViewController over another UIViewController as shown in image above. I use - (IBAction)ContinueToPayment:(id)sender { PayByVC *Newpage = [[PayByVC

I am writing a managed custom action. I am using the DTF Framework from Windows Installer Xml to wrap the managed dll into a usable CA dll. The CA does what it is supposed to, but I am still having trouble with error handling: Dim record As New Record(1) ' Field 0 intentionally left blank ' Field 1 contains error number record(1) = 27533 session.Message(InstallMessage.Error, record) The above code produces the following text shown in the MSI log: MSI (c) (C4 ! C6) [13:15:08:749]: Product: TestMSI -- Error 27533. The case-sensitive passwords do not match. The error number refers to the code

I'm creating a installer for a c# windows project using VS 2008. I'm trying to write a custom action that copies a settings file from the source directory of the MSI file stored on a file server (e.g. \server\fileshare\myappinstaller\mysetting.xml) to the target directory on the computer on which my application is been installed (e.g. C:\Program Files\My App). The settings file can't be added in to the installer as it will contain settings with will be unique to the customer installing the app. Does anyone have code (preferably C# or VB.NET) for such a custom action? Alternately does anyone

I've created a simple winforms app and a custom installer. It all seems simple enough but I get the following popup and error details in the event log. The description for Event ID 11001 from source MsiInstaller cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Product: Custom Action Tester --

I have a VS2010 WiX project with a main .wxs file and an empty .wxs file. The empty .wxs is overwritten in the prebuild event of the project, using heat.exe to harvest everything from a console exe. The exe has InstallUtil hooks, and in the days of VS setup project the exe was installed as a Service. I tried to use the <ServiceInstall> bits in WiX, but when I specified the executable and other elements to get the Service installed, light complained of a collision between the .exe in the main .wxs and the .exe in the heat-generated .wxs. I think Custom Action is not the best way to do the