Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why did microsoft’s API team recreate an Exception class in Microsoft.Office.Interop.Outlook that would conflict with the System Namespace’s Exception class?
Does it have to do with the unmanaged nature of interacting with the Office Suite? Why should it be used instead of System.Exception?
This is an automatically generated wrapper around the Outlook COM library’s
Exceptionclass, which represents an exception to a recurring appointment.The types in the Office PIAs are thin wrappers around the corresponding native COM libraries and do not follow standard .Net conventions; this is why Office automation is so annoying in C# < 4.0.
For example, collection classes are pluralized (eg,
Columnsinstead ofColumnCollection), many properties are parameterized (which are not supported by C# < 4), most method parameters areref objects, and many events share the same name as a method (eg,Document.Closein Word).The VSTO Power Tools make Office automation in C# much easier.