[Bug 12401] NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API for managed assembly installation on NTFS filesystems need reparse point/junction API support (FSCTL_SET_REPARSE_POINT/FSCTL_GET_REPARSE_POINT)

[WineHQ Bugzilla]

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

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|NET Framework 2.0, 3.0, 4.0 |NET Framework 2.0, 3.0, 4.0
                   |installers and other apps   |installers and other apps
                   |that make use of GAC API    |that make use of GAC API
                   |for managed assembly        |for managed assembly
                   |installation need reparse   |installation on NTFS
                   |point/junction API support, |filesystems need reparse
                   |i.e.                        |point/junction API support
                   |DeviceIoCtl(FSCTL_SET_REPAR |(FSCTL_SET_REPARSE_POINT/FS
                   |SE_POINT/FSCTL_GET_REPARSE_ |CTL_GET_REPARSE_POINT)
                   |POINT)                      |

--- Comment #50 from Anastasius Focht <focht at gmx.net> ---
Hello Jacob,

--- quote ---
Requesting more info: Which wine versions are affected by this?
--- quote ---

you mean with regards to .NET Frameworks installations? Well, technically it's
no longer a hard requirement/blocker for .NET installers since Mar 2009
(https://source.winehq.org/git/wine.git/commitdiff/8044c11ecfca09e2b643feccb95a4d8f645ba656
-> Wine >= 1.1.18) *unless* your WINEPREFIX and/or installation target
directory resides on NTFS partition which is unlikely the case for most users.

I thought people were aware of this fact. See also my comment from 2009
(https://bugs.winehq.org/show_bug.cgi?id=10601#c23):

--- quote ---
this specific problem is worked around by commit
8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see
comment #15 for analysis.

You might close this one but if the ongoing discussion results in current
default FS type to be changed/reverted again you have to *reopen* this bug.

The implementation of NTFS junction point API is tracked separately by bug
12401
...
--- quote ---

Maybe we should have been more explicit in the summary line from start. I've
refined it now.

Talking about .NET Framework installers in general: .NET Framework 2.0 (SP1,
SP2), 3.0 (SP1), 3.5 (SP1), 4.x should be pretty ok. Only few permanent issues
are present, such as need for native 'mscoree' override (if you use default
Wine build, without '--disable-mscoree') and the delay on the .NET 3.x language
packs (broken MS installer). You also need to ensure that any extra
dependencies are installed in order (winetricks usually takes care of this).

I've recently installed all of them in the same 32-bit WINEPREFIX (WinVer =
'Windows XP') without any winetricks/dll overrides, starting from .NET 2.0
(SP1, SP2), through 3.0 (SP1) and 3.5 (SP1) up to late 4.7 (requires default
'Windows 7'). Aaron Stebner's .NET Framework setup verification tool
successfully validated the WINEPREFIX (files and registry entries, running .NET
2.0 and 4.0 test apps). Quite an impressive feat.

Be aware there were a couple of broken Wine 4.x releases, where either
regressions in MSI and/or other components prevent proper installation.

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.