Printable View
Hello everybody
I`m trying to use the MS Package & Deployment wizard for an application I`ve built. It cannot find dependency information for two dlls. The fact is that I have the dep files for these dll`s. Can I use these dep files to remedy the problem?
Moved.
Sorry hack
Must have been a bit hasty and I misplaced the post.
Yes you should be able to, place the .dep file in the same directory as the .dll and PDW should find it.
The dll`s are in System32 system directory. Is it safe to copy the dep files there?
It may be safe, but do you want to place files in that folder that really aren't system files?Quote:
Originally Posted by divined
Also, I don't know who your target audience is, but many of our clients have workstation OS setups which prevent any type of use of the System and System32 folders.
I trust Inno Setup and Inno Script to find the things that MS might have missed.
See the links at www.***********
After more careful consideration the files I need to copy are in the /Program Files/Common Files/ directory. So I only need copy them in that directory. The problem is that Crystal Reports is so modular that even ********** has a hard time.
You dont need to switch to another packager when its not necessary. The dependancy files that are missing are both Crystal Reports files?
yes. They are both Crystal Report files. Does that make a difference?
The fact is that I`ve integrated pretty much all of the files that BusinessObjects states are required. Nonetheless, the executable crashes on the distribution machine but works fine on the one where Crystal Reports 10 has been fully installed. I was hoping those dep files could help!!!
Either your missing something else related to your programs dependancies or something related to CR dependancies.
In the CR Runtime.hlp help file it will show you exactly which dlls, ocx, etc are required for each and every CR control, function, and method.
Eventually, I decided to use Crystal Reports 10 merge modules and Microsoft Visual Studio Installer 1.1. It worked flawlessly now! I don`t know if ********** can handle merge modules so that I could use that package which I`m more familiar with.