Recently I’ve been playing with Windows PowerShell 2.0 again in the context of my day-to-day activities. One hint should suffice for the reader to get an idea of what’s going on: push-based collections. While I’ll follow up on this subject pretty soon, this precursor post explains one of the things I had to work around.
Being designed around the concept of managed object pipelines, one may expect powershell.exe to be a managed executable. However, it turns out this isn’t the case completely. If you try to run ildasm.exe on the PowerShell executable (which lives in %windir%system32WindowsPowerShellv1.0 despite the 2.0 version number, due to setup complications), you get the following message: https://goo.gl/XXyT2b #DataIntegration #ML
