Failed casting of a MAPI property brakes entire upload email procedure
See original GitHub issueI encountered a situation in which reading PR_ATTACHMENT_HIDDEN property returned empty string from GetMapiProperty()
. In this case operation of casting it to bool?
inside GetMapiPropertyBool()
caused an exception which caused entire procedure of uploading an email to fail.
I would propose to resign from hard casting and start using ‘as’ operator here. In case value cannot be cast we will get null which I guess is desired.
Issue Analytics
- State:
- Created 5 months ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Handling MAPI property errors
These methods report partial success by returning S_OK and placing error information in an SPropProblemArray structure. Unlike the property ...
Read more >C# Problems getting a specific named MAPI property from ...
UPDATE Try the following script in OutlookSpy on a machine where your code fails. When the IMessage window pops up, do you see...
Read more >How to resolve "MAPI Store Full" error in Aid4Mail
Instructions on how to resolve the "MAPI Call Failed. Error adding data to the MAPI store because it is full" error in Aid4Mail....
Read more >Read MAPI properties not exposed in Outlook's Object Model
How to read MAPI properties that are not exposed in the VBA Object model using the Property ... The full list of available...
Read more >Untitled
Choi yoo jung produce 101, After effects error needs 2 more frames playback, ... Create case from email sugarcrm distribution method primary team...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed with pull request from @CodeTraverser … I’ll also have to check issue #333 before making a new nuget package.
When making a pull request you first always fork the repro make changes there and make a pull request overthere for upstreams