We Keep Coding

How to add plugin for Excel Online?

I would like to use Excel functionality from a browser. I currently have an excel based Microsoft office application. It adds an icon to the ribbon and does C# based custom application logic to communicate to a database server.
Since it requires application releases for any changes in the schema I am curious if I can convert this into an web application and still benefit from Excel's built in functionality.
I am expecting this to be possible since Microsoft Excel Online is run inside a browser. My question is, is it possible to add plugin to such online excel document? If yes, any example would be much appreciated.

You absolutely can, and depending on approach you can do so with nothing more than a VSTO project template. This is little more than a ClickOnce application. This can launch a browser within a window to perform the logic.
You may use the Office Interop assemblies to decouple your application from Office apps, yet still communicate easily. Make sure you set Embed Interop Assemblies to true once added as a reference.
For those using Office in the browser, it seems as though Microsoft is shifting into CSOM/JSON/REST, meaning this solution is coded entirely differently than COM. This should help you get started:
https://msdn.microsoft.com/EN-US/library/office/dn268594.aspx.

c# new mail from outlook with attachment

This has been asked before in one way or another, but i need some clarity on an issue I am having.
essentially, my client wants his app (wpf, written in VS2010) to be able to create new messages in his outlook (not send them, but just popup with the new mail message with certain fields filled in - he will type up the rest of the body and then send)
So to date I have just been going the route of using the mailto:
System.Diagnostics.Process.Start(string.Concat(#"mailto:" , toAddress , "?subject=" , subject));
easy peasy.
Now he wants attachments to be included. Doing some reasearch I see that there once was an &Attach tag I could add, but it doesn't work for me. further research revealed that its been killed off since office 2007 (I have 2013 installed on my box, client has all different types) so I cant use this method.
Further reasearch suggests that i go the COM automation route. there are nice tuts online like this one on MSDN
seems simple enough but I get stuck at this point
Step1. Create a Console application and reference the Outlook Primary Interop Assembly (PIA). To reference the Outlook PIA, right-click the project file and click the "Add Reference..." button. In the Add Reference dialog, navigate to the .NET tab, find Microsoft.Office.Interop.Outlook 12.0.0.0 and click OK.
Now I have a bunch of different ones (v11 - v15)
I guess because of different versions of office I have had.
Now my question is
Which version should I pick
What happens when I publish (clickonce) and deploy to my client given that their machines all have different versions of office.
Will the highest version accommodate them all?
Can I pick one to suite them all
(note: It has to happen through outlook so i cant use the normal .net mail method - that would have been great if i could)
Thanks

My recommendation is not to use PIAs, use NetOffice instead, as it provides a very nice abstraction and will work with any Office version (https://netoffice.codeplex.com/). Will also work nice with Clickonce distribution.

Editing Microsoft Word Documents Programmatically

I want to know if this could be done.
I am building a data dictionary for our software system (school project), and I'm thinking of an automated way to do this. Basically I don't use much of Microsoft Word (2007), I only use it in documenting schools stuff, etc. I want to know if its possible to create/edit a Word document programmatically from a template.
The idea is, I will create a page on Word that contains an empty form that will be repeated on every page. For every data that I will input to my program, it will update the corresponding field in the form and skips to the next form.
The purpose of this, is to eliminate copy-paste methods (my habit) and to speed things up when doing the documentation.

Word automation, as suggested by others, will lead you to a world of hurt for two major reasons:
Office is not intended to be run unattended, so it can pop up message boxes at any time, and
It is (probably) not licensed to enable office functionality for computers which don't have it. If you generate a Word document on a web site using automation, you have to make sure that this functionality cannot be reached by computers which don't have office installed (unless they changed this rule in the last years).
I have used Aspose.Words, it costs a little, but it works well and is intended for this.

Not exactly sure what you really want, but creating word documents with c# shouldn't be any problem:
http://support.microsoft.com/kb/316384

If i find out your purpose correctly you need to visit this microsoft msdn link
Manipulating Word 2007 Files with OpenXML

Definitely possible. A fairly easy way of doing it using Office Automation. See this KB article for a basic sample: How to automate Microsoft Word to create a new document by using Visual C#
I think the main difference to that sample will be that you'll open your template and do SaveAs instead of creating a new document, but I can't remember exactly.
However, depending on your exact requirements, there might be better alternatives. For example, it's not recommended to do Office Automation on servers (including on webservers), so if that's needed you might want to look at something else.

You can use com interop of .net framework.
Understanding the Word Object Model from a .NET Developer's Perspective
Building COM Objects in C#

Using COM programming is not the best way as mentioned by erikkallen, I suggest using OPEN XML. It is really easy to use and your document generation operation will be very fast.
http://blog.goyello.com/2009/08/21/how-to-generate-open-xml-file-in-c-in-4-minutes/
http://msdn.microsoft.com/en-us/library/aa338205(v=office.12).aspx

Processing Microsoft Office Outlook 2003/2007 email messages

Summary
It's been while now that I receive emails on a specific work-related domain, and I'd like to build up a database based on the information that is provided within these emails messages.
These messages are work related items about some needs and requirements in the computer science industry in my corner of the world.
I would like to parse or analyze these emails in an automatic way so that I can get recurring information into a database and build a business intelligence-like database which would keep me informed about the most demanded field of specialization.
Technological environment
O/S: Microsoft Windows 7 Pro
Office: Microsoft Office 2007 Pro
Yes, I can use .NET 4.0! =)
(I'll be pleased to provide further information as needed.)
Questions
How to access either PST files or the Outlook personal data files through the COM Interop assembly?
What are the objects to use to instantiate each of the emails found in the Outlook PST file or other?
What is the best way to go to parse an email message?
Thanks for any of you who can share her/his grain of salt in order to help me achieve my objective. That is very meaningful to me.

If you plan to use the Outlook 2007 COM object Model I suggest you start with this article: How Do I ... in Outlook
Look specifically for "Folders and Stores", "Search an Filter", "Solution Storage".
Aside from this, the PST format is now documented here: PST File Format SDK
but this is an unmaged C++ API, hard to use in .NET. There was a .NET port project initiated here: http://pstsdknet.codeplex.com/documentation but it seems quite dead (or not yet born)... so it's a difficult road to head for.

Creating Outlook Email Draft via C# Application

I am in the estimating phase of a project, and one requirement is that my application will create draft emails (with attachments) in MS-Outlook, which the user can then review and send. The app is written in WPF.
The clients will have either Outlook 2003 or Outlook 2007. The files that need to be attached will already exist on the file system when the drafts are generated.
I have done some initial research, but would like to get some opinions from people who have first-hand experience.
Questions:
What tool would you use to
accomplish this?
Will there need to be separate code for Outlook 2003 vs. 2007?
In general, using whatever tools are recommended, is this a relatively straightforward problem to solve?
Thanks for any insight.

a c# wpf application should be able to do the job just fine, you just need to add the outlook libraries in your references and you can work with outlook directly from your WPF app.
I only write for 2003, but I do know that 2003 and 2007 use different libraries. There's probably a clever way check what version of outlook is being and use the methods from the correct library, but it will take some work to figure out.
It's relatively straight forward except for the security prompt you'll get if you send the email. But I suppose if they are going to have them review it first, you should be able to generate the email, open it in an outlook window for them to review, and have them click the send button.

Would you be able to use WebDAV and then simply create the message and drop it in the users' Drafts folder?
Basically, you'll end up using something like this product (or you can roll your own) to create and save the message. You might be able to find an open source solution.

I think there are a couple tools you could use here:
Visual Studio Tools for Office (VSTO)
total control over Outlook
version of Outlook may matter
Assuming you have Exchange, you could use WebDAV, Exchange's XML methodology
version of Outlook wouldn't matter here
Use the built in mailto: functionality
lots of results for using this to include attachments - Google Results
would work for email apps other than Outlook
this probably would be quickest solution, but the least control over the output

An Outlook Add-in is probably a good way to go for this application. The tool set you need is Visual Studio Tools for Office (VSTO). With the possible exception of the WPF requirement, this is pretty straightforward.
Be aware that the API's and the VSTO tools evolved between 2003 and 2007. You can potentially have a single code base but you will need to write for the least common denominator, 2003.
2003 and 2007 also have different Primary Interop Assemblies, the components that bridge the gap between your .NET code and the native code COM interfaces that Outlook has. This can be a challenge when it comes to building and installer for your add-in. If you want your add-in to install the PIA's, you need to detect the version of Office and install the appropriate version, or, more commonly, just build two different installers.
I've never tried to do WPF inside Outlook 2003. There may be some issues with it but I don't know.