I have a VSTO Ms Outlook Addin which interacts with Contacts, Tasks, Meetings,Calender and Emails of Outlook and it works fine with Office 2007,2010,2013,2016.
Now, I would like to implement the same for "app for outlook".
How should I do that? Can anyone explain.
You can start by consulting this getting started.
As a former VSTO add-in dev, you have to rethink the way you design Office add-ins. A web add-in is no more than a web app using a library office.js to fill the bridge between your logic and the office host. Keep in mind that you still have the possibility to use web services to do things that are not available with office.js, see how here
I wrote a blog post explaining the differences from a technical and business perspective of these two generations of addins.
Related
I need your help on a generic question. I am using Visual Studio 2012 to develop my Windows Forms Application that is running only on my machine locally to support my work. I have Windows10 and Office2016 installed. My Application interacts with MS Access (via System.Data.OleDb) and Outlook+Excel via Office.InterOp. Fine.
Today I received the information that our Company is rolling out Office365 and I started researching how this could impact my development work. I am not a programmer (more business) but always try to teach myself. But in this case I have no clew what all that means. I read about registering my Application before I connect to Outlook, Outlook REST API and many other things.
So my questions are:
Will my Application work the same way after migrating to Office365 (InterOps) ?
Is there a good tutorial out there that helps me getting started?
I really appreciate any help and guidance on this. Have a great weekend. Thanks
First what is yoy current version of Office you use ? Then do you know if your compagnie will move to office pro plus ? (I suppose yes)
Even if you pass to Office ProPlus the interop will still work, you should after starting to move you app using Graph API, but this API is to interact with the Office 365 data, not the Office App, it's in this case you register your app o the Azure Active Directory to have the right to use Office data
It is working on the web but not on the desktop. I have read all the available threads already but I am still not able to figure out the reason
Please guide, any help would be appreciated
My Manifest is compatible with outlook 2013 or later, what can be the reason?
Do you get any errors?
The Troubleshoot user errors with Office Add-ins page describes the information to help resolve common issues that your users or you encounter with an Office Add-in.
You can also use Fiddler to identify and debug issues with your add-ins.
I am trying to understand how to develop add-ins/macros in JS for Office, do I need VSTO for it or does it run from Office somewhere?
I did understood that Microsoft is making the first steps toward replacing VBa with JS and impemented an API to develop macros in Office.Js simmilar to the one Google has for it's Docs. But where can I find a development enviroment for Office.js?
The new web-based add-ins are basically a web application executed in the context of the Office application, either on the Desktop (by embedding a browser, IE11 at the moment) or in the browser (Office Online) where everything is web-based already.
The add-in can be hosted on any web resource you like. You just need to specify a source location URI.
Settings and metadata of the add-in are defined in a manifest file. The article Office Add-ins platform overview describes it very well.
Development can be done in any editor or IDE suitable for coding web apps. There is no Alt+F11 VBA IDE anymore, but you may try the Script Lab add-in, a Microsoft Garage project that allows you to try out some code directly in Office and share code snippets. It includes a great collection of sample code too.
The new WebApplications are hosted on a Webserver. You can develop Office Apps with Visual Studio.
Here is a good course for developing Office Apps including an overview of the Javascript Office API:
https://mva.microsoft.com/en-us/training-courses/introduction-to-office-365-development-8329
When I try to run Outlook via Interop using the profile name it opens a dialog for the password. This script is running from Windows Task Scheduler Task. Does it use the admin account when running these tasks? The profile been made and my email account is the only one loaded in here.
The Always prompt for login credentials is unchecked for the account listed in the profile.
This is a network computer in domain. Outlook 2010.
Profile Switch(link):
Process.Start("Outlook", "/profile profilename")
'logs in with a prompt for the password
How can I pass the password in code and avoid the dialog?
Alternatively, I have a macro that does what I need, but I have not been able to get it to run when the profile loads. This would solve the problem as well. Macros enabled is checked in the Trust Center.
Thanks
First, you need to run both application under the same security context to be able to automate one from another.
This app is being launched from Windows Task Scheduler
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.
As a workaround, you may consider usign a low-level API on which Outlook is based on - Extended MAPI. Or any third-party wrapper around that API such as Redemption.
Does a custom (i.e. one I've developed for SharePoint 2010) visual webpart have to operate within a sandbox solution in SharePoint office 365, or can it be a farm solution?
Thanks, Confused
Web parts have to be sandboxed for SharePoint 365. Visual web parts can't be sandboxed since the ascx control that comes with the web part is copied to the file system. if you need to create a visual web part in SharePoint 365 you can use the SharePoint Power Tools extension.
http://visualstudiogallery.msdn.microsoft.com/8e602a8c-6714-4549-9e95-f3700344b0d9
There you have the option to create a visual web part that can be deployed as a sandboxed solution.
Independent from the type of SP-I (SharePoint Item) you're creating, Office 365 only supports sandboxed solutions.
Microsoft is going to migrate Office 365 to SharePoint 2013 within the next weeks/months. When migration is done, you can also create Apps using the new SharePoint 2013 App model.
But for now, it's only possible to deploy Sandboxed solutions, because it's not allowed to do any changes to the filesystem or elements, that are available across the boundaries of your SiteCollection.
When it comes to WebPart development, you've to remember that it's not possible to impersonate using SPSecurity. (There are more limitations for Sandboxed Solutions, you should revisit the MSDN in order to get a common understanding of what you can do within the Sandbox)