Delphi 7 has a main menu option for Component Install Component that guides you through the process of getting a component onto the Palette. Cs6 Master Collection Mac Keygen Only there. Unfortunately, that functionality was lost in the IDE’s transformation to the Borland Developer Studio. I won’t go into details but I was not happy to say the least when I learned of this change. Regardless, your choices of installing components hasn’t changed it’s just you’re no longer guided through the process.

I thought it might be useful to walk through a few scenarios using Delphi 2007. There are many ways to accomplish these tasks so don’t consider this your only option. Well, posting here did not seem to work again. Trying again.

Uninstalling previous version of the package. If you have a previous version of the package already installed, you should remove it using the following method. Open the 'Component/Install packages' menu item in Delphi/C++ Builder and remove Alpha packages there. Remove all AlphaControls files in the AlphaControls. I would say that the best way to install components is to use your. Link to some old tutorial. How to install a Delphi component package from the command.

Steve, Blog did not post the first time I tried, then I decided I would rather send you a direct email. Can’t seem to do that using 'Contact me' button.

I get the message I include at the end of this note. I would rather not send you here what I was going to send on the blog. Why the original response to your blog did not work on my first attempt to send the blog message, I do not know. Can you send me an email direct as I can not send one to you.

П™ x81 Thanks for your reply. Server Error in ‘/blog’ Application. A potentially dangerous Request.Form value was detected from the client (ctl08$comment='oday. As I’ve harped on for ages I’ve always thought Delphi’s component installation was greatly lacking. This isn’t as noticeable with small components but once you get into the medium sized components it becomes a messy, inconsistent mire of methods.

Part of our training process for new hires is just teaching them all the different ways you can install components. The problem is that since Borland didn’t set standards we now have to deal with – Full-blown stand-alone installers. These are great but rare, they offer full installation with IDE detection, package compilation, registration, updating search paths and creating uninstallers. The only downside is that they are harder to integrate into an automated 'mega install' for quickly building out dev machines, but I’ll gladly deal with that. Companies like RemObjects, DevExpress and Raize excel here.

Mecanica Vetorial Para Engenheiros Dinamica here. – Attempts at generic installers. The two I know of are from Mustang Software, used for the VirtualTreeView and SilverPoint’s MultiInstaller, which reads an INI and allows installing of multiple products. Both of these are actually very good options, except almost no one uses them and they aren’t frequently maintained.

I use MultiInstaller here at work to install 25+ component libraries, everything from Toolbar2000, DIRegEx, our own custom library, PBear’s HTML, Abbrevia, FastMM, AsyncFree, etc. A good option but no one really uses it. – Zip file + readme. Tedious and error prone since not everyone has the same instructions, often the readme isn’t updated to take into account the newest folder layout and assumptions about the developers knowledge are often made. I’ve had to explain even to seasoned developers how to do certain things because the readme skipped steps that I’m sure seemed 'obvious'.

– The 'Non-Installer Installer'. This is the worst form of component installer. It’s basically a folder structure that someone dropped inside an InnoSetup or NSIS install. It unpacks files and creates an uninstaller but does *nothing* else. No component registration, no detection of IDE, no library path update.

They are horrible because they imply that they are installing something, that something more than an unzip command has been executed. I always end up repackaging these installs as plain zips so as not to lead on other developers. These cause me the most headaches because I get devs saying, 'I installed component X but it’s still not working' I would love to see Borland provide a way for component vendors of all sizes from the one-offs to the full blown to create installers that can do all the needed housework like install, compile, register, update, etc.