setup project
-
Hi, How do I get the installation path that the user selects while installing ? If I had to copy a specific file from a folder in the local machine under the path where the application is installed , How do I do it ?(for eg : if I have a file named aaaa.dll which is tend to change frequently in the same folder as I have the setup.exe , if the installation path selected is C: and I have created 2 folders bin & data under it using File system editor in setup .How can I copy aaaa.dll to bin & data folder at runtime). Thankx in advance Priya
-
Hi, How do I get the installation path that the user selects while installing ? If I had to copy a specific file from a folder in the local machine under the path where the application is installed , How do I do it ?(for eg : if I have a file named aaaa.dll which is tend to change frequently in the same folder as I have the setup.exe , if the installation path selected is C: and I have created 2 folders bin & data under it using File system editor in setup .How can I copy aaaa.dll to bin & data folder at runtime). Thankx in advance Priya
what kind of set up tool that you are using. Rock Throught The Night
-
what kind of set up tool that you are using. Rock Throught The Night
-
Hi, How do I get the installation path that the user selects while installing ? If I had to copy a specific file from a folder in the local machine under the path where the application is installed , How do I do it ?(for eg : if I have a file named aaaa.dll which is tend to change frequently in the same folder as I have the setup.exe , if the installation path selected is C: and I have created 2 folders bin & data under it using File system editor in setup .How can I copy aaaa.dll to bin & data folder at runtime). Thankx in advance Priya
Hi, Priya You will need to add a custom action to your setup project. Pass the [TARGETDIR] variable to your custom action: CustomActionData = /instdir=[TARGETDIR]\\ (the last "\\" is neccessary for correct passing of paths) Get the "instdir" parameter in the custom installer class's Install method in the custom action project: [code] Dim instdir As String = Me.Context.Parameters("instdir") [/code] That's it Regards, Serge (Logic Software, Easy Projects .NET site)
-
Hi, How do I get the installation path that the user selects while installing ? If I had to copy a specific file from a folder in the local machine under the path where the application is installed , How do I do it ?(for eg : if I have a file named aaaa.dll which is tend to change frequently in the same folder as I have the setup.exe , if the installation path selected is C: and I have created 2 folders bin & data under it using File system editor in setup .How can I copy aaaa.dll to bin & data folder at runtime). Thankx in advance Priya
You can interop with the msi.dll COM server to get access to the database and package methods, or you can P/Invoke the exported C-style functions from the same DLL. You can query the component's installation directory at any time using
MsiGetComponentPath, where you pass the ProductCode, the ComponentId, and a path buffer plus it's maximum declared size. See the Windows Installer SDK in MSDN[^] for more details. There's a catch, though: VS.NET's Windows Installer project sucks. It will generate new ComponentIds each time you recompile and doesn't let you specify a feature/component layout. I'd recommend getting a decent Windows Installer development environment like Wise for Windows Installer[^]. Finally, whether or not that file changes often Windows Installer is designed to allow for such changes and you should not copy the file manually. Windows Installer is an installation package manager - not just a simple install runtime. Just add the changed file to your setup project and make sure that the project's property "RemovePreviousVersions" is set to True and that the "UpgradeCode" never changes. Also change the "Version" according to how much changed (it's really up to you). If you'd like, you can generate a patch (.msp file) that is the difference between two installation packages. Again, though, because of the Windows Installer's short-comings this would be difficult and would require manual, post-build steps. This is the correct way to distribute updates to your product. If you're interested in Windows Installer, see Widnows Installer[^].Microsoft MVP, Visual C# My Articles