Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Getting the right files for a build

Posted on 2002-04-01
10
Medium Priority
?
159 Views
Last Modified: 2010-05-02
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
Comment
Question by:rwomalley
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
10 Comments
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 6911401
I believe PDW pulls the DLL from:

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

And not the System folder.

Anthony
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 6911408
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
 
LVL 3

Expert Comment

by:Gunsen
ID: 6918614
I believe you have to make a deploy script for each OS
0
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!

 

Author Comment

by:rwomalley
ID: 6918697
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
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 6918730
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
 
LVL 75

Accepted Solution

by:
Anthony Perkins earned 400 total points
ID: 6918735
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
 

Author Comment

by:rwomalley
ID: 6925136
can i edit the pdm file directly to point to where i want to take the dlls?
0
 
LVL 75

Expert Comment

by:Anthony Perkins
ID: 6925374
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
 

Author Comment

by:rwomalley
ID: 6925385
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
 

Author Comment

by:rwomalley
ID: 6925388
Thanks alot!
Bob O'M>
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The debugging module of the VB 6 IDE can be accessed by way of the Debug menu item. That menu item can normally be found in the IDE's main menu line as shown in this picture.   There is also a companion Debug Toolbar that looks like the followin…
This article describes some techniques which will make your VBA or Visual Basic Classic code easier to understand and maintain, whether by you, your replacement, or another Experts-Exchange expert.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…
Suggested Courses

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question