Deployment package creation question 2

[StormbringerX]

Hi all,

I have just begun the process of packaging my application and being a complete novice at this part of the game, I'm looking for advice.

Most of the process is fairly self-explanatory, however when I get to the Install Locations portion I see that most of my dll's and OCX's will be located in the \winnt\system32 directory. Some want to go into the \winnt directory, others are wanting to go into my application directory.

I assume that the Install Location the package defaults to is simply the directory that these files currently reside in on the development machine.

Can anyone tell me a rule of thumb concerning these Install Locations? Should I go with the default? Do you find it easier to install them in a separate directory all by themselves? Or maybe it's best to leave those that want to go into \winnt\system32 alone and move my other OCX's, etc into a separate directory?

Please, any guidance, help, hints, warnings, anything at all would be appreciated. I can find all kinds of tutorials about HOW to navigate through the wizard, but nothing that really helps concerning the pros and cons of doing things one way as opposed to another.

Thanks again
Dave

 

[LPlates]

Here's a general rule of thumb I use...

System Ocx's into system32 or system (VB Runtimes etc)

Your own custom Ocx's into your own directory (Unless you want to (Attempt to) hide your file(s) ie: contains top secret cryptic data on Binladen's whereabouts

 

[StormbringerX]

Appreciate the thoughts, LPlates. I had thought that question might bring a few more responses than it did... maybe it would have if I actually had info on BinLaden..

I agree with your line of thinking and will probably do just as you suggested.

Later...

 

[ThatRickGuy]

On a side note, I would strongly suggest using a more robust deployment tool. The VB pakage and deployment tool can lead to some annoying bugs and agrivation. I'm a big fan of the Inno pakage deployment system. Much more configurable and avoids a lot of the problems the VB deployer runs into.

-Rick

 

[StormbringerX]

Appreciate it Rick.

I just downloaded a copy of INNO and am looking at it now...