Force CLR optimization on .NET to finish so mscorsvw.exe can go away

[GoogleCodeExporter]

What steps will reproduce the problem?
1. dotnet40
2. Start wine
3. Check tasks (top, htop) for mscorsvw.exe

What is the expected output? What do you see instead?
No long-term mscorsvw.exe process when Wine is used after initial .NET 
Framework installation.

What version of the product are you using? On what operating system?
20140302 on Xubuntu 14.04 x86_64

Please provide any additional information below.

http://blogs.msdn.com/b/davidnotario/archive/2005/04/27/what-is-mscorsvw-exe-and
-why-is-it-eating-up-my-cpu-what-is-this-new-clr-optimization-service.aspx

Workaround: .../ngen.exe executequeueditems

Mostly a nuisance problem during app installation troubleshooting or when 
making a backup of a new Wine directory after third-party components are 
installed (before a problematic app install is started).

Original issue reported on code.google.com by jhanso...@gmail.com on 19 Feb 2015 at 12:08

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Does this help?

Original comment by austinenglish@gmail.com on 27 Feb 2015 at 12:49

Attachments:

• ngen_execute.txt

[GoogleCodeExporter]

(sorry for the late follow-up)

It doesn't appear to work with dotnet40 at least.  I think the command line is 
the problem.

If I execute "wine ngen.exe executequeueditems" then ngen loads but eventually 
exits without doing much.

If I execute "wine 
$WINEPREFIX/drive_c/windows/Microsoft.NET/Framework/v4.0.30319/ngen.exe 
executequeueditems" then I see a bunch of sub-processes triggered that look 
like pre-compiling.  Subsequent executions result in it just exiting.

Original comment by jhanso...@gmail.com on 17 Mar 2015 at 1:38

[GoogleCodeExporter]

Please move discussion to here:
https://github.com/Winetricks/winetricks/issues/480

Original comment by austinenglish@gmail.com on 30 Mar 2015 at 6:52