trial versions

Jeff,

>We offer a trial version of the program which is much smaller, but still two
>SIS files. I would assume these need be signed as well. The trial EXE is
>different as we don't want someone to be able to hack it to make a full
>version, ie; code for features of the full version is not present. Is this
>going to double the cost of getting certification?

If you are signing multiple versions then, yes, each is treated separately I'm
afraid. In this case, it sounds like you'd have MyTrialVersion.sis and
MyFullVersion.sis to sign (assuming they share the same data files, these data
packages only need to be signed once).

Regards,

Phil

OK, thanks for getting back quickly. We will probably just get the full
version signed and see how it goes. If we run into situations where the
trial needs to be signed, then we will do it at that time. The data files
will be different between the versions as the trial version has a reduced
amount of data. It is all the same data, just not as much for the trial.

"Phil Spencer" <[email protected]> wrote in message
news:[email protected]...
> Jeff,
>[color=green]
>>We offer a trial version of the program which is much smaller, but still
>>two
>>SIS files. I would assume these need be signed as well. The trial EXE is
>>different as we don't want someone to be able to hack it to make a full
>>version, ie; code for features of the full version is not present. Is
>>this
>>going to double the cost of getting certification?
>
> If you are signing multiple versions then, yes, each is treated separately
> I'm
> afraid. In this case, it sounds like you'd have MyTrialVersion.sis and
> MyFullVersion.sis to sign (assuming they share the same data files, these
> data
> packages only need to be signed once).
>
> Regards,
>
> Phil[/color]