Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Directories included in package
- Thread starter cheviac
- Start date
You can refer to the folder that the application is running from with:
App.Path
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'People who live in windowed environments shouldn't cast pointers.'
App.Path
________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first
'People who live in windowed environments shouldn't cast pointers.'
JohnYingling
Programmer
If you are using Package and Deployment, then I know of only one way; on the Included Files screen select all the files in the folder by Ctrl+A. Unfortunately, you will have to add the folder name for installation to each file on the Install Loaction screen later. When there, add the folder name to the end of the $(AppPath) in the Install Location of the first file e.g. $(AppPath)\NewFolder, then select the whole entry and press Ctrl+C. From the on, you can select the text in the Install Location for each file and press Ctrl+V to paste the new folder name.
Forms/Controls Resizing/Tabbing Control
Compare Code (Text)
Generate Sort Class in VB or VBScript
Forms/Controls Resizing/Tabbing Control
Compare Code (Text)
Generate Sort Class in VB or VBScript
JohnYingling
I was going to do this in the .LST file, would it be incorrect reasoning? The thing about the .LST file is you can play and replay, in the wizard you get one crack at it, and little chance to cut and paste when you re-compose a package and have to do it all again.
My thinking is I want to have my unique DLL in the $(AppPath) not the $(WinSysPath) that is imposed, just in case of version conflicts with my freeware DLL (more likely with users having several apps doing similar things)
I was going to do this in the .LST file, would it be incorrect reasoning? The thing about the .LST file is you can play and replay, in the wizard you get one crack at it, and little chance to cut and paste when you re-compose a package and have to do it all again.
My thinking is I want to have my unique DLL in the $(AppPath) not the $(WinSysPath) that is imposed, just in case of version conflicts with my freeware DLL (more likely with users having several apps doing similar things)
- Status
