When starting up outlook 2013, the harmon.ie plug in stays on the splash screen with Loading harmon.ie.
As a result the outlook.exe cpu raises but nothing happens.
Running outlook 2013 16-bit on a Windows 8.1 Enterprise 64 bit version.
It seems you are facing a .net issue. Would you please register the following registry key which instructs harmon.ie to use .net 4.x.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Mainsoft\Prefs\PreferredCLRVersion]
#="v4.0"
---- Jean
Related
The problem:
I have a feature for a Microsoft Outlook web add-in which works fine in Office 365 Outlook, but when I test the same feature on Outlook for Mac or Outlook for Windows, the same feature doesn't work. The web add-in still installs fine on Outlook for Mac, it's just that there is a discrepancy between the behavior I am seeing on Office 365 Outlook and Outlook for Mac (this is also true when testing on Outlook for Windows, which has the same behavior as the Mac version).
What I've tried (Mac): I've tried running defaults write NSGlobalDomain WebKitDeveloperExtras -bool true as suggested from this answer and defaults write com.microsoft.Outlook OfficeWebAddinDeveloperExtras -bool true as suggested here and have an option to View Source which opens the HTML source in what appears to be a TextEdit window, but I'm still unable to inspect element in order to see any errors.
What I've tried (Windows):
I've tried using the VSCode Debugger Extension for Office Add-Ins to try to attach the debugger to Outlook for Windows, but keep running into this 'Error processing attach' error.
Additional Notes:
On Mac, I'm running Microsoft Outlook for Mac version 16.43 on MacOS Catalina version 10.15.6 and on Windows I'm running Outlook on Windows 10 Pro version 1909 inside a VM.
My understanding is that while debugging web add-ins for Word, Excel, and PowerPoint are all pretty well supported, debugging add-ins for Outlook on Mac or Windows is somewhat limited at the moment. Has anyone had success in debugging Outlook web add-ins running on Outlook for Mac and/or Windows?
For Outlook for Mac, we think this is specific to the Mac App Store build of Office, which currently doesn't support those flags. To workaround this, you will need to get a non App Store build. You can get one by signing up for the developer program and getting a tenant: https://aka.ms/o365devprogram. (similar issue: https://github.com/OfficeDev/office-js/issues/506)
For Outlook for Windows, we suggest attaching a debugger. Instructions for how to attach a debugger can be found here. Note that there is a different debugger for add-ins that run in Edge and IE.
I have been facing the same issue as asked in this other post
Visual Studio 2015 Windows Phone Emulator not deploying
but the solution worked here is not working for me.
Windows 10 pro upgraded from home version
Visual Studio 2015
Apache Cordova "Sample" app.
In Emulator it is showing as "Starting
in the behind "Hyper-V" "Summary" it is visible but if double click the the Hyper-V "instance" it is not visible there but only in "Summary"
What am I missing here?
For the developer sake and investment, MS must make sure that the solutions are tested everywhere before releasing them.
This link will direct you to print screen of the error. https://prnt.sc/cykrgg
in the VS output we get the following last message.
My OS is 64 bit.
2>The build configuration was changed to x86 for x86-based emulator deployment.
could this be impact of 64 to 86 bit version difference or anything else?
I have Norton antivirus
I am getting
Hyper-v administrator pop up every time I try to run the app.
This case is resolved by Microsoft Support Team over a Ticket and Rohit, support engg from MS did really helped me a lot.
The reason why it was not coming up.....
My machine has a AdWareAntiVirus from Lavasoft by Name WebCompanion that was not allowing it work.
I removed it then it started working.
if any body have any problem with VS 2015 Emulator definitely focus on the Antivirus and include the Emulator XDE into exception list and also include in Firewall.
Thanks,
Ekambar
Has anyone used WTL on Windows 10 already? All applications that I create with WTL segfault on Windows 10. They work on Windows 8 and Windows 7.
I even tried the most basic Hello-World application in WTL on Windows 10 and it segfaults when I run it. There are no clear indications of what is wrong. The program just segfaults with generic Windows segfault error.
Looks like WTL isn't Windows 10 compatible yet? Has anyone had this problem yet.
Just asking here as others will probably have the same problem. I tried two different Windows 10 (pre-release beta, and official release). I'm using latest WTL version WTL 9.0.4140 Final (2014-05-30).
All of our commercial applications are WTL built in VS2008. They work fine on Windows 10. If you can get a dmp file you should be able to review the crash dmp in windbg and see what is causing the fault.
Windows 10 with Visual Studio 2015 Community compiles and runs WTL sample MemDlg, I used WTL91_5270_Beta
our commercial video application is WTL-based(vs2015 express).
work fine, but it act different to MFC-based applications.
when win10 menu popup, video frame-rate drop in MFC(26fps->10fps), WTL(26fps->5fps).
https://github.com/sailfish009/wtl (WTL Version 9.1 (build 5321 final) 2015-11-17)
Visual Studio 2013 for Desktop is displaying incorrectly. When I open the program, it displays correctly but upon moving my cursor over links or images inside of the interface, they either expand to fill the whole window or the line itself blurs.
I'm running Windows 8.1. I've run it in compatibility mode for XP, Vista, and 7. I've run as administrator. I've reinstalled and repaired. This error is easily reproducible and has occurred over the course of 3 days.
Any help would be appreciated.
Can only guess that your video card vendor happens to maintain a bad driver (or Windows Update pushed a bad version to your machine).
http://support.microsoft.com/kb/2894215
The workaround is to disable hardware graphics acceleration and test again.
We have an issue with an Outlook 2007 AddIn (created on a Windows 7 development machine with Visual Studio 2008/VSTO).
It installs with the MSI installer on these machines:
- the development machine
- a Windows XP machine
Install initially succeeded on a Vista machine, but after installing an updated version of the AddIn, it gets disabled when starting Outlook. We suspect it might be related to how Vista handles security.
Have anyone encountered issues specific to installing VSTO AddIn on a Vista machine?
(Please note that the AddIn in our case gets installed alright, but is 'just' disabled when starting Outlook.)
The add in might be throwing an exception.
An unhandled exception causes the add in to be disabled.
We hit this issue on some random machines and after much head scratching, it turned out that Office.Interop was not installed on the client. We had assumed it would be installed with Office 2007 - which it appears to be in many cases.