Sending email via .NET

  • Thread starter Thread starter msnews.microsoft.com
  • Start date Start date
M

msnews.microsoft.com

Hi,

I have a .net app that is sending email via outlook. I works fine. The
problem is that the client PC has Outlook 2000 SP3 installed and on my box I
have Outlook 2003 installed. I can not upgrade the client PC and cant
downgrade my PC. How can I get things to work?

G.
 
Can you be more specific about what isn't working? Do you mean it works on
outlook 2003 but not 2000?
 
I have on my PC (developers box) outlook 2003, and on the PC that the app
will run I have outlook 2000. When the app runs I get this error.
Error interno de la aplicación. - at
Outlook.ApplicationClass.CreateItem(OlItemType ItemType)
at wsMSCIndicadores.clsMail.SendEmail() in H:\Documents and
Settings\glake\My Documents\Visual Studio
Projects\wsMSCIndicadores\clsMail.vb:line 82

I am gessing that there is a differance between versions.
I can not install 2003 on that PC and I can not install 2000 on my PC, so,
what can I do? Can I get the dlls for 2000 and use them on my pc? or can I
copy the 2003 dlls to the 2000 box?

Thanks.


Diane Poremsky said:
Can you be more specific about what isn't working? Do you mean it works on
outlook 2003 but not 2000?

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Coauthor, OneNote 2003 for Windows (Visual QuickStart Guide)
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/






msnews.microsoft.com said:
Hi,

I have a .net app that is sending email via outlook. I works fine. The
problem is that the client PC has Outlook 2000 SP3 installed and on my
box I have Outlook 2003 installed. I can not upgrade the client PC and
cant downgrade my PC. How can I get things to work?

G.
Click to expand...
Click to expand...
 
You aren't supposed to copy them.

One solution is to develop versions of your code for specific versions of
Outlook. Use development machines that have those versions of Outlook
installed. And of course you have to ensure that each client has the correct
version of the Framework installed.

Another solution is to develop only on the oldest version of Outlook you
plan to support and use early binding only on those methods, properties and
events and late-bind to properties and methods that are from later versions
of Outlook if you use them at all.
 
.... and the correct version of the Office PIAs.

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

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


Ken Slovak - said:
You aren't supposed to copy them.

One solution is to develop versions of your code for specific versions of
Outlook. Use development machines that have those versions of Outlook
installed. And of course you have to ensure that each client has the correct
version of the Framework installed.

Another solution is to develop only on the oldest version of Outlook you
plan to support and use early binding only on those methods, properties and
events and late-bind to properties and methods that are from later versions
of Outlook if you use them at all.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


George Lake said:
I have on my PC (developers box) outlook 2003, and on the PC that the app
will run I have outlook 2000. When the app runs I get this error.
Error interno de la aplicación. - at
Outlook.ApplicationClass.CreateItem(OlItemType ItemType)
at wsMSCIndicadores.clsMail.SendEmail() in H:\Documents and
Settings\glake\My Documents\Visual Studio
Projects\wsMSCIndicadores\clsMail.vb:line 82

I am gessing that there is a differance between versions.
I can not install 2003 on that PC and I can not install 2000 on my PC, so,
what can I do? Can I get the dlls for 2000 and use them on my pc? or can I
copy the 2003 dlls to the 2000 box?

Thanks.
Click to expand...
Click to expand...
 
Yup. That too. Isn't .NET code fun? It was supposed to eliminate DLL Hell,
instead it introduced PIA and Framework Hell. A nice tradeoff.




.... and the correct version of the Office PIAs.

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

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Not to mention CAS Hell, the real burner.

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

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
All those poor people who have the addin running on the development machine
and can't get it running on the client :(

MS really ought to have a more compelling picture for deployment. Even VSTO
requires too much in the way of manual manipulation of the package.




Not to mention CAS Hell, the real burner.

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

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