I have developed an addin using Angular 5 version, I have built it and deployed on a Apache server with sercure http, I have tested this addin on Office Web App by logging in with Different users and I see that it works as I expected,
But the problem Now is I opened the Outlook Client with specific user configured with it, Addin Icon on the ribbon appears but when I click on it just shows the Empty section in Addin window at the right side.
The Icon and name of Add-In appears on the Ribbon, Even after I click the Add-In Button the Name of the Add-In appears as a header in Add-in window but rest is blank with no error message.
Note: The Outlook Client is on another machine mut on the same domain. On this machine I tried the Add-In from browser it works fine.
Office Outlook Client Version is "Microsoft Outlook 2016 MSO (16.0.4639.1000) 32bit
Exchange server Version is "Version 15.1(Build 1466.3)"
In Outlook Client I also want to know that how can I debug the Addin.
Where I can see the error logs if button dont appears in the Outlook Clients its all stucked in between.
I got the solution in this case, The actual problem is Document mode of Internet Explorer.
As we know that Web Add-in uses Internet Explore Frame to load. After when I debug it Using F12 Debugger. I came to know in the Emulation section the document mode was default selected to 7. And the Document Mode 7 doesnt have latest supported JavaScript suport(My Addin is built on Angular 5 version using Routes).
So in index.html of my Add-in Project I missed to mention the document mode in Header with meta tag, that which emulation version I want to run the script with.
I have added to head of index.html in my add-in
<meta http-equiv="X-UA-Compatible" content="IE=10" />
Now it works on my client and uses emulation Document Mode 10
You can debug your add-in in Outlook Desktop by attaching a debugger. You may not see the affordance like in Excel, but right clicking on the taskpane will show the same control to attach the debugger in the context menu.
Related
I have a Client Project relationship in my web-app. I want to allow my web-app users to be able to file emails right from within Outlook. So in my Outlook Web Add-In, I want to create the client project folders on the fly, if they do not exist already, and move the selected email item in the respective project folder.
My code works fine in Outlook Windows. In Outlook Web, it executes without any errors, but the folders are not displayed. If I reload the web page, the folders are there and the email is in the right folder.
I have talked to Microsoft support and they are saying that OWA is working fine.
Can anybody help me spot any issues with my code?
CreateFolderPath EWS operation is not allowed in my add-in. So that does not seem to be an option.
The manifest file is available at https://newdev.timesolv.com/Integrations/addin/SimpleVersion.xml
This is a bug. It has been submitted to Microsoft and they have acknowledged it.
Update: On January 27th, 2020, the issue was closed by OfficeDev. I confirmed and it was working fine.
We've created an Outlook add-in which integrates our custom CRM with Outlook. A command button is added to messages in read and compose mode. A function file is called on the button click.
The add-in manifest passes validation and installs properly on all machines. However on Outlook 2016 desktop (only) we are seeing an error on some machines. The exact error message says: “We’re sorry, we couldn’t access [NCS Outlook Add-in]. Make sure you have a network connection. If the problem continues, please try again later.” ([NCS Outlook Add-In] is the name of our add-in.)
Note that this message appears IMMEDIATELY after clicking the add-in command button. It does not first say “[NCS Outlook Add-in] is working on your request” like it add-ins do when an error has occurred.
We have tried Outlook logging and haven't found anything useful in the logs. We've checked settings and disabled other add-ins. We have also tested across machines with user accounts. The same user will have the error on one machine and not the other. In short, it seems that the error is machine specific and not profile related.
Version of Office 365 installed: 1705 (Build 8201.2209).
We experienced this exact behavior in Outlook 2016, the solution was to enable protected mode for the restricted and internet zones.
The easiest way to change this is in IE.
In Internet Explorer, click the Tools button, and then click Internet Options.
Click the Security tab, and then select the Restricted Sites Zone.
Select the Enable Protected Mode check box, and then click OK.
Restart Internet Explorer.
Here is a little more information:
https://support.microsoft.com/en-us/help/2761180/apps-for-office-don-t-start-if-you-disable-protected-mode-for-the-rest
Try this:
1) Close Outlook
2) Rename the folder C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook
to C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook.OLD
(Where %USERNAME% is current User Name.)
3) Start Outlook, Setup User Profile
4) Add/Test Add-In.
If that works, then something broken on old Outlook profile. But if same problem: Exit Outlook, delete the Outlook folder and rename Outlook.OLD back to Outlook.
I ran into this exact same problem after uninstalling Visual Studio 2015 on my development machine. (I had been using Visual Studio 2017 for Outlook add-in development.)
The problem went away as soon as I reinstalled Visual Studio 2017. The Outlook 2016 installation had nothing to do with the problem, I never changed Outlook or its profile at all.
This would indicate that the problem is somehow related to the SDK tooling on the machine...perhaps something to do with the .Net framework?
If I ran into this problem on a customer machine I would try reinstalling or repairing the .Net framework, or perhaps reinstalling Outlook (assuming it contains some add-in tooling that is broken.)
Just passing this on in case it helps anyone else.
I have built an add-in which works fine in Excel online, whereas it does not work in Excel 2016 for Windows.
I know that in Windows 10, we could use this tool to debug the add-in, however I am using Windows 7.
I just installed Visual Studio 2017, right clicking on the add-in shows a menu where Attach Debugger is. But clicking on Attach Debugger fires nothing.
Does anyone know how to debug in this case?
Two potential options:
You can use Volorn.js to remotely debug your add-in. You can use the Debug Office Add-ins on iPad and Mac article as a starting point. Although this article is targeting Mac and iPad, the concepts are the same for Windows.
You can also use Visual Studio by creating a new Excel Web Add-in. Simply replace the default manifest with your own. Note that you still need to retain the default web site, Visual Studio still this for some library references. It will use your manifest's URL for the source location however.
Office applications use Internet Explorer for the web browser, so all settings from IE should carry over. I have found that if you disable (uncheck) both the Disable script debugging (Internet Explorer) and Disable script debugging (Other) options, your debugger breakpoints will be hit (I tested this in Outlook 2016).
You will need add debugger; statements to the source code to add breakpoints. When these statements are hit, a dialog like this should appear:
Simply select 'Yes' and a new instance of visual studio should open, with the debugger attached to your script.
We are developing an Outlook Mail Addin for our product.
When i debug the solution in Visual Studio my Office365 Outlook account opens and i can see the plugin i developed in the list of outlook plugins and i can use it.
The problem is that even after stopping the solution in Visual Studio i can still use the plugin. And when i re-run the solution it displays the cached version of the addin not the current version that i have in visual studio.
Looks like the addin is cached somewhere. Can't seem to stop it.
How can i solve this problem?
The add-in doesn't get cached, it always loads from the source location set in your manifest. During testing, when you build the solution the app gets deployed to the Mailbox you specify. However, the app can only run while your local web server is running. The add-in's tab will continue to be displayed, but if your web server has stopped it will fail when it loads - it should never load a cached version. You'll have to manually uninstall the add-in from the add-in page if you don't want it to run while you're not debugging.
Your browser is caching the files used by your add-in. If you deploy an updated version your browser will rely on the old files it still got cached. Deleting your browser's cache should solve the problem.
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.