I'm developing a vsto outlook plugin and works perfectly when I run on debug mode. If I install it, it's always disabled automacally and I can't make it work.
Does anybody knows what's happening or could I do to figure out what's the problem?
We have encountered times when our Chem4Word add in has been hard disabled. This may have caused by pressing the stop button in visual studio during debugging! This makes word think the add in has crashed. In our case it was only apparent when trying to run it as an installed add in, running in visual studio IDE never showed an issue.
See here for instructions on how to clear any hard disabled add ins
https://learn.microsoft.com/en-us/visualstudio/vsto/how-to-re-enable-a-vsto-add-in-that-has-been-disabled?view=vs-2019
I think that this applies to all versions of office.
You can also look in the registry at
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Word\Resiliency\DisabledItems
Substitute your target application and version number as appropriate.
The key should not have any items if nothing in hard disabled.
Related
I'm trying to debug a DLL that I've written in VB.Net. When the external program starts, it loads the DLL and everything runs fine...but I cannot see the class variables in the Locals pane. They show up blank as shown below.
Also, some lines of code generate the error "There is no source code available for the current location", but I think I understand why. Whenever it tries to step into class members of any of the Microsoft DLLs, it would of course have no information for those. But any lines which deal only in code that I've written, it works fine.
This is a COM DLL AddIn for Microsoft Access 2007, but I'm assuming the issue is roughly the same regardless of the type of DLL. The Shared COM Addin Wizard was used to get started, and then customization proceeded from there with satisfactory results...except for the invisible variables in the Locals window.
I'm new to writing & debugging a DLL like this; until now I've only done EXE files. I've researched MSDN, Google, and Stack Overflow, and here are the details that are asked about on other threads...
Visual Studio 2008, .Net 3.0, and Access 2007
Project Properties > Debug > External Program points to MSAccess.exe.
Project configuration is set for Debug.
Optimizations = off.
Generate debug info = Full.
The PDB file is present in the \bin\ folder with the DLL.
Breakpoints are working.
Debug.Print messages are working.
I dug through the registry and found all references to the project, DLL, and its custom UserControl (required since the project creates a CustomTaskPane, and all path paths point to \bin\ folder.
What am I doing wrong?
What am I doing right?
What can I improve?
Ok, answering part of my own question. I think I fixed the error message "There is no source code available for the current location". In the project properties "Enable unmanaged code debugging" was enabled.
With that option disabled, I can now step through the code without error, even if it hits objects for which I have no code. The debugger is acting a little differently too, but I haven't yet pinned it down. I did read up on the differences between managed & unmanaged code, and debugging them in mixed combinations, but while I understand in principle, I don't yet understand in practice.
My local variables are still blank, though.
Alright, after working on this for days in between other projects, I have an answer...of sorts. I think the solution and/or projects had become corrupt. I'll pass along what I can in the hope it may help others.
Yesterday I had a marathon session of "click everything", in the project settings and Options > Debugging, but nothign helped. At some point I stopped fiddling with the debug settings and continued working on the code until I was tired and went home.
This morning with a fresh mind I tried again, and discovered the private class variables were now all visible. And I don't know why. Also, there was a new problem: the Just-In-Time debugger prompt kept popping up, even thought it wasn't enabled in the settings:
Also, the play/stop/step toolbar buttons would become disabled when they shouldn't be, yet the menu selections for the same items functioned normally.
I double-checked all settings again. I played with everything and could NOT get the local class variables to become invisible again, and could not get the JIT dialog to go away.
So I...
Made a copy of the solution folder.
Cleaned the solution.
Rebuilt the solution, including the Setup project.
Uninstalled the Setup project from Windows via Solution Explorer.
Cleaned the solution again.
Deleted the SUO file.
Deleted everything in \bin\ and \debug.
Rebuilt the solution, including the Setup project.
And still the problems persisted.
After the JIT prompt, I clicked Continue (F5), then closed MSAccess. Aafter execution stopped, some IDE panes (such as Explorer, Locals, etc) disappeared, and some flew around to random locations on the screen. It was then I decided something might be corrupt, and started making plans to uninstall/reinstall all of Visual Studio 2008 from scratch, and possibly even a new solution from scratch.
So before reinstalling, I tried creating a new solution from scratch, and found everything worked perfectly, even with all settings as they were from the original solution.
So in the original solution I...
Exported the settings from Tools > Import and Export Settings.
Reset all settings.
Imported the settings I just saved.
At the moment the import dialog closed, I received the error message: "An unexpected error has occurred".
When restarting the VS IDE, I received a dialog that said "Visual Studio is configuring the environment for first time use". That didn't sound good.
Tried importing the settings again, same error.
Rebooted, tried importing again, same error.
Closed the Solution file, tried importing the settings again without any solution open, and it worked....or seemed to.
Then opened the Solution...and same problems were back.
Exported the settings from the new Solution.
Imported those settings into the original solution...and it's fixed..?
There was no import error, and the project started working correctly..!!
The local class variables were visible, and the JIT prompt was gone..!!
So...I guess something was bunged up in the Solution, one of the Projects, the IDE settings, or...something. I hope this helps someone else.
I have come across this particular problem several times across several versions of the IAR embedded workbench (EW430 5.40.7 [EW 6.0], EW430 5.51.2 [EW 6.4], EW430 6.20.1 [EW 7.0]), but each time only after a long period of having no problems. The problem doesn't seem to have affected the other firmware developers in the office, so no help can be offered there. I'm currently on Windows 10, but the problems first occurred when I was on Windows 8.1 (same PC.)
The problem is that, for no obvious trigger, the IAR ide will start to hang until terminated (or it will just crash on one of the EW versions) on any attempt to change the active build configuration in MSP430 projects using the emulator.
From my testing, it appears to be directly related to something the IDE is doing with the emulator, as when the build configuration is changed, I can see the emulator menu in the menu bar disappear, then the hang happens. Under normal circumstances, the menu will disappear, but then reappear once the other debug configuration is completely loaded.
I have tried the default project "flashing the LED" to see if it was only my project - but if I select the msp430x4xx (C) - Debug, right click it and select "Set as Active" from the context menu, to make this the active project, the IDE also hung. I then reopened the EW IDE, and opened the LED flashing project again. The original 1xx asm project was the active project.
I then changed the settings of the 4xx (C) Debug project (without making it the active project) from the emulator to the simulator, and clicked OK. The program did NOT crash.
I then set the 4xx (C) Debug project as the active project and it did NOT crash. The simulator even runs without problems.
The version of the FET firmware didn't change from when the IDE worked correctly to when it didn't, and the FET is not even used at this point. It can be completely disconnected and the same results will occur.
I have tried the following, without success:
erasing the files in my project folder's settings subfolder
erasing the *.dep files in the project folder.
deleting the IarIdePm.ini file from AppData\Roaming\IAR Embedded Workbench
making sure none of the project files are read-only
reinstalling the program to the same location
removing and reinstalling the program to the same location.
What does solve the problem (until it reoccurs) is to reinstall the program, but to a different directory (for e.g., the default directory will be in program files (x86)\IAR Systems\Embedded Workbench x.x. Installing again into program files (x86)\IAR Systems\EWx (just so it is different) allowed that installation to work, but the old installation continued to fail.
Best advice so far (from our support person) has been to do the above, install to another directory and live with it, as it doesn't happen often.
Since it has happened to me on 3 occasions with 3 different versions of the program, I would like to know how to fix or prevent it! If anyone could offer anything to try (or even better, a straight solution :)) that would be greatly appreciated!
Cheers!
Since newer versions and updates on W10, it seems that old compatibilities are being removed from this OS. I have no direct solution for this problem since Microsoft does not promise support for old software and hardware. Even I tried to find a solution for that problem, and I found on the IAR website a list of IDE's and their compatible versions. (remember, old versions are not compatible)
( https://www.iar.com/knowledge/support/technical-notes/ide/windows-10-and-iar-embedded-workbench/ )
You will need to update your IDE and program version to a newer version if you plan to continue to use this IDE natively on Windows 10 or you may use Virtual machines with an old operational system (like Windows 7) to compile your program on old IDE.
P.S.1 I manually uninstalled KB4592449 recently updated and the program return to work natively. Probably it will continue working until this update (or other similar) being installed again on the computer, but probably there is any vulnerability that the computer will be exposed to, and in this case, I'm paying the price.
P.S.2 KB4580325 promotes the same behavior in IAR 5.11 on windows 10. Both KB's implement securities about the flash player - that I Don't use - then, I can securely uninstall it.
P.S.3 Since I updated my windows up to Windows 10 version 21H1 (compilation 19043.1165) AND I configured Windows defender to not be monitoring IAR IDE (IarIdePM.exe) disabling all protections available, everything works fine. But Remember: my program is original, not cracked or altered by anything, then I am secure to do what I did.
It is a 'natural' that software problem. Not found way of fixing it. The solution temporary is modify manually the file .eww for change of project active. The ultimate solution is to use another development environment.
I'm following the instructions here but it seems not to work. I'll contact the developer, but wonder if someone has been able to make it work somehow.
The installation process is completed, but Netbeans doesn't see the plug-in. I assume it is deployed incorrectly.
Not sure how it got fixed but suddenly upon starting the IDE an update for the plugin showed up and it started working afterwards.
This is kind of weird, and I only seem to be seeing this on Windows 7 (when I build the app in windows 8 this does not seem to be happening). I see this with C++Builder XE through XE3. I will compile an app (statically linking the packages and the rtl), and then run it from the debugger. If I then make a change to the code and try to recompile and run the app, the compile appears to go ok, but the app crashes when it tries to start. If I close C++Builder and reopen it, then force it to rebuild either by doing a rebuild all, or making a minor change it compiles and runs fine. This is the case every time. I have tried in the past to switch to dynamically linking the rtl and that "appeared" to make the problem go away but I am not sure if that is a solid assumption. Has anyone seen this behaviour, and does anyone know how to resolve it. It is getting tiresome to have to restart the IDE all the time.
Edit:
The crash happens before any of my code. Here is the call stack:
007d17b3; __delayLoadHelper2
007d7efa; __imageBase
007d308b; __wstartup
btw: there are no delay load dlls in this project.
According to the Embarcadero Forums, Try disabling "Incremental Linking".
I have a VB.NET ClickOnce application that I am trying to install on my computer. Previously, I was able to install and run these apps without issue. Now when I install the application, I can see the flash of a window opening, and then nothing. (There are also no processes left hanging or anything when viewed with the task manager.)
After some digging around I noticed that there are files in my Temporary Internet Files with names like "FusionBindError" and then my application name and different DLL names.
I have done everything I can find on the net to do, reinstall applications, reinstalled the .NET Framework, deleted my Local Settings folder and relogged in.
Does anyone out there have any other ideas for me to try?
I tried the Mage.exe suggestion, but it failed to help. Same with the other installation location suggestion. The application flashes at the bottom of the screen but does not open. I have tried using FUSLOGVW to check the bindings and nothing shows up in there. (Good or bad, there are no binding entries.)
Have you tried using mage.exe? This is a command-line tool that comes with .NET framework. Start up a VS command prompt, and try mage -cc. This will clear your applicaiton cache and will force a new click-once download. This is the first thing I do when my click-once applications fail and it works 99% of the time.
A couple of suggestions:
FusLogVW isn't working for you because you have to enable assembly binding failure logging inside the registry. This MSDN article describes how to do this.
Another thing that comes to mind is, perhaps the ClickOnce app install, or perhaps the whole ClickOnce store is corrupted. Try deleting the ClickOnce app store then reinstalling the application.
It's possible that new prerequisites were added that you don't have on hand. If the URL you are using points directly to "my.application" or whatever your equivalent is, prerequisites won't be processed.
So try pointing to the setup.exe that is created in the same directory as the .application file.
Other than that, it sounds like you're doing all the right stuff...
Also, it could be useful to run the fuslogvw utility on a machine where the application actually works. Or reflector.
And then see if indeed any of its dependencies being loaded surprise you.
Also, for these types of errors, be sure to check if disabling the antivirus resident protection helps. Sometimes it causes problems accessing assemblies' manifests and such.
I uninstalled my Kensington Mouse software, and that resolved my installation errors.
Who knew that mouse software that I never used could cause so much trouble??
Sometimes if your machine is working for days this problem will show up. Try to restart your machine. The same problem happened to me and it disappeared when I restarted my machine.