I have a Basic MSi project in installshield 2012 that allows the user to change the installation path, the default installation path is a fixed path C:\xxx directory. The problem is that if the user decides to install the application in another location that the default C:\xxx folder the system will do that, but it will also create and empty C:\xxx folder!
How can I prevent this?
with regards,
Ehsan
In the components panel you need to go through all the components and on each one change the "Destination" field from C:\xxx to [INSTALLDIR]xxx.
The is problem that a component, possibly a registry component or SQL component, has a "Destination" of C:\xxx and even though no files are copied as part of the component InstallShield still creates the folder.
Related
I have made a setup project using Visual Studio Installer. Now in this setup project I just want to have a custom dialog box which have one textbox and one button(BrowseButton), when I click this button a popup for selecting a folder in the target machine may appear.
In other words I want The "Browse For Folder button" or ""browser button" so that I may select any folder in the target machine. Once I select a folder the path should now come in the textbox. Because in the end I would like to save this path in the registry of the target machine.
I have Orca and I did tried to make this custom dialog using it but I am unable to do it.
There is only one browse dialog in those setups, and that's for the main application folder, so there isn't a way to do this. A custom action won't help because they all run after the files are installed.
I don't know why and where you need to browse to, but in most case there is a simple default location (such as an application data folder or a shared folder) that works fine. This really helps during upgrades when the upgrade install may need to do something with that variable location, and any apps will always know where it is. It's easier for the user too.
i'm new to installshield and am learning how to use it on the fly, I have an installshiled 2011 project that upon a custom installation when i deselect a component from being installed, it is not installing the files, but the folder for those files is created empty, how can i prevent it from being created?!
Thanks in advance.
I solved this by going to Files and Folders under application data,
looks like some one checked the parent node under custom installation, when i checked only the child node it didn't create any unnecessary folders.
I'm using Visual Studio 2012 and TFS Express. I have the top level collection 192.168.100.100\Collection; under it I have a project for each program; under those I have the solution folders. So in the project folder FooBarBaz I have the solution OldName. (I'd rather not post screen shots of the folder tree, but I can rig up an ASCII art depiction if needed.)
I want to rename the folder OldName to NewName. I have already successfully renamed the solution itself and checked that in. I have also successfully changed my local mapping from ~/Projects/OldName to ~/Projects/NewName.
In MSVS Source Code Explorer, when I right-click on OldName the context menu options Rename and Move are both greyed out.
How do I rename the folder in TFS? I am the team's TFS admin so I can use the web-based settings and I can also use the TFS control panel on the host system.
Right click on the folder name in the left panel.
Also, you must have those folders mapped into your current workspace.
Pre-step assumption: Create local folder with solution and project under it and added solution to TFS. TFS now has a path in TFS pointing to a TFS folder that contains your added solution. This location is bound to the location on your local machine that is likely out of sync with the path structure represented in Source Control Explorer.
You want to rename the folder in TFS that holds your solution. When I right-click in Source Control Explorer, “Rename” is grayed out. It appears that TFS wants the TFS path to match your local path structure.
In order to rename the TFS folder I had to:
Check everything in
Remove binding to source control
Do a get latest - TFS assumes structure inherited binding - so whatever the folder is named and where it is in the TFS path structure, the get latest will create a local folder to hold the code.
Now, right click on the folder and do a rename in Source Control Explorer.
TFS and your local workspace are now in sync. If you now go and rename the TFS folder that contains your solution, the next time you open the solution, your local folder name will be automatically changed to match TFS.
Of course, don’t forget to go back later - after VS has released the lock, and delete your old/first/”no longer bound to TFS” version of the local solution folder.
I hope this helps someone else.
I have an InstallScript installer that utilizes dynamic file links for several components. These components contain configuration files that standard users should be able to edit. We recently discovered that when these files are installed on Windows Server 08, the permissions are set to full access for the Administrators group, but only read & execute access for the Users group. The typical install location is C:\programName.
I've tried creating new files manually as an admin (right click - new text file) in the C:\programName directory, and they are generated with identical permissions. I'm assuming that this is just the standard permission setup for new files.
Is there any way, within InstallShield, to set the permissions for dynamically linked files or the directory containing them?
I've looked for permission settings in
Organization -> Components
Application Data -> Files and Folders
but I haven't found anything. The documentation on dynamic file links makes no mention of permissions.
We are using InstallShield 2010.
Generally these permissions are a good thing; they're inherited from their parent folders. Non-administrator users (including the limited access admin before accepting a UAC prompt) should be unable to modify files under Program Files or C: so I would suggest addressing this concern in your application (for instance by using each user's Documents folder). Since you don't talk about why you need it, it's hard to say with certainty if this applies to your case.
If it turns out it does make sense to address this in the installation instead of the application, you can use the SetObjectPermissions API to set permissions programmatically.
In "Files and Folders" page right-click the file or folder, select Properties and click the Permissions button. In the "Permissions" dialog you can then right-click in the Name(s) list and use the New context menu option to add a new permission.
If the option is not available for a file, you can try setting it on the parent folder.
In MonoDevelop I can right click a file in a MonoTouch project and select "Remove" and it then gives me an option of removing the file from the project. However, if I right click a folder, the only option available is "Delete" which brings up a confirmation box saying that the entire folder will be deleted. How do I remove a folder from a MonoTouch project? Does this functionality exist somewhere or has it not been built yet?
I think the easiest way to do this is to handle all the files outside of monodevelop. Just move it to wherever you like and then delete the folder from inside monodevelop.