BeeJ
1/11/2012 12:06:00 AM
It happens that ralph formulated :
> On Fri, 06 Jan 2012 17:27:42 -0800, BeeJ <nospam@spamnot.com> wrote:
>
>> Jeff Johnson presented the following explanation :
>>> "BeeJ" <nospam@spamnot.com> wrote in message
>>> news:je62n9$63d$1@dont-email.me...
>>>
>>>> I have a command line EXE app, App.exe, that I want to have registered.
>>>
>>> No, you want to "associate files."
>>
>> No, neither. (DN?)
>>
>
> Well it certainly looks like a good imitation if you aren't. <g>
>
> Considering it is always best to ask permission before doing this, and
> you will need permission to perform the registration, why not simply
> create a .REG file then offer the user the opportunity to run it?
> (Lots of ways to mechanically set this up.)
>
> -ralph
From the registry requirement I though it was clear that I wanted the
App.EXE to be "registered" as if it had been installed by a "setup" or
installer.
This is NOT an ActiveX exe in that it does not "register" like an
ActiveX EXE registers.
It is an app with no GUI.
When started with a shell command with parameters, it goes off and does
what it is told silently.
anyway, if you read the other post you would see that I have added code
to my main app to install the needed regestry entries.
It all works but is there not some "system" method to do this like
regsvr32 does for other types?