Other issues or features related to Microsoft Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After adding URL's in IE mode pages it has a expire days of 30. I would like to know how to extend more than 30 days as per InternetExplorerIntegrationLocalSiteListExpirationDays policy.
Please help.
Other issues or features related to Microsoft Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thanks for catching that bug. Fixed now.
I'm not sure a GUI is really necessary because a non-technical user can add their IE Mode pages via Edge and then just run the script. A technical user, who may want to automate the configuration for other users, shouldn't have any trouble editing the script.
But if you decide to create a GUI, I'd be very interested to see what you come up with. I have a lot of expertise with HTAs. I have no experience with WPF or WinForms. I have seen that for PowerShell, AnyBox looks like an easy way to add GUI elements, but I've never tried it.
I'm not sure a GUI is really necessary because a non-technical user can add their IE Mode pages via Edge and then just run the script. A technical user, who may want to automate the configuration for other users, shouldn't have any trouble editing the script.
The GUI would be mainly for those who messed up adding the URLs in the first place, and they are confused about what exactly did they add. The FindReplace (or RemoveEntries) is well and good, but if they don't remember, and the entry is too long to copy from Edge, and they can't be bothered to Reset then Re-Add ... then it will help to have a simple window populated with whatever is in the current user_list_data_1, with 2 buttons beside each line, "edit" and "remove", and an empty field at the end, with an "add" button beside it ... maybe even an import section, where it reads from a csv and populates a scrollable list, with an "add bulk" button.
It's helpful sometimes to visualize the current state, in order to be able to make a decision about what they want to add. They can do it from the Edge settings itself, but that's a multi-step action, while a GUI would make it all run from the script.
But you are right, this is basically me being lazy, and thinking "Hey, Lazy poeple are people too :) "
But if you decide to create a GUI, I'd be very interested to see what you come up with. I have a lot of expertise with HTAs. I have no experience with WPF or WinForms. I have seen that for PowerShell, AnyBox looks like an easy way to add GUI elements, but I've never tried it.
Oh, good, as I have no experience with HTAs whatsoever. I was going to create a simple (read: fugly) web page, and use the click driven actions of the buttons to implement this. You will probably make a better one in a fraction of the time.
I have experience with winforms on PowerShell though, as I like my scripts to show up as a system tray icon, with context menus to enable/disable different aspects of the script. I even go a step further and use ps2exe module to convert the ps1 scripts to executables. Helps with curcumventing the Execution Policies for the scripts, and just plain gets ignored by the Antimalware, except when I kill processes (which you are doing) but there is a work around for that, as far as I recall.
I have never tried AnyBox either. I skimmed it just now, and I think it's too much of a hassle for the quick "1 form" jobs.
Anyway, I'll create the GUI for the ps1, and avoid the embarrassment of creating an HTA :D
I will post when I have something ...
If I were to make a GUI, I would separate the data from the script and have the GUI part in one script and the rest in the other (worker) script. The settings would all go in an INI file (XML and JSON are also options) and the GUI script's job would be to read the current settings from the file, present them for additions and edits, and then on submit, write a new settings file, and finally run the worker script passing the name of the settings file as the only parameter. That's how I do it with WinSetView, which has an HTA interface and a PowerShell worker script.
The current script would then only need to be modified to accept one parameter (name of the settings file) and if that parameter is present, get the settings from the file, instead of from the variables at the top of the script, and process the changes without any prompts.
To continue the potential coding discussions, I suggest taking this offline. We can exchange email (you can find my email in the WinSetView manual). Or we can communicate via GitHub. You may want to consider making a fork of IEModeExpiryFix, especially if we end up not agreeing on an approach for a GUI. ;-)
I would welcome an offline discussion. I will email you once I get home (past 5 PM here now), and we'll see how this goes.
I will not fork this though. This is your script, and however you would want the script done, then that's how it's going to be done.
greetings, perform the test by closing the browser session and apply the script. it worked correctly.