After some digging around on the intrawebs and some trial and error I believe
I have found a resolution, however, I have yet to determine whether or not
this is a work around or a solution.

I disabled Microsoft VBA for Outlook AddIn Don't know why this works but it
does. Maybe something doesnt play well with VSTO and VBA on AddIns Who
knows? Again, if anyone has any information or can lend some clarifcation on
this it would be greatly appreciated.

"BigDubb" wrote:

We have attempted to create a new Outlook Addin for a Meeting request. For
the most part users are very happy with the new changes but we seem to have
hit an peculiarity when attempting to modify a request or dismiss a reminder.


Instance 1: When attempting to modify an existing appointment that a user
has accepted. When the originator of the request attempts a change an error
message pops up "Changes to the meeting cannot be saved. The meeting has been
updated by another person. Close and reopen the meeting, then make your
updates." I'm a little perplexed as to where this concurrency issue is
happening.

Instance 2: When attempting to send a cancellation notice, the user gets the
same prompt as previous instance.

Instance 3: When attempting to dismiss a reminder the user gets the same
prompt as in instance 1.

These problems don't occur when the add-in isn't installed. Which of course
leads me to believe it's the addin. However. I have some breaks in the code.
i.e. PropertyChanged or FormRegionShowing to see if any of the message data
might be changing.

Unless the form region is specifically opened, no code on the custom region
is ever hit, nor are any costom properties ever saved.

Does anyone have any ideas as to why this might be happening, and how I
might go about resolving this problem. Thanks.