[Bug 10467] Making Microsoft .NET 2.0 to work in wine, based on example app FastMD5 1.4 for NET 2.0

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=10467





--- Comment #73 from Anastasius Focht <focht at gmx.net>  2008-12-15 12:34:04 ---
Hello,

--- quote ---
Reproduce:
clear wine
./winetricks corefonts msxml3 msxml6
./winetricks dotnet20
wine ./Fastmd5.exe
--- quote ---

I don't see the point of all those dependencies?
The FastMD5 example app only needs .NET 2.0 Framework (winetricks dotnet20),
nothing more.

--- quote ---
FastMD5 is working pretty well in 1.1.10. Calculates correctly all hashes,
there are some problems with clipboard handling.

..
Click Open, Select info.txt, Click "Create Hash", copy anything (can be empty
string) to the clipboard (from any application), click "<- Clipboard", Click
one more time "Create Hash", click "Crate Hash" one more time.

Crash
--- quote ---

The problem you are experiencing has nothing to do with clipboard action.
Ideally any other operation can trigger the same problem - you just need to
wait long enough (until the garbage collector/finalizers ought to run).
It's already covered by bug 13462 though not well understood from reading
comments.
The patch there prevents the crash by providing needed interface stub to the
.NET runtime.

.NET simply treats the callback stub "unimpl" as disconnected RPC endpoint.
There will be small resource leaks (for runtime callable wrapper) when the
garbage collector/finalizer is run but that causes no harm - and most
importantly: prevents a crash.
This applies to all .NET apps, maybe the importance for bug 13462 is
underestimated hence no further attempt was made to get a patch in.

--- quote ---
Problem is in fixme:ole:CoGetContextToken stub
--- quote ---

Don't try to guess... it won't work ;-)
While this stub will be a source of problem in future (needed to support COM
context switching properly) this FIXME can be currently ignored.

Regards


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.