When I press F12 in IE11 (v.11.1016.18362.0) to open developer tools first time it shows an exception with text
Check dependency list! Syncronous require cannot resolve module
'serviceHub'. This is the first mention of this module!) [3040]
iexplore.exe.
Sometimes if I need to debug JS, it shows that error window about 5-10 times and I close it one after one...
I tried:
Removed and install again IE11 in windows components
Replaced files in C:\Windows\System32\F12\
Installed all Windows updates
Disabled all extensions and helpers in IE settings.
What else can I try?
When I tried to debug it, I see an exception in with text
"There was no method handler registered for the
'getTranslatedLocation' method."
But I have no plugins in IE enabled anymore.
The solution was just to set checkboxes "Disable debugging (Internet Explorer)" and "Disable debugging (others)" in IE11 settings.
Related
Whenever i open atom IDE, chrome developer tools window loads in it. How can i start Atom normally for coding
Check the screenshot
I think you have set Atom as the current default URI handler, so seek in the settings for URI handlers
and select the third option, never become the default atom//:URI handler.
This will work and if not try reinstalling Atom.
I have a signed VSTO vb.net add-in that is loaded into Excel 2013. There are roughly 200 users, and 90% are having no issues. For the 10%, every time they boot Excel, the add-in is soft disabled.
I have stood next to them as they boot XL, go into COM Add-ins, check the add-in, and click ok. It loads (and works fine) without error. They then quit XL, boot XL again, and the add-in is again disabled. No "An add-in was causing issues dialog", no errors, just disabled -- if you click on the add-in name in COM Add-ins, there is no indication of any error in the Load Behavior (just "Load at Startup"). They re-enable and it works fine for that session.
The fact that it's a subset of people makes me believe it's a setting on their machine (perhaps in the Trust Center?) but I have yet to find a guilty setting. All users have the same version of Windows, and should be on the same update.
My Google searches have found lots of entries for add-ins that are misbehaving or where the Trust settings are very restrictive -- from what I can see, neither of those categories fit. I found one article that talked about the boot order with Analysis Toolpak, but none of the users assisted had Toolpak enabled.
Being that no error (either from the add-in or Excel) are displayed, I've been at a loss as to why it turns off (and why it's working perfectly on 90% of the machines).
I would appreciate thoughts on either what to look at in my code (even though there are no errors visible) or what settings to attempt.
For the 10%, every time they boot Excel, the add-in is soft disabled.
There can be a lot of reasons why your add-in is disabled automatically.
First of all, I'd suggest checking the list of prerequisites - whether they all were installed correctly (including the .net runtime)
Then I'd recommend enabling any logging mechanisms to look for any unexpected exceptions fired at startup.
There may be a conflict with other add-ins that are being loaded in the Office application. Disable all other Add-Ins except the one in question and retry.
The Antivirus on the system may be blocking the Add-In load. Run latest updates for the Antivirus and retry. If this doesn’t help, disable the Antivirus program completely and retry. Sometimes the Antivirus software also installs additional Office add-in, you may need to disable these additionally by running through the Antivirus control panel (Settings).
Visual Studio Tools for Office can write all errors that occur during startup to a log file or display each error in a message box. By default, these options are turned off for application-level projects. You can turn the options on by adding and setting environment variables. To display each error in a message box, set the VSTO_SUPPRESSDISPLAYALERTS variable to 0 (zero). You can suppress the messages by setting the variable to 1 (one). To write the errors to a log file, set the VSTO_LOGALERTS variable to 1 (one). Visual Studio Tools for Office creates the log file in the folder that contains the application manifest. The default name is .manifest.log. To stop logging errors, set the variable to 0 (zero).
Read more about possible pitfalls in the following articles:
Troubleshooting COM Add-In load failures
Troubleshooting Outlook Add-ins
I'm trying to debug a class library (PDM Add-in) using Explorer.exe for SOLIDWORKS PDM Professional. I'm on Windows 10. Explorer starts for a second and then something happens that shutdown the debugger.
This what I see in my debug tab.
onecoreuap\shell\windows.storage\sharedstoragesources\util.cpp(6571)\windows.storage.dll!76538288: (caller: 765382E5) ReturnHr(1) tid(c0c) 80004002 No such interface supported
pcshell\shell\appresolver\lib\pintostartcontextmenu.cpp(97)\appresolver.dll!7720C6F5: (caller: 7720DA4B) ReturnHr(1) tid(c0c) 8007007E The specified module could not be found.
onecoreuap\shell\windows.storage\sharedstoragesources\util.cpp(6571)\windows.storage.dll!76538288: (caller: 765382E5) ReturnHr(2) tid(c0c) 80004002 No such interface supported
CallContext:[\InvokeAssociatedProgram]
There is some sort of unhandled exception that gets thrown in Explorer by some stupid Microsoft extension. I think it's OneDrive. Since the debugger is attached to Explorer, it crashes because of this fatal error. The debugger doesn't catch the exception because the symbol file of the culprit code is not loaded. Actually, you can see something illuding to that in the output window In Visual Studio.
This didn't happen to me in Windows 7.
Solution 1
Use Notepad.exe to debug Solidworks PDM addins (This is already recommended by Solidworks API doc examples) but I don't really feel comfortable having to go To File > Open > Going to the vault (login) and setting the file filter to solidworks document types every time I start debugging. Moreover, Notepad OpenFileDialog dialog does not support multi-selection.
Solution 2
Use this console application I developed that invokes the OpenFileDialog dialog. The console app will:
Log you into the vault.
Uses the vault's path as the start up directory for the OpenFileDialog.
Sets the extension filter for SOLIDWORKS files
You can enable multiple-selection if you need it.
I am using Visual Studio Code for a javascript project. You can set breakpoints and step through and debug very easily the code that runs in nodejs. Is there any way to allow breakpoints and debugging for the client side, browser running code?
Debugging via console.log gets old real quick.
For debugging in Chrome there is the Visual Studio Code: Debugger for Chrome extension. You can find this extension in the marketplace, search for debugger as told in the debugging manual. Unfortunately there is (currently) no support for other browsers,
Debugging node.js works out of the box, see the debugging manual above or John Papa's blog post.
Debugging both client and server (as Phil commented) is not possible at least in my opinion since you need to have two different launch configurations, sorry.
You should use developer tools which all modern browses have (F12).
I prefer chrome because with workspaces and you can inline edit your code in browser.
By opening you project in chorme Browser and using chrome DevTools.
You can debug it whatever you want.
steps:
Open your project (with url).
Open DevTools (F12)
Choose the "Elements" and choose the Element
You can see "Event Listeners" on the right panel , Select what you needed
And then, You can right click the event you, Select "Show function defination"
Enjoy yourself !
If you means Debug Nodejs ,As I known there's A npm package named "debuger"?
Another technique is to use the Visual Studio Code: Debugger for Chrome extension. Save the contents of your launch.json config for node.js and delete it. Then create the Chrome launch.json. Combine the two and you can debug either the server or the client in Code (but not both at the same time).
To debug the client, the server must be running, so from a command prompt use the "node" command that starts the server. In Code launch the Chrome debugger and debug the client side.
I have Visual Studio Ultimate 2012 that is working fine except for one issue. Whenever I try to connect through the sign in Wizard to Team Foundation Server I get an error in a popup Titled: "Script Error" as if it can't render the result or something. here are more info on the subject
Line: 4
Char: 16405
Error: Object doesn't support this property or method
code: 0
URL: https://....../TFS/Loader.min.js
Any suggestions? (I tried re-installing but the same issue shows)
I had the same issue. I generally use Chrome, the version of MSIE installed was IE 8. When i updated to IE 11 the issue was resolved.
As I'm using Windows Server 2008, I couldn't find a way to reinstall IE (only to enable/disable it), so this solution didn't work for me. But there is other workaround I found. When you try to connect to tfs server and the browser window "Sign in to TFS" inside Visual Studio opens with javascript error and then nothing happens, right click on the window and select "Properties" find Addres (URL) and copy full path (https://app.vssps.visualstudio.com/_signin?realm=...). Paste this to Internet Expolorer (doesn't work with other browsers) and sign in to tfs and you'll be redirected to some tfs web service. After this switch back to Visual Studio and try to connect to tfs again. This time you should connect without need to log in.
I only needed to set IE as my default browser and it corrected the issue for me.
Yes!!!! I found sol'n
Un-install IE using control panel.
Install it again and make IE default browser with recommened settings.
and you done.
Worked for my case
Update to to IE 11 and everything will work fine.
Update of IE is not an option for me. I need it for testing on this machine. In my case following helped me:
I opened developer tools of IE8 (press F12). It was in 'IE8 Compat View' mode. I switched to 'IE8' mode and specified Document mode to 'IE8 Standards'.
Then I were able to sign in to TFS through IE8. Once I signed in using browser I restarted Visual Studio and everything worked correctly.