PowerShellTools 4.4 and Internal Packaging Team
PS C:\windows\system32> $PSVersionTable
PSVersion 5.1.16299.1146 PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.16299.1146 CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
PowerShellTools 4.4+ and Visual Studio 2017 Professional 15.8.6+. Summary my company has stringent security around software acquisition and installation. This includes re-packaging software installations for install to workstations. I do not think they understand how Extensions and Updates are made available to Visual Studio.
A test lab machine I was provided the post-package installation of PowerShellTools 4.4 along with Visual Studio 2017 15.8.6. In short I believe all their package did was put the PowerShellTools file/folder footprint on the machine without actually running any installation steps. There is no PowerShellToolsPro.Vsix, etc.
What they did put files at C:\ProgramData\Adam_Driscoll\PowerShell_Tools_for_Visual_Studio_4.4. - $MSBuild (folder) - $PublicAssemblies (folder) - _rels (folder) - Commands (folder) - ItemTemplates (folder) - package (folder) - ProjectTemplates (folder) - Snippets (folder) - Several files at the base including catalog.json, EULA.RTF, log4net.dll, dll's, txt's, json's, pkgdef's, ps1's, etc.
This to me looks like a post-install footprint. I do not see the PowerShellTools anywhere else, Visual Studio 2017 certainly gives no indication it is present. Any advice/documentatin that I could provide our intrernal packaging team on the proper installation procedures?
