Actually (last I checked, at least), Mono installs and runs quite smoothly
on Windows, without hurting your .net installation at all (it is
self-contained). So you shouldn't need a Linux machine to test
your code (for basic tests at least).
Cheers,
--Jonathan
- Original Message -
From: "J
> The code in question is pretty detailed, but the synchronization scheme
boils down to this: I have
> two overlapping (avoiding the word "interlocked") synchronized regions,
where I start, the first,
> start the second, exit the first, then exit the second, like this:
>
> object monitor1 = new obj
I think you are on the right track with apartments. But just
running your code in _an_ STA will not make it run in
_the_ STA in which the MMC interface pointer is
valid. Cross-apartment calls (between the MTA and an
STA, but also between STAs) need proxying (except
for free-threaded objects, etc.).
Indeed, for local variables, even setting them to Nothing on the next
line after their last usage is counter-productive. Consider this :
Sub f()
Dim o as New MyClass
o.DoSomething()
' ... more code not referencing 'o'
End Sub
In release builds, the 'o' local variable stops preventing the GC
from
