Am 25.03.2018 um 23:14 schrieb Matthias Seidel: > Am 25.03.2018 um 15:05 schrieb Matthias Seidel: >> One thing that comes to my mind: >> I am still on Windows 10 1703, because I had problems with 1709 (Fall >> Creators Update). >> Will try again... > OK, after hours of updating Windows 10 to from 1703 to 1709 I ran into > the same error like before when building AOO trunk: > > --- > error CS1548: Kryptografischer Fehler beim Signieren der Assembly > c:\Source\aoo\main\cli_ure\wntmsci12.pro\bin\cli_basetypes.dll -- > Zugriff verweigert . > dmake: Error code 1, while making > '../../wntmsci12.pro/bin/cli_basetypes.dll' > > 1 module(s): > cli_ure > need(s) to be rebuilt > ---
I have found the solution... We use a "strong name key" file (main/cli_ure/source/cliuno.snk). After deleting the file and doing "svn update" to restore it, I could do a complete build again! After nearly 30 years, Windows remains a mystery to me! ;-) Regards, Matthias > Maybe a developer has more insight why there is a "Cryptographic failure > while signing assembly" on 1709 but not on 1703: > > https://technet.microsoft.com/en-us/library/t21abc4c(v=vs.120).aspx > > Regards, Matthias >
smime.p7s
Description: S/MIME Cryptographic Signature
