Posts 11 - 20 of 20
First | Prev. | 1 2 | Next | Last
|
|
Robert Mills
Posts: 17
Joined: 2018-07-30
|
Hi Andrei,
Sorry for the delay, but I finally had a chance to try out a new add-in project. Long story short, it does exhibit the same issue. I create a new C# ADX project targeting Outlook with a minimum version of 2010. Upon create and registration, it worked fine. After I added our EV code signing certificate it failed with the same error above.
Thanks,
Robert |
|
Posted 03 Jun, 2019 12:27:59
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18183
Joined: 2006-05-11
|
Hello Robert,
Does it work with a test certificate?
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 05 Jun, 2019 01:29:46
|
|
Top
|
|
Robert Mills
Posts: 17
Joined: 2018-07-30
|
Hi Andrei,
The test certificate generated from ADX signing options within Visual Studio worked. It only supports SHA-1.
I was able to find one of our other code signing certificates, which isn't an EV cert, that was able to load correctly. The certificate that is failing to load is an EV certificate. Both support SHA256, issued by the same CA (DigiCert).
It seems there is an issue with an EV Code Signing certificate. Do you all have such a certificate to verify with?
Thanks,
Robert |
|
Posted 05 Jun, 2019 08:47:08
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18183
Joined: 2006-05-11
|
Hello Robert,
Could you please confirm that the "Code Signing" purpose is enabled for the certificate that you use? Add the Certificates snap-in to the mmc.exe console and check this.
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 06 Jun, 2019 06:13:53
|
|
Top
|
|
Robert Mills
Posts: 17
Joined: 2018-07-30
|
Hi Andrei,
It is purposed for Code Signing. The same EV certificate works with running the Add-in when built from VS 2017, we've been using the same certificate for the past 9 months. Just once I build from VS 2019 it exhibits the error.
Thanks,
Robert |
|
Posted 06 Jun, 2019 07:16:03
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18183
Joined: 2006-05-11
|
Hello Robert,
Thank you.
The issue is: VS 2019 doesn't let you use SHA1 certificates. You can sign your add-in using {Add-in Express installation folder}\Bin\adxpatch.exe; to get help, start adxpatch.exe /?.
Sorry, it took so much time.
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 06 Jun, 2019 08:03:04
|
|
Top
|
|
Robert Mills
Posts: 17
Joined: 2018-07-30
|
Hi Andrei,
I'm not sure I entirely follow. The EV code signing cert is a SHA2 certificate. I've tried removing any attempts to sign with SHA1 which correctly doesn't sign the assembly with SHA1, but the manifest still fails to load.
Thanks,
Robert |
|
Posted 06 Jun, 2019 10:52:17
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18183
Joined: 2006-05-11
|
Hello Robert,
According to our guys, currently, there's no way to sign a manifest from the IDE using the EV Code Signing certificate:
- VS 2019 doesn't let you use an SHA1 certificate; only SHA2 is used
- the .NET classes that we use don't let us use an EV certificate correctly
- The tool that Microsoft provides for signing an XML with an EV certificate doesn't sign adxloader.dll.manifest correctly.
As a workaround, you can use VS2017 or adxpatch; see
{Add-in Express installation folder}\Bin\adxpatch.exe /?
As soon as we have a possibility to test EV certificates, we'll look for a solution. I'll send you a note once we have such a solution.
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 07 Jun, 2019 08:44:05
|
|
Top
|
|
Robert Mills
Posts: 17
Joined: 2018-07-30
|
Hi Andrei,
Thanks for the all details, I really appreciate it.
Thanks,
Robert |
|
Posted 10 Jun, 2019 11:38:03
|
|
Top
|
|
Andrei Smolin
Add-in Express team
Posts: 18183
Joined: 2006-05-11
|
You are welcome!
Regards from Belarus (GMT+3),
Andrei Smolin
Add-in Express Team Leader |
|
Posted 11 Jun, 2019 04:23:40
|
|
Top
|
|
Posts 11 - 20 of 20
First | Prev. | 1 2 | Next | Last
|