|
-
Aug 1st, 2003, 01:48 PM
#1
Thread Starter
Fanatic Member
deployment wizard ?
What should I do when the "Missing Dependency information." window pops up?
He who never made a mistake never made a discovery?
-
Aug 1st, 2003, 02:00 PM
#2
Hyperactive Member
Well...like it says, if you want to mark the file as permanently missing the information, go ahead; otherwise, just click "Next"
-
Aug 1st, 2003, 02:05 PM
#3
Thread Starter
Fanatic Member
Ok, whats the significance of doing one or the other? Also, this question related as well, when I get to the Installation locations part some locations are marked $(WinSysPath) and some $(AppPath).
Also, again. I have some folders that need to be installed with my app, how to I get these to be added to the deployment.
What should these be?
Last edited by Navarone; Aug 1st, 2003 at 02:08 PM.
He who never made a mistake never made a discovery?
-
Aug 1st, 2003, 02:27 PM
#4
Hyperactive Member
Ok, whats the significance of doing one or the other?
I think (which doesn't necessarily mean this is right) that if you mark a file as permanently having no dependencies it will never ask you again for that file and will always make that presumption; whereas, if you don't mark it you'll get prompted every time, but if it is a component that you have developed and you make upgrades to that component and it later has dependencies (which the system fails to locate), you wouldn't know until you deployed the app. and discovered it was broken. -- I hope that's all clear as mud, and if I'm off, one of the more educated will enlighten both of us.
Also, this question related as well, when I get to the Installation locations part some locations are marked $(WinSysPath) and some $(AppPath).
Also, again. I have some folders that need to be installed with my app, how to I get these to be added to the deployment.
What should these be?
A file that goes into the $(WinSysPath) -- e.g. Windows/System32 -- is most often a .dll file that is referenced in your project that is not proprietary. Files that go into the $(AppPath) are files specific to the application (.ocx, .dll, etc.) and any proprietary references as well. Based upon what you are saying, and I would presume you mean that you want some files to be included with the install, they should go into the $(AppPath) -- when you add them in, and click "Next", it will most likely make that association for you though.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|