2

PowerShell is case insensitive language and so are the modules like WebAdministration expected to be.

This doesn't work:

PS IIS:\AppPools> Set-ItemProperty .\DefaultAppPool -Name Enable32BitAppOnWin64 -Value $true

Whereas this works:

PS IIS:\AppPools> Set-ItemProperty .\DefaultAppPool -Name enable32BitAppOnWin64 -Value $true

Difference is only in capital and small letter 'e' in property name. Moreover, the first command doesn't even throw any error.

Can anyone explain this behaviour?

Martin Brandl
  • 56,134
  • 13
  • 133
  • 172
zerocool18
  • 523
  • 1
  • 4
  • 11
  • https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/15077202-make-propeties-name-case-insensitive-for-creating – zerocool18 Jul 04 '16 at 13:36

1 Answers1

1

This is probably a bug since the behaviour differs for different Windows versions (e. g. for Windows 10, the first letter must be lowercase whereas for Windows 7 not).

There is also a related question on SO.

Community
  • 1
  • 1
Martin Brandl
  • 56,134
  • 13
  • 133
  • 172