Develop Reference

How to read .ost file in asp.net C# console application

//Set NameSpcae for Outlook "Mapi" is by Default Name
NameSpace outlookNs = null;
DailyLog("Start Outlook Application Mapi", "");
outlookNs = app.GetNamespace("MAPI");
DailyLog("End Outlook Application Start Mapi", "");
DailyLog("Start Outlook Application Logon", "");
outlookNs.Logon(null, null, false, false);
DailyLog("End Outlook Application Logon", "");
Console.WriteLine("Set By Default Name MAPI");
//Add Pst File in OutLook
Console.WriteLine("Adding PST File From Path : " + pstFilePath);
DailyLog("Set PST File Path :- " + pstFilePath, "");
**outlookNs.AddStore(pstFilePath);**
DailyLog("Set PST File Path :- " + pstFilePath, "");
Console.WriteLine("SET PST File To Successfully.");
DailyLog("SET PST File To Successfully.","");
if (Convert.ToInt16(ConfigurationManager.AppSettings["isSendRecieved"]) == 1)
{
outlookNs.SendAndReceive(true);
}
i get this error message "The Outlook data file (.pst) failed to load for this session"
<add key="MailPort" value="25"/>
<add key="MailServer" value="smtp1.projectstoday.com"/>
also used the port and server
what should i add the port number and Mail server for Office365

Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution. Read more about that in the Considerations for server-side Automation of Office article.
If you deal with Exchange accounts you may consider using the EWS or Graph API (in case of Office365) instead, see Explore the EWS Managed API, EWS, and web services in Exchange for more information.

C# Outlook - Call Rejected By Callee

Trying to add an event to Outlook calendar through my event registration app using asp.net/C#. Getting call was rejected by callee error when trying to initialize (line 1). How do I overcome this issue?
Error:
"Retrieving the COM class factory for component with CLSID {0006F03A-0000-0000-C000-000000000046} failed due to the following error: 80010001 Call was rejected by callee. (Exception from HRESULT: 0x80010001 (RPC_E_CALL_REJECTED))."
Outlook.Application outlookapp = new Outlook.Application();
Outlook.AppointmentItem appt = outlookapp.CreateItem(Outlook.OlItemType.olAppointmentItem) as Outlook.AppointmentItem;
appt.Subject = er.Event.Name;
appt.MeetingStatus = Outlook.OlMeetingStatus.olMeeting;
appt.Location = er.Event.LocationName;
appt.Start = er.Event.StartTime;
appt.End = er.Event.EndTime;
appt.Recipients.ResolveAll();
appt.Display(false);
appt.Save();

Firstly, you cannot use Outlook from a service (such as IIS).
Secondly, even if your code worked, you'd end up creating an appointment and displaying (!) it locally on the server machine, where there isn't anybody to see it.
Create an iCal file and provide a link to the user - the ics file will be opened on the client machine using Outlook and the user will be able to save it.

Server-side Automation of Office is not supported
Developers can use Automation in Microsoft Office to build custom solutions that use the capabilities and the features that are built into the Office product. Although such programmatic development can be implemented on a client system with relative ease, a number of complications can occur if Automation takes place from server-side code such as Microsoft Active Server Pages (ASP), ASP.NET, DCOM, or a Windows NT service.
See : https://support.microsoft.com/en-ca/kb/257757

application to manage multiple outlook accounts

I have multiple outlook accounts, and all accounts are added to the outlook express.
I can list emails from inbox in asp.net application from one account only which is set as default.
I can list emails from another account by setting it as default data file..
here is my code :
public static Microsoft.Office.Interop.Outlook.Items GetHotMailInBoxItemsUsingLoggedInOutLookAccount(this string strMailStatus)
{
Microsoft.Office.Interop.Outlook.NameSpace _ns;
Microsoft.Office.Interop.Outlook.MAPIFolder inboxFolder = null;
Microsoft.Office.Interop.Outlook.Items _items = null;
Microsoft.Office.Interop.Outlook.Application _application = new Microsoft.Office.Interop.Outlook.Application();
_ns = _application.Session;
inboxFolder = _ns.GetDefaultFolder(Microsoft.Office.Interop.Outlook.OlDefaultFolders.olFolderInbox);
if (strMailStatus.Equals("1"))
{
_items = inboxFolder.Items;
}
else
{
_items = strMailStatus.Equals("2") ? inboxFolder.Items.Restrict("[Unread] = true") : inboxFolder.Items.Restrict("[Unread] = false");
}
_items.Sort("ReceivedTime", true);
return _items;
}
I want to switch "_application.Session" as i want.
ie: change the default data file from asp.net application..

Consider using EWS (Exchange Web Services) instead. See EWS Managed API, EWS, and web services in Exchange for more information.
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
Read more about that in the Considerations for server-side Automation of Office article.

How to open Outlook new mail window on server C#

I am using this link for open outlook new mail window.
How to open Outlook new mail window c#
But It is working fine On Local machine but when I deployed it on server it shows below error.
Retrieving the COM class factory for component with CLSID
{0006F03A-0000-0000-C000-000000000046} failed due to the following
error: 80040154 Class not registered (Exception from HRESULT:
0x80040154 (REGDB_E_CLASSNOTREG)).
Microoft office outlook is install on local machine not on server.It is required to install and configure outlook on server.
Plz help.
Thanks.

1. Using Outlook
To send an email using outlook, we need to add a reference to the dynamic link library for Outlook which is called Microsoft.Office.Interop.Outlook.dll
For the same follow the below steps:
Go to your solution explorer
Click on add a reference
Click on .Net Tab
Go through the DLL and select Microsoft.Office.Interop.Outlook.dll
correctly.
when you have selected the correct reference you select the “OK” button and this reference will be added to your project under references.
using Outlook = Microsoft.Office.Interop.Outlook;
//method to send email to outlook
public void sendEMailThroughOUTLOOK()
{
try
{
// Create the Outlook application.
Outlook.Application oApp = new Outlook.Application();
// Create a new mail item.
Outlook.MailItem oMsg = (Outlook.MailItem)oApp.CreateItem(Outlook.OlItemType.olMailItem);
// Set HTMLBody.
//add the body of the email
oMsg.HTMLBody = "Hello, Jawed your message body will go here!!";
//Add an attachment.
String sDisplayName = "MyAttachment";
int iPosition = (int)oMsg.Body.Length + 1;
int iAttachType = (int)Outlook.OlAttachmentType.olByValue;
//now attached the file
Outlook.Attachment oAttach = oMsg.Attachments.Add(#"C:\\fileName.jpg", iAttachType, iPosition, sDisplayName);
//Subject line
oMsg.Subject = "Your Subject will go here.";
// Add a recipient.
Outlook.Recipients oRecips = (Outlook.Recipients)oMsg.Recipients;
// Change the recipient in the next line if necessary.
Outlook.Recipient oRecip = (Outlook.Recipient)oRecips.Add("jawed.ace#gmail.com");
oRecip.Resolve();
// Send.
oMsg.Send();
// Clean up.
oRecip = null;
oRecips = null;
oMsg = null;
oApp = null;
}//end of try block
catch (Exception ex)
{
}//end of catch
}//end of Email Method
For more information Open outlook

Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
Read more about that in the Considerations for server-side Automation of Office article.
Consider using standard .Net classes or any other components designed for the server-side execution. In case of Exchange Server account you can use EWS (Exchange Web Services), see EWS Managed API, EWS, and web services in Exchange .

If you run that code on the server, who will see the newly created message? Even if there is a user logged in locally to the server, IIS runs without a desktop session.
If you want the message to be displayed on the client, that is where your code needs to run. Why not use a mailto url? It will work in any browser and the default email client will be opened. If you need something more sophisticated than that, you need to write your code in JavaScript and create an instance of the Outlook.Application object using new ActiveXObject(). You can only do that in IE and your site must be trusted to do that.

Is it possible to access redemption method of outlook add in using windows services

I have created outlook addin in C# to storing mail subjects in SQLite database using redemption(background). Can we access redemption method/Class of outlook add in into the windows service.
Outlook Object Model cannot be used from a service.

Do not use Outlook Object Model in a service. Secondly, you are assuming that you only have ContactItem objects in the folder, your code will break if there is a distribution list there.
The RDO family of Redemption objects can be used in a service

You are right, you shouldn't use the Outlook object model from a windows service. The Considerations for server-side Automation of Office article states the following:
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
Redemption is a wrapper around a low-level API (Extended MAPI). But add-ins is a feature of Office applications. Extended MAPI doesn't know wnything about them. So, any wrappers (Redemption in your case) around Extended MAPI don't provide access to add-ins.
Consider using any other communication methods with your add-in, for example - .NET Remoting (WCF). You may consider your managed add-in as a regular .Net application.

using Microsoft.Office.Interop.Outlook;
using OutLook = Microsoft.Office.Interop.Outlook;
and the code will be
object missing = System.Reflection.Missing.Value;
try
{
OutLook.MAPIFolder fldContacts = null;;
OutLook._Application outlookObj = new OutLook.Application();
string folderName = "Default";
fldContacts = (OutLook.MAPIFolder)outlookObj.Session.GetDefaultFolder(OutLook.OlDefaultFolders.olFolderContacts);
//LOOPIN G THROUGH CONTACTS IN THAT FOLDER.
foreach (Microsoft.Office.Interop.Outlook._ContactItem contactItem in fldContacts.Items)
{
StringBuilder strb = new StringBuilder();
strb.AppendLine((contactItem.FirstName == null) ? string.Empty : contactItem.FirstName);
strb.AppendLine((contactItem.LastName == null) ? string.Empty : contactItem.LastName);
strb.AppendLine(contactItem.Email1Address);
strb.AppendLine(contactItem.Business2TelephoneNumber);
strb.AppendLine(contactItem.BusinessAddress);
//write to text file
StreamWriter sw = null;
sw = new StreamWriter(AppDomain.CurrentDomain.BaseDirectory + "\\LogFile.txt", true);
sw.WriteLine(DateTime.Now.ToString() + ": " + strb.ToString());
sw.Flush();
sw.Close();
}
}
catch (System.Exception ex)
{
throw new ApplicationException(ex.Message);
}