registering components

[wolfrose]

Is there a rule to registering components? What type of components need to be registered and which ones do not? I am writing a huge program that I plan on passing out to other people, but I need to know what components need to be registered in my setup program.

[Shawn N]

P&D Wizard will do all of that for you.

[wolfrose]

true, but it's so amateur looking. I am writing my own.

[Shawn N]

I'm almost positive that controls created from OCX files are created at loading.

If your program can't create these objects, because the files are not registered, your program will error out giving the user a message like "Unable to create Object."

Something else you might want to consider is that you might be trying to overwrite a newer version of the file with your own, so you'd have to check the version of the file before overwriting.

Maybe you could modify the P&D project to your liking.

[vbmom]

Even if you don't want to use P&D, run it anyway to see what it comes up with. It will tell you what ocx's, dll's etc need to be delivered or are expected. When you're working with Windows NT versions, you can often deliver com objects, but not always with 2000 or XP. You also need to consider if things like IE are required, and what is the minimum version.

You ask a huge question. Deployment is a swirling miasma, and no matter how hard you try to get it right, you still have to test it on each platform before you can say it works. And even then...

As for me, P&D is far more professional that anything I could ever write!

[Shawn N]

Remember me vbmom?