.net 3.5 installer happy already?!

[Dan Kegel]

After the recent success with the .net 3.0 installer, I decided to try .net 3.5:

$ wget http://download.microsoft.com/download/7/0/3/703455ee-a747-4cc8-bd3e-98a615c3aedb/dotNetFx35setup.exe
$ sha1sum dotNetFx35setup.exe
b0ca05c12ebb9a3610206bad7f219e02b7873cbd  dotNetFx35setup.exe
$ rm -rf ~/.wine
$ sh winetricks dotnet20
$ wine dotNetFx35setup.exe

And surprise, although there was a crash dialog about
printfilterpipelinesvc, the installer reported that it finished ok!

I have no idea if the installed runtime actually works,
and there are a ton of log messages after installation
finishes.  (Presumably the .net optimization service?)
But it's nice to have gotten this far.
- Dan

p.s.
A few of the common warnings at random:

Could not load type 'System.DateTimeOffset' from assembly 'mscorlib,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
while compiling method token 0x6000723

fixme:shell:URL_ParseUrl failed to parse L"System.ServiceModel"
Could not load file or assembly 'System.ServiceModel, Version=3.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its
dependencies. Exception from HRESULT: 0x80070002 while compiling
method token 0x60001bc

Error compiling System.ServiceModel.Web, Version=3.5.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35: Could not find or
load a type. (Exception from HRESULT: 0x80131522)

fixme:shell:URL_ParseUrl failed to parse L"System.ServiceModel"
Warning: System.IO.FileNotFoundException: Could not load file or
assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' or one of its dependencies. Exception
from HRESULT: 0x80070002
File name: 'System.ServiceModel, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089'
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].