Closed jenastadt closed 1 year ago
I noticed something else
The installation path is "C:\Program Files (x86)\clawPDF" of the MSI package, but the application is recognized as 64-bit in the task manager?
There is something structurally wrong.
A 64-bit compiled application must install in the "C: \Program Files\" directory and a 32-bit compiled application must install in the "C: \Program Files (x86)\" directory.
The operating system also determines the environment in which the application runs. In our case, a 64-bit application would also have the 64-bit environment, i.e. no access to a 32-bit email client.
In this case, the program directory does not determine the environment in which the application is run, but the operating system.
A compiled 32-bit version of the "clawPDF" would also be required for users who use a 32-bit e-mail client and a compiled 64-bit version of the "clawPDF" for users who use a 64-bit e-mail client " be available.
I have the same issue here. My email client is the built-in Windows 10 Mail application. When I hit the Email button the application crashes silently. .. Any idea? I am available for diagnostics as well.
I have tried debugging the issue in Studio and the crash occurs in MAPISendMail. I am still digging.
Follow-up!! I think I have found the issue.
Members of the MapiFileDescriptor, MapiRecipDesc and MapiMessage classes (structures) are not in the same order as what MAPISendMail is expecting
https://docs.microsoft.com/fr-ca/windows/win32/api/mapi/ns-mapi-mapimessage
I reordered the members to match what Microsoft expects and BOOM it worked like a charm.
Not sure why the members are not in the same order as the documentation though. Has this ever worked? :-)
[MapiClient.cs.patch.txt]
(https://github.com/clawsoftware/clawPDF/files/4512170/MapiClient.cs.patch.txt)
I have attached a patch file of what I have changed in order to get this to work.
Follow-up!! I think I have found the issue.
Members of the MapiFileDescriptor, MapiRecipDesc and MapiMessage classes (structures) are not in the same order as what MAPISendMail is expecting
https://docs.microsoft.com/fr-ca/windows/win32/api/mapi/ns-mapi-mapimessage
I reordered the members to match what Microsoft expects and BOOM it worked like a charm.
Not sure why the members are not in the same order as the documentation though. Has this ever worked? :-)
[MapiClient.cs.patch.txt]
(https://github.com/clawsoftware/clawPDF/files/4512170/MapiClient.cs.patch.txt)
I have attached a patch file of what I have changed in order to get this to work.
Thank you @christianpare. Your patch works like a charm with Thunderbird 78.3.1 (32-Bit) on Windows 10 (64-Bit) [10.0.17763.1457]
I uploaded a compiled version of the fix here: https://github.com/christian1980nrw/clawPDF/blob/master/clawPDF.Mail.DLL E-Mail is working again after replacing the file. @hessandrew @clawsoftware Please accept my pull request and release a new Version. Please update your MSI to Ghostscript 9.55.0 too. I am already using the DLL´s without issue.
Fixed with version 0.8.5
OS: Windows 10 Enterprise LTSC 2019 (1809) E-Mail Client: Mozilla Thunderbird 68.5.0 (x86) de >>> (default e-mail client: yes)
Nothing happens when you press the Email button.
OS event viewer with two entries
The following can be read in the LOG-File "clawPDF.log"
Windows features .NET Framework 3.5 (include .NET 2.0 and 3.0) .NET Framework 4.7 Advanced Services are activated
I am available for further error analysis.
S. Lehnert Systems engineer