<vbg>
J André Labuschagné
<vbg>
J André Labuschagné
Okay I'm Back. With success.
First thanks for everyone's help. Abe your images helped & Jane I did read
your document. Thanks to all others who contributed. I read every thread.
A few thoughts after this experience.
1. Always purchase a 3 year certificate. You don't want to do this more
than 3 times a decade.
2. I did use a vista computer to receive the certificate. Know that I know
the process I think it is easier on Vista(I don't have an xp anyway).
Abe's images helped me retrieve the certificates.
3. Jane's pdf on setting up signtool & including it in Sb is mandatory
reading. However for vista you should have a pfx file you already exported.
So you can start the document at the point of setting up signtool.
4. When purchasing I do not remember giving them a key password. I believe
they used my original password. So I suggest you use something you would
use on a regular basis.
5. After compiling I still got error -01.
6. I had to go to the script editor. click on the code -sign application.
Point to the pfx file.
7. Try to do this when you don't have other things on your plate. The
problem there is no warning. All of a sudden you can't code sign. So
making note of your expiration is important.
Now I have just one question. In my original message, backing up the
certificate was mentioned. What do I backup just the pfx file.
I will be getting a new computer soon. Do I need to retrieve the
certificate in internet explorer to my new computer or just the pfx file.
Again thanks to everyone. I can now go back to programming.
--
Thanks
Gary Hoffman
http://www.hoffmancomputersystems.com
The PFX file can be backed up and copied from computer to computer.
And/or if you have spc and pvk files, copy them as a pair.
That's why I recommend getting them as a file, because once they're
collected they're independent of the computer you bought them on.
The new (development) build of SetupBuilder includes presets for
code-signing, so you won't have to do as much typing in the project
properties and compiler directives.
If code-signing suddenly fails and your certificate hasn't expired, it's
possible that the timestamp server you're using is down. Try switching to
the other one.
Jane
>Now I have just one question. In my original message, backing up the
>certificate was mentioned. What do I backup just the pfx file.
>
>I will be getting a new computer soon. Do I need to retrieve the
>certificate in internet explorer to my new computer or just the pfx file.
I put everything I needed for code signing in a folder called
CodeSign. I copy it to any backup drives and other computers.
SB7 uses the CodeSign folder and so works on any of my computers.
Steve
--
Neural Planner Software Ltd www.NPSL1.com
EasyNN-plus. Neural Networks plus. www.easynn.com
SwingNN. Forecast with Neural Networks. www.swingnn.com
JustNN. Just Neural Networks. www.justnn.com
Gary,
Glad you finally got it working. I sure didn't have a lot of fun getting it
to work either. I bought my 3 year certificate in Nov and I'm hoping things
will be easier in 2 1/2 years. In any case, next time I think we'll be able
to just export the file from IE like you just did and put it in the same
location where the old file is. The signtool will already be there for you.
So it shouldn't be so bad.
As for backups, I have a backup program that copies all my source code
folders to an external drive. I put a folder there with my certificate and
after Jane set me straight on the fact I need signtool I copied that there
too. So they both get backed up every night. If I can get my source code,
I can get what I need to sign files.
--
Regards,
Abe Jimenez
Clarion 7.1.7075 EE Windows 7 Pro 64 Bit
There are currently 1 users browsing this thread. (0 members and 1 guests)