[Bug 45129] New: Some applications/ installers fail trying to run Windows PowerShell cmdlets or .NET apps that reference 'System.Management.Automation' v1.0.0.0 assembly
wine-bugs at winehq.org
wine-bugs at winehq.org
Fri May 4 04:52:54 CDT 2018
https://bugs.winehq.org/show_bug.cgi?id=45129
Bug ID: 45129
Summary: Some applications/installers fail trying to run
Windows PowerShell cmdlets or .NET apps that reference
'System.Management.Automation' v1.0.0.0 assembly
Product: Wine
Version: 3.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs at winehq.org
Reporter: focht at gmx.net
Distribution: ---
Hello folks,
just for documentation purpose and to collect potential dupes in future.
Example from bug 45033
.NET helper executable extracted from custom action which makes use of
'PowerShell' class.
--- snip ---
$ wine ./customactions.exe ChangeAppStartingCursor
...
01ae:fixme:wer:WerRegisterRuntimeExceptionModule
(L"C:\\windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscordacwks.dll",
0x630000) stub!
...
01ae:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime"): stub
01ae:fixme:advapi:ReportEventW
(0xcafe4242,0x0001,0x0000,0x00000402,(nil),0x0001,0x00000000,0x32d0f0,(nil)):
stub
01ae:err:eventlog:ReportEventW L"Application: customactions.exe\nFramework
Version: v4.0.30319\nDescription: The process was terminated due to an
unhandled exception.\nException Info: System.IO.FileNotFoundException\nStack:\n
at customactions.Program.ChangeAppStartingCursor()\n at
customactions.Program.Main(System.String[])\n"
...
Unhandled Exception:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Management.Automation, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. File not found.
at customactions.Program.ChangeAppStartingCursor()
at customactions.Program.Main(String[] args)
wine: Unhandled exception 0xe0434352 in thread 1ae at address
0x3620023:0x7b446ec7 (thread 01ae), starting debugger...
--- snip ---
That assembly is part of Windows PowerShell:
https://docs.microsoft.com/en-us/dotnet/api/system.management.automation?view=powershellsdk-1.1.0
which provides 'PowerShell' class implementation for .NET apps.
https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.powershell?view=powershellsdk-1.1.0
--- quote ---
PowerShell Class
Definition
Namespace:
System.Management.Automation
Assembly:
System.Management.Automation.dll
Represents a PowerShell command or script to execute against a Runspace(Pool)
if provided, otherwise execute using a default Runspace. Provides access to
different result buffers like output, error, debug, verbose, progress, warning,
and information.
Provides a simple interface to execute a powershell command:
--- quote ---
https://4sysops.com/wiki/differences-between-powershell-versions/
--- quote ---
PowerShell 2.0 is integrated in all Windows versions since Windows 7 and
Windows Server 2008 R2. If you want to ensure that a PowerShell script also
works properly on a system with PowerShell 2.0, you can switch to a PowerShell
2.0 prompt on every Windows version after Windows 7 with PowerShell.exe
-Version 2. However, this will only work if you installed .NET Framework 2.0 /
3.5.
--- quote ---
$ wine --version
wine-3.7-65-ge637a6f0bf
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list