Connect to Outlook via asp.net app?
It sounds like you really want to connect to Exchange. For exchanges before 2007, WebDAV is the way to go. For Exchange 2007, they have access to web services.
Independentsoft make a good (and cheap) .NET library for anyone who needs to exchange mailboxes (and calendar).
source to share
here is a link to open Outlook with a new mail using asp.net http://topictolearn.blogspot.com/2011/12/opening-outlook-with-new-e-mail-from.html
source to share
I'm going to do something like this, and I see no reason why it won't work: write an Outlook Addin that uses object deletion to communicate with any other services or tools you are working on. Since this is an ASP.NET application, you might want to use a web service instead of deleting objects.
Do you want an ASP.NET application to launch Outlook if it isn't already running? Can I use the same Outlook process for different users, or would you like to connect to custom Outlook processes? Do you want your ASP.NET application to act as the server that Outlook is trying to connect to, or vice versa?
If edge cases are tricky, you could try writing a Windows service to act as an intermediary or gateway between the two, for example. a service that runs on every Outlook computer and launches Outlook on demand.
source to share
jtacoma: Do you want an ASP.NET application to launch Outlook if it isn't already running?
Whatever is easier. If it doesn't matter that Outlook is down, we don't need to start it.
Can you use one Outlook process for many users, or would you like to connect to custom Outlook processes?
You need to connect to a custom Outlook process.
Do you want your ASP.NET application to act as the server that Outlook is trying to connect to, or vice versa?
And vice versa. I want ASP.NET to connect to Outlook.
See also: I am currently browsing another asp.net application and they are connecting to Outlook using a WebDAV request . I'm not sure if this is a good way to do it. Looks pretty messy to me.
source to share
Does your solution require Outlook to run on an ASP.NET server? If so, you can look into the implications of licensing. I don't think MS intends to automate Outlook this way. I also don't think it is possible to have multiple instances of Outlook, which could pose a major performance bottleneck issue. It will help if you can share more details - what actions are you trying to automate with Outlook? Is Exchange Server Enabled?
source to share
Outlook is really nice to look at through the COM API set ... however I'm curious if you need to connect to the Outlook client or connect directly to the Exchange server.
What is the actual task you are trying to do?
For example, once you import the outlook com DLL and create the interop library, it's pretty trivial to do most of the things:
outlook.Application outlookApp = new outlook.ApplicationClass();
outlook.NameSpace olNameSpace = outlookApp.GetNamespace("MAPI");
olNameSpace.Logon (Credentials);
outlook.ContactItem contact = (outlook.ContactItem)
outlookApp.CreateItem(OlItemType.olContactItem);
contact.FirstName = "Joe";
contact.LastName = "Smith";
contact.Save();
This snippet creates a new contact in Outlook.
source to share