Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As Pekka says this could turn into a big project .. your description is pretty general and as you know the devil is in the detail ! but there are a number of options ..</p> <ol> <li><p>you may be able to use <a href="http://msdn.microsoft.com/en-us/library/bb176546.aspx" rel="nofollow noreferrer">Folder.WebViewURL</a> Property of a folder that you have created in outlook and show your app via a web app (you can build that on any tech stack you like) ok drag and drop may become a little tricky to do.</p></li> <li><p>Outlook forms could also be used. A form can call out to your web service and display what you want. There is some info about form on SO but <a href="http://www.outlookcode.com/article.aspx?ID=35" rel="nofollow noreferrer">http://www.outlookcode.com/article.aspx?ID=35</a> is the best place.</p></li> <li><p>Subclassing .. you can then create your own tree under the outlook tree and display whatever you want in the right hand pane such as grids forms etc. these can interact with the normal outlook folders and you can do your drag and drop though you woudl have to create Outlook Items to display them in the inbox. There is a tutorial on the technique <a href="http://www.codeproject.com/KB/office/additional_panel_Outlook.aspx" rel="nofollow noreferrer">http://www.codeproject.com/KB/office/additional_panel_Outlook.aspx</a> though not doing exactly what you want but the technique is sound.</p></li> <li><p>Next up build your own MAPI Message Store Provider which is probally the hardest thing to do on the list.<a href="http://msdn.microsoft.com/en-us/library/cc842153.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/cc842153.aspx</a></p></li> </ol> <p>As I said your question is no functional spec and there are always many ways to skin the cat but 2 or 3 are probaly where you shoudl look at unless it simple enough just a display a web app.</p> <p>Marcus</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload