ISESteroids 2.2 is almost done. Today, we decided to invite anyone interested to look at it and test drive the beta.
The link to the current beta version can always be found in version history. Or, you can download the beta here:
(Note: Beta versions will not be available on the PSGallery because we do not want to confuse anyone who auto-updates ISESteroids from the Gallery based on new versions and suddenly finds himself with a beta version).
To use the beta version, installation does not differ from production version: download and unzip the file, run install.bat – that is it.
Who can participate?
Anyone can. The beta version shares the requirements with the production version: either use the trial period, or your license.
Your existing licenses will just work fine with ISESteroids 2.2. Remember, we have a pretty simple and straight model: pay once, enjoy many. Free updates for ISESteroids 2 in all of its subversions and updates. Definitely no maintenance fees, subscriptions, or other follow up costs.
So a better question would be: who should participate? If you are curious, hungry for more, and enjoy providing feedback, then this is right for you.
If you are super busy and just want ISESteroids to help you get your job done, then better stick to the production version. While the beta version is very very stable, it is just not fully tested (which obviously is the whole point of the beta program).
What to expect?
The current beta version is 18.104.22.168, and it is a really major update. Not on the surface however. ISESteroids 2.1 was already pretty feature-rich. But inside.
We reworked the entire engine, made it much much faster, ensured that even 30K+ lines of code can be edited smoothly. We started to implement memory optimizations, too, to reduce the memory footprint. So this release is all about speed and robustness under the hood. Compared with the current production version, you’ll see areas of brutal speed improvements (squiggles, navigating documents, scrolling). Other areas are beyond our control (loading a document will still take some time).
There are a couple of new features, too, of course. For example, the function navigator combobox now also lists code regions. That’s really cool because this way you can organize large scripts and see your “code layout” in the function navigator combobox.
The function referencer sorts regions first, then functions/workflows/configurations. Regions are sorted by startoffset (in the order in which they appear in your code), while the rest is sorted alphabetical.