I'm planning a project using MS project. then I send the different tasks to my collaborators directly to their outlook as outlook tasks.
Now, I want to synchronize outlook with MS project i.e each time the collborator modify a task on his outlook (when he puts it as done/finished..), this infos will be directly updated in my MS project. How can I do that?
There was an addin for this WAY back in like 2002 produced by Microsoft for the Japanese market but it never really took off and I think it was killed in like 2005.
If you are using Project Online Im almost sure you can link tasks to Planner. That might do what you need.
Related
We just released our Office JS Add-In for Outlook. Our Add-In takes one or more emails and sends them to an external web service to upload as a case note attachment for our enterprise application. With the previous Visual Studio Tools for Office (VSTO) technology, we could invoke our Add-In with any number of emails selected so that many could be sent at one time. With the Office JS technology, if we select any more than 1 email, the Add-In button is not enabled and we can't invoke our Add-In. We have 12,000 customers using this tool using VSTO and they will report this as a bug for our Add-In given that the old technology works and the new technology does not. We would like this capability added for Office JS so our customers can do what they did using VSTO.
This is not possible today. We track Outlook add-in feature request on our user-voice page.
It looks like the feature you want has been requested by others already. Please upvote the existing request https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/suggestions/11080962-allow-outlook-add-in-commands-to-be-used-on-select. Feature request on user-voice are considered when we go through our planning process.
I am currently working on an existing office 365 outlook add-in.
I'm not using visual studio but eclipse on a mac.
I simply need to do some debugging to check the response of an api call, so I added my debug code and deployed the add-in on the hosted server.
Then, from the Office Admin Center I re-upload the add-in making it available to all users.
The original problem was that the updated version of the add-in did not update straight away in outlook.
I left it for a day and today outlook was serving the updated add-in but then I had to add some more debugging code and once redeployed the new add-in version again was not served in outlook.
Thinking it was a caching issue I deleted all the browser cache (Local Storage, Session Storage, Cache Storage).
Unfortunately since then the Add-in is not loading at all returning an Add-in error:
Uncaught Function ContextActivationManager_getAppContextAsync call failed. ErrorCode is -2, exception: Failed origin check
from outlook-web-16.01.js
I tried to re-deploy it updating the version in the manifest but still no success.
I cannot really afford to waste another day to wait for the new version to kick-in so I was wondering if there is a faster way? Am I doing something wrong in deploying the add-in? Is there a reason why uploading a new version of the add-in it doesn't get served straight away in outlook?
RESOLVED. Apparently there is nothing wrong with the add-in deployment. I have spoken directly to the outlook support team and they said that if you are using the outlook web app the plugin takes time to become available because it goes through a release process.
So either use the desktop version of outlook or wait at least half hour before the plugin finally becomes available.
The error I mentioned earlier looks like it is not related to the add-in deployment.
which project use to create event receiver for sharepoint 2007 list - sequential workflow or state workflow? i'm using VS 2010
Neither.
Workflows are events which are run via the SharePoint Timer service and can be executed by any server in the farm.
An event receiver is essentially an event handler that will be executed either synchronously or asynchronously (depending on which event you're implementing) on the same server which handled the request that triggered the event receiver.
Visual Studio 2010 does not have much OOTB support for SharePoint 2007. You might consider installing the WSP Builder extensions (note that the proper download is not the recommended download - you'll need the 2010 BETA 1.4). They give new project types which include event receivers. Note though that there are some quirks with those project types but overall they are very helpful to getting the project set up correctly.
Be sure to read the documentation regarding the folder/file layout of your projects. If done correctly, you can use WSPBuilder to generate your WSPs for you.
A quick search revealed this blog post which might help get you started with regard to project structure. I'm sure there are many, many more references available. Happy coding!
Can someone give me a quick explanation of when I would use Visual Studio 2008 Outlook 2007 Ad-In project type? and how would that compare to developing a bunch of outlook macros directly in outlook?
Basically, I want to have some sort of application read email (with attachments) from a pop3 email box, do some filtering/editing/validation of the subject/sender/content and then if certain conditions are met, save the attachments to a local file, and then add an entry into an SQL server database table (i.e. date/sender/subject/message).
Seems there are at least 10 different ways to do this....so between an outlook macro and a VS Office Project, how do I pick?
I am not clear, if I create this solution as a Visual Studio outlook add-in, where does it run? Is it loaded into outlook, does it run as a separate process and communicates back and forth with outlook? if outlook is not running, does it start it?
An Outlook Add-on is a compiled component that uses the Outlook API to perform the tasks you need. A macro/VB script is an interpreted script that actually uses the same API. The add-on approach is better if you want to deploy your functionality.
When you work on an Outlook add-on in Visual Studio, you'll be creating a .NET component, which integrates into the Outlook application, which is written in C++ so uses COM. You'll have to be careful about managed/unmanaged types and releasing objects you retrieve from Outlook.
I have recently completed just such a tool, but I chose to use Add-in Express (http://www.add-in-express.com/). These guys provide a layer of abstraction over the [challenging] Outlook API and also provide some excellent support if you're stuck.
In my case, with Add-in Express, I "run" by setting Outlook as the application command to run, in the Project properties. Add-in Express sorts out the installation of the add-on within Outlook. So when I press "Run", Outlook starts and my add-in is displayed, which may be debugged in the normal fashion. I'm not sure how VSTO (Visual Studio Tools for Office) works in this respect - or at least, I can't remember.
This is an example of an outlook add-in..
Personally, I don't see macros distributable.
I want to create a custom Addon/plugin for Outlook 2003, to support integrated functionality with a task management system.
I am unable to find many good development resources for the same.
Can someone please explain Outlook 2003 architecure and development of a plugin.
Good links/resources are also welcome.
Here is a tutorial on outlook architecture getting started building Outlook 2003 plugins from MSDN:
http://msdn.microsoft.com/en-us/library/aa289167.aspx
There is also a huge list of resources here: http://www.microeye.com/resources/res_tech_vsnet.htm
Good luck!
What you want can be done.
The bottom line is that you need to use Visual Studio 2005 or Visual Studio 2008 plus Visual Studio Tools for Office (VSTO) plus Outlook 2003 (of course) to build an "Adddin" for Outlook.
Addins are quite complicated to write mostly because Outlook has eccentricities that are not well documented. For example, a method Outlook.MailItem.GetHashCode() is not always the same even for the same object despite what you might expect from something as seemingly absolute as a 'HashCode' for an object. Knowing that and many other quirks of the VSTO+Outlook API are for what the professionals get paid. There are MANY quirks. If you are learning then you will need to start with the resources Gdeglin has provided.
Also look at the MSDN VSTO forum:
http://social.msdn.microsoft.com/Forums/en-US/vsto/threads <- very active!
And Outlook code: http://www.outlookcode.com/
Also here is a Google search on MSDN for various VSTO 'tips'.