ddemeyer

Put more thought into it... * DisplayName can already be done, with a lookup over Find-IshUser explicitly asking for the FISHDISPLAYNAME field in the PowerShell process perhaps a post-routine over...

The idea is quite old, not picked up yet. Given the switch from either `WcfSoapWithWsTrust` or `WcfSoapWithOpenIdConnect` to `OpenApiWithOpenIdConnect`. This set of cmdlets might be a good candidate to directly...

Thanks, more food for thought... It looks like we are heading for option 2 so backwards compatible only doing x times more API calls then before, so theoretically somewhat slower...

In all scenarios the `-ModifiedStep` goes up, but you could also count down. So from very recent to the birth date of the database. This way you get recent results...

Was looking for more standardized terminology and a way to make querying from Now to database birth date the default. So still pursuing backward compatible option 2. - [ ]...

Investigating further, the idea is good, the performance and accuracy guarantees however not. ISHRemote tries to be version-agnostic where possible, for #49 there are two reasons to put this idea...

Hi @tintinno There is a bigger problem as mentioned on [ISHRemote > Prerequisites](https://github.com/sdl/ISHRemote#prerequisites) as > Note that we rely on Windows PowerShell (FullCLR), and not PowerShell Core (CoreCLR) which relies...

Time moves on, and I'm happy to close this issue with the release of ISHRemote v7, see https://github.com/sdl/ISHRemote/blob/master/Doc/ReleaseNotes-ISHRemote-7.0.md and https://github.com/RWS/ISHRemote/releases/tag/v7.0 for more details. In short ISHRemote v7 works on PowerShell...