Interesting problem:
One of our products uses the System.Management.Automation.dll assembly from
AppFabric 2.0. It has AssemblyVersion 1.0.0.0 and AssemblyFileVersion
6.1.7600.16385.
The System.Management.Automation.dll assembly that appears to come with
AppFabric 2.1 or PowerShell v3.0 has
Wow, that's beginner mistake. Get them to fix the file version or rename
the file. Or you can install to a new location (which essentially renames
the file). DefaultVersion basic lies to the Windows Installer and it will
never be certain the file that is on disk is the right one (because the one
Can I mitigate the effect on Repair by enabling checksums and having the
install forcibly verify them?
I'm sure my managers will be trigger their Microsoft support contracts, but I
have to deal with it.
Installing in a different location will require significant code changes as
this thing
Meanwhile, I can confirm that PowerShell v3.0 and WMF 3.0 both installs this
assembly.
Errata on the AppFabric references. That should be AppFabric 1.0 and 1.1
respectively. ADFS 2.1 uses an assembly,
Microsoft.IdentityServer.Powershell.dll, which is linked against this
4 matches
Mail list logo
