Is this also true for VS? If that is the case then I know why my code isn't working. That doesn't seem relevant based on your problem because it refers to debugging and a missing base. Well, I already managed to do it in another way. Instead of saving the installdir during the installation process I now get the AssemblyPath from system.
Reflection during the first startup and save that directly. But thanks for your help anyway. This can be done manually using orca or automatically by running a vbs script found here as a VS PostBuildEvent: cscript. Ben Adams Ben Adams 91 1 1 silver badge 4 4 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science.
Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Linked 4. Related 3. If the property name you specify does not exist, Windows Installer will create it for you. Use of an explicit. One of the useful features of these direct call custom actions in which your code is called directly from Windows Installer is the ability to write your own entries to the Windows Installer log.
You have to enable it at install time with a command line like this:. The first line is a standard logging entry reporting that the custom action is being called; the second line is the output from the call to LogMessage in the custom action. This is a useful debugging technique for tracing the path of your custom-action DLL calls.
It has an Exclude property value of True. Visual Studio also lets you use an executable as a custom action. Instead you can use the arguments value shown in Figure 2, the properties window of a custom action, to call the forms program executable in the sample Visual Studio solution. The argument string is surrounded by quotes so that it gets passed as a single string into the main of the receiving program. NET assemblies can contain installer classes, and Visual Studio.
NET lets you call methods in these installer classes as custom actions. If you select a. NET project in the Solution Explorer, a right-click lets you add a component, one of which is an installer class. The boilerplate code generated for you includes an attributed class with [RunInstaller true ], which is what makes it an installer class. To add code of your own, override the existing class methods and use the install method shown here:. This is where you add your install code.
You should also add a corresponding uninstall method that reverses whatever your install code does to the system. By adding a custom action in the same general way as described earlier, you add these calls as custom actions in your setup project.
Figure 3 shows the properties for the custom action. Note that the InstallerClass property is set to True. This is the general format required for passing data into installer classes.
You must put quotes around Windows Installer folder properties so that the internal parsing works correctly. The parameter string ends up in Context. Parameters of the installer class, an IDictionary object with keys and values, and there will be a key corresponding to your CustomActionData key targ in the example. This means that there will be a this. Hans, It's always helpful if you explain exactly what the problem is. What error you are getting on what line.
I'm guessing you're having problem with the Item properties. Usually those become indexers in C , so offhand: foreach XmlNode node in xmlDocument["configuration"]["appSettings"] Double check the docs to make sure. You'll see that the Item property of the XmlDocument has the notation, "In C , this property is the indexer for the XmlDocument class". Also watch out for case sensitivity issues. That's the best guess I can give you.
Your not a bad guesser Hans "Bob Grommes" wrote: Hans, It's always helpful if you explain exactly what the problem is. This discussion thread is closed Start new discussion. Similar topics PHP. NET Framework. So for making a new installer project you have to do the following.
Step 1: Select a setup type project from the New Project dialog. Now we will have a look at Solution Explorer of the setup project. Here you can see the "Set up Sample" project has been added to the solution.
On the top-most bar, you can see some of the icons, each icon is worth opening to explore the functionality of the setup project. Additionally, I have added 2 console apps, 1 window app, and 1 class library just to show how to add multiple projects of various kinds to an installer setup.
We can also choose which project s we want to add and which we don't want since there can be some projects which are only for developers and testers. I am going to explore some of them since in the next step we will use these icons.
Step 2: Clicking on 'file system editor' icon Adding project outputs to the installer: In simpler words, we are now adding files that we actually want to install and these files should be project outputs exe, dlls, etc.
However there are more options available and one can add just a plain file, assembly, etc. All these files along with dependencies referred files will be installed on the user system. Step 3: Define the target installation directory by setting 'Default location' That's It The project is ready as such and you can build it and distribute it.
0コメント