How to redistribute Outlook Object Model?

[papachina]

I'm sending email in my application via Outlook Object Model. What I did is
importing mso.dll from Office and call _MailItemPtr->Display() to bring up
the "New Message" dialog.

But there may be customers who do not have Outlook installed on their
computers, so I guess I have to ship Outlook Object Model with my
applicaiton, right? How can I obtain the license to redistribute from
Microsoft?

Also is there any way to determine whether the user has Outlook installed or
not? If it's already installed, then I can just use the existing mso.dll.

Thanks.

 

[Sue Mosher [MVP-Outlook]]

Wrong. Users will have to purchase and install Outlook, either standalone or as part of Office.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[papachina]

Maybe I didn't make myself clear. I'm a developer for a commercial product.
We are trying to add simple email sending function in our product. I
implemented a prototype via Outlook Object Model, which calls #import
"C:\Program Files\Common Files\Microsoft Shared\OFFICE11\mso.dll"

So my question is: What kind of license do I need in order to use this
mso.dll in our commercial product?
Thanks.


Wrong. Users will have to purchase and install Outlook, either standalone or
as part of Office.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

I understood perfectly. That component is not redistributable. It's part of Office. The license must be held by your customers. Customers who do not have Outlook will not be able to use your application, or at least not the part that integrates with Outlook.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[papachina]

I see. So I can implement this email functionality in my product, but my
customers need to have Outlook installed on their computer in order to use
this functionality.

Just to make sure, I DONOT need any approval from Microsoft to use this
mso.dll in my product, right? So I'm free to link this dll as 3rd party
library in my product?

Thanks.


I understood perfectly. That component is not redistributable. It's part of
Office. The license must be held by your customers. Customers who do not
have Outlook will not be able to use your application, or at least not the
part that integrates with Outlook.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

So I can implement this email functionality in my product, but my

customers need to have Outlook installed on their computer in order to use
this functionality.

Exactly.

Just to make sure, I DONOT need any approval from Microsoft to use this
mso.dll in my product, right?

Right.

So I'm free to link this dll as 3rd party library in my product?

You can use a reference to it, but you may not redistribute mso.dll. Micrsooft does provide redistributable PIAs for developers to include in ..NET applications, in case the client doesn't already have them installed, but they're useless without the base .dlls that are part of the Office/Outlook installation.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers