[Bug 43688] New: DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

Bug ID: 43688
           Summary: DyKnow 5.4 Fails to install, reports
                    System.Runtime.InteropServices.MarshalDirectiveExcepti
                    on
           Product: Wine
           Version: 2.16
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 59140
  --> https://bugs.winehq.org/attachment.cgi?id=59140
DyKnow 5.4 installation log

This an error trying to install DyKnow 5.4 on a clean 32 bit prefix running
wine-staging 2.16. See debug log.

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

Fabian Maurer  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Fabian Maurer  ---
Does "winetricks -q dotnet40" help?

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

--- Comment #2 from [e-mail] ---
Created attachment 59146
  --> https://bugs.winehq.org/attachment.cgi?id=59146
After dotnet40 log

Install log of DyKnow 5.4 after running winetricks -q dotnet40.

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

--- Comment #3 from [e-mail] ---
Installation after installing dotnet40 gives a different log and a popup dialog
named "applycomsettings.exe ... Initialization Error" containing "unable to
find a version of the runtime to run this application." along with another
popup dialog box that contains "Error: -1603 Fatal error during installation.
Consult Windows Installer Help (Msi.chm) or MSDN for more information."

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from [e-mail] ---
winetricks -q dotnet35sp1 allows dyknow to install in wine-staging 2.17.

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

--- Comment #5 from Fabian Maurer  ---
There's nothing fixed in wine, is there?

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |INVALID
             Status|RESOLVED                    |CLOSED

--- Comment #6 from [e-mail] ---
I don't think so, but changing the don't version did allow the program to
install, next is figuring out why it only renders a large black window.

[Bug 43688] DyKnow 5.4 Fails to install, reports System.Runtime.InteropServices.MarshalDirectiveException

https://bugs.winehq.org/show_bug.cgi?id=43688

--- Comment #7 from Fabian Maurer  ---
If the original problem still persists, then there is no reason in closing this
bug.