office-interop

I'm trying to make a program that would open new Outlook 2007 message. I've referenced from COM tab Microsoft Outlook 12.0 ObjectLibrary. These items showed up in references in VS: Microsoft.Office.Core Microsoft.Office.Inerop.Outlook Now I try to invoke following code: var _outlookInstance = new Microsoft.Office.Interop.Outlook.Application(); var _message = (OutlookApp.MailItem)_outlookInstance.CreateItem(OutlookApp.OlItemType.olMailItem); where OutlookApp==Microsoft.Office.Interop.Outlook namespace. While invoking second line of listing I keep getting this exception: (InvalidCastException)

I have this warning: Warning 3 Ambiguity between method 'Microsoft.Office.Interop.Word._Application.Quit(ref object, ref object, ref object)' and non-method 'Microsoft.Office.Interop.Word.ApplicationEvents4_Event.Quit'. Using method group. on my line wordApplication.Quit(); I have tried replacing it with: wordApplication.Quit(false); // don't save changes and wordApplication.Quit(false, null, null); // no save, no format but it keeps giving me this warning. It's not a huge problem because the code compiles perfectly and functions as expected, but I'd like to get rid of the warnings. What can I

At the moment we're using office interop to generate documents from templates in office 2003 (word, excel & powerpoint). This seems to be rather frowned upon (see office-interop-with-64bit-windows-in-asp-net ) and whilst it works fine I would be happier with a supported solution. What non hacky method is there to do this? Requirements are Office 2003 only. (No office xml / office 2007 compatability pack allowed) Must run server side from ASP.NET Must be able to create Word, Excel & Powerpoint documents from user supplied .dot, .xlt and .pot templates Must be able to further customise the

Is there any way to know whether a doc / ppt / xls file is password-protected even before opening the file? This might help.. http://social.msdn.microsoft.com/Forums/en-US/oxmlsdk/thread/34701a34-f1d4-4802-9ce4-133f15039c69 I have created an utility method that tries to detect if a given office document is protected by a password or not. Here are the list of advantages: supports Word, Excel and PowerPoint documents, both legacy (doc, xls, ppt) and new OpenXml version (docx, xlsx, pptx) does not depend on COM or any other library requires only System, System.IO and System.Text namespaces pretty

Edit Please see also How do I properly clean up Excel interop objects? . I recently came across this question, and it provided a lot of insight into the problem of how to properly dispose of COM objects. Definitely check beyond the first (marked) answer, because the other answers go beyond the simple "don't use two dots" and "use ReleaseComObject for every com object" advice. I revisited this question in the first place because I realized that, despite being very thorough about registering and disposing all my COM objects, my Excel instances still weren't being properly disposed. It turns out,