ProgReg.ini

[TimGrun]

We are writing a lot of add-ins that are used in our EViews development. To ensure that all our users have access to our add-ins, we have a centralized ProgReg.ini file that gets copied to each individual EViews user.
We have things working, but we are guessing what each parameter in the ProgReg.ini file does. Is there documentation for ProgReg.ini file?

Thanks,
Tim Grunwald

[EViews Gareth]

There isn't documentation available for it.

I'd recommend using an EViews program to install all of the addins, rather than copying the progreg.ini file. You can use the ADDIN command to register all of the addins.

[TimGrun]

Thanks Gareth.

Are there ways of programming the deletion of an existing add-in, or setting the default add-in path?

Another problem, with the following command:
addin(proc="getfame", menu="Getfame",desc="Read from Fame database",docs="https://www.rsma.frb.gov/twiki/bin/view ... ns#GETFAME") \\mqlx1\mq-home/eviews/addins/GetFame/getfame.prg

The menu and desc options retain their mixed case, while the docs options does not. So the documentation for getfame goes to the wrong webpage. The path of the add-in, getfame, also appears to lose its mixed case, but somehow EViews is still able to find the add-in.

Thanks,
Tim

[EViews Gareth]

Windows file paths are case insensitive. Http paths are not. It didn't occur to us that people might host their add-in documentation. I'll see if we can go about fixing the case issue.

There is no way to delete an add-in or set the default path though programmatically.

[TimGrun]

Thanks Gareth,

We are using our internal twiki for all our other documentation, so it seemed like a good place for the add-in documentation too.
That's why we are "hosting" the add-in documentation. :D

I was afraid of the answer about deleting current add-ins and changing the default path. So what I do is delete the current progreg.ini file and stick the default add-in path as the first line, before executing the EViews program with all the addin commands.

Thanks,
Tim

[EViews Gareth]

Of course, you could delete the progreg.ini file as part of the EViews program :D