Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 164
  • Last Modified:

Getting the right files for a build

I have an application developed on a Win95 machine and deployed to a variety of Win95, Win98 and NT machines. Our group is moving to an XP OS and moved my code to the XP machine. Now when I do a build, the PDW takes files from Windows/System for Oleaut32, olepro32 and others but these files are not backward compatible to the older OS we are deployed to.
A couple of questions:
1.) How can I change my build (using PDW) to take the correct dlls. I know I can store them in a separate directory but I can't point to that directory using PDW. Is there a file I can modify (obviously this information is stored somewhere) to point to the 'build' directory for PDW?

2.)  Back in the days of VB3 we used to install all of the dlls into a directory that we controlled, a subdirectory  under the application. We would not install the dll's into the system directory. Is this a possibility to help avoid problems with versions etc?

Thanks,
Bob O'M>
0
rwomalley
Asked:
rwomalley
  • 5
  • 4
1 Solution
 
Anthony PerkinsCommented:
I believe PDW pulls the DLL from:

\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist

And not the System folder.

Anthony
0
 
Anthony PerkinsCommented:
Actually that should have read:
PDW will use components in the folder:

\Microsoft Visual Studio\VB98\Wizards\PDWizard\Redist

BEFORE the ones in the System or System32 folders.

Anthony
0
 
GunsenCommented:
I believe you have to make a deploy script for each OS
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
rwomalleyAuthor Commented:
But isnt there a file in the vb source directory that PDW reads from to know where to get the dlls? And if so, can it be modified?
0
 
Anthony PerkinsCommented:
Components will be pulled from the Redist before the System or System32 folder, however you should be able to modify options in the .PDM files.

Anthony
0
 
Anthony PerkinsCommented:
Here is something from MSDN that may help:

<quote>
Since a project can be distributed several different ways, several deployment packages can be created for a project, and all of the package/deployment scripts are stored in the same .pdm file. New scripts are added to the beginning of the projects .pdm file.
</quote>

Anthony
0
 
rwomalleyAuthor Commented:
can i edit the pdm file directly to point to where i want to take the dlls?
0
 
Anthony PerkinsCommented:
I have never had the need to do it, however take a look at the following from MSDN:

<quote>
You can manually modify the script (.pdm) file in a text editor, such as NotePad. The .pdm file contains all the scripts for a single project, and it is a recording of all the options you selected when packaging or deploying an application using the PDW.

To modify the path to a folder in a script, open the project's .pdm file in a text editor, and modify the path in all references to the file. After saving the changes to the file, rerun the PDW.

NOTE:

This method does not work for updating the path to the project's .exe file. The PDW picks up the path from the Path32 setting of the .vbp file instead.


Make a backup copy of the .pdm file before modifying.

</quote>

Anthony
0
 
rwomalleyAuthor Commented:
Thanks, I think you have answered my question.
Bob O'M>
p.s. I wasn't able to award you the points. Did you enter your answer as a comment?
0
 
rwomalleyAuthor Commented:
Thanks alot!
Bob O'M>
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now