Browser emulation defaults

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
amoseng
Posts: 4
Joined: Mon Mar 26, 2018 1:44 am

Browser emulation defaults

Post by amoseng »

Hi!

When doing browser emulation in a form project, the default browser being emulated is Internet Explorer. Are there any plans to upgrade this default to using Edge instead? I couldn't find any specifics on Edge registry paths, but I would assume they don't use the same base path, as they are two different products.

If you have some info on this, or already have plans, please let me know :)

Current default declaration used is:

Code: Select all

[Microsoft.Win32.Registry]::GetValue('HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer', $valueNames[$i], '0')
Top
User avatar
Alexander Riedel
Posts: 7457
Joined: Tue May 29, 2007 4:43 pm

Re: Browser emulation defaults

Post by Alexander Riedel »

[Topic moved by moderator]

In order to facilitate a timely answer please post in the appropriate product forum with the information requested. Posting in an unrelated forum, like 'Feedback' will get your question to the wrong people and potentially delay an answer.

https://blogs.msdn.microsoft.com/patric ... atibility/

We will investigate what can be done.
Alexander Riedel
SAPIEN Technologies, Inc.
Top
User avatar
amoseng
Posts: 4
Joined: Mon Mar 26, 2018 1:44 am

Re: Browser emulation defaults

Post by amoseng »

I figured it didn't belong in the support forums, as it's not really an issue. At least not yet :D
Thanks for looking into it!

Local info:
Product: PowerShell Studio 2019 (64 Bit)
Build: v5.6.167
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.18362.
Top

Return to “PowerShell Studio”