IE Mode - large enterprise production support requires F12 developer tools for debugging

%3CLINGO-SUB%20id%3D%22lingo-sub-792340%22%20slang%3D%22en-US%22%3EIE%20Mode%20-%20large%20enterprise%20production%20support%20requires%20F12%20developer%20tools%20for%20debugging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-792340%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20indicated%20on%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fedge-ie-mode%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fedge-ie-mode%3C%2FA%3E%26nbsp%3BIE%20mode%20does%20not%20support%20IE11%20or%20Microsoft%20Edge%20F12%20developer%20tools.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20actually%20planning%20to%20migrate%2030'000%20Windows%207%20desktops%20to%20Win10%2FOffice365-Cloud%20Services.%20Actually%20we%20have%20a%20dual%20browser%20strategy%20with%20Chrome%20and%20IE11.%20There%20are%20still%20some%20business%20critical%20applications%20depending%20on%20IE11.%20A%20crucial%20pre-condition%20for%20migration%20to%20Win10%2FOffice365%20is%20the%20ability%20to%20decouple%20browser%20adoption%20dependencies%20from%20Win7%20-%26gt%3B%20Win10%2FOffice365%20rollout.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20strategical%20move%20to%20Chromium%20Edge%20with%20IE-Mode%2C%20available%20on%20both%20platforms%20is%20already%20a%20big%20help%20for%20this.%20Great.%3C%2FP%3E%3CP%3ENow%2C%20our%20production%20support%20is%20used%20to%20have%20the%20'developer%20tools'%20feature%20available%20for%20debugging%20in%20with%20IE11.%20It%20would%20be%20a%20crucial%20pre-condition%20to%20have%20these%20debugging%20capabilities%20available%20on%20Edge-Chromium%20IE-Mode%20as%20well.%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20are%20the%20obstacles%20for%20providing%20F12%20Developer%2FDebugging%20features%20in%20IE-Mode%3F%3C%2FP%3E%3CP%3EMight%20be%2C%20MS%20was%20just%20not%20aware%20of%20this%20use%20case%20at%20the%20time%20of%20deciding%20this.%3C%2FP%3E%3CP%3EThomas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-796488%22%20slang%3D%22en-US%22%3ERe%3A%20IE%20Mode%20-%20large%20enterprise%20production%20support%20requires%20F12%20developer%20tools%20for%20debugging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-796488%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F383798%22%20target%3D%22_blank%22%3E%40tomotello%3C%2FA%3E%26nbsp%3BWe%20recommend%20using%20IE11%20in%20standalone%20mode%20for%20debugging%20and%20development.%20If%20you%20have%20constraints%20using%20IE11%20standalone%2C%20another%20option%20is%20to%20try%20IEChooser.exe%20(C%3A%5CWindows%5CSystem32%5CF12%5CIEChooser.exe).%20Will%20that%20help%20your%20scenario%3F%20If%20not%2C%20could%20you%20please%20elaborate%20on%20why%20these%20options%20will%20not%20work%20for%20you%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

As indicated on https://docs.microsoft.com/en-us/deployedge/edge-ie-mode IE mode does not support IE11 or Microsoft Edge F12 developer tools. 

We are actually planning to migrate 30'000 Windows 7 desktops to Win10/Office365-Cloud Services. Actually we have a dual browser strategy with Chrome and IE11. There are still some business critical applications depending on IE11. A crucial pre-condition for migration to Win10/Office365 is the ability to decouple browser adoption dependencies from Win7 -> Win10/Office365 rollout. 

The strategical move to Chromium Edge with IE-Mode, available on both platforms is already a big help for this. Great.

Now, our production support is used to have the 'developer tools' feature available for debugging in with IE11. It would be a crucial pre-condition to have these debugging capabilities available on Edge-Chromium IE-Mode as well. 

What are the obstacles for providing F12 Developer/Debugging features in IE-Mode?

Might be, MS was just not aware of this use case at the time of deciding this.

Thomas

1 Reply

@tomotello We recommend using IE11 in standalone mode for debugging and development. If you have constraints using IE11 standalone, another option is to try IEChooser.exe (C:\Windows\System32\F12\IEChooser.exe). Will that help your scenario? If not, could you please elaborate on why these options will not work for you?