New version of Power Threading Library posted today!

I posted a new version of my Power Threading Library today on http://wintellect.com/Resources/visit-the-power-threading-library

This version has some minor bug fixes and a few new (minor) classes. See the Power Threading Overview.pdf file for change log information.

On May 26 2009 12:30 PMBy jeffreyr
With 6 Comments

Comments (6)

  2. Christian

    Hi Jeffrey,

    I have a little question to the ReaderWriterLock in .NET 2.0. It seems that there exists a potential deadlock problem caused by reentrancy. Following scenario:

    - The UI-Thread calls a AquireReadLock and must wait because another thread holds a WriterLock
    - Now something strange happened: the runtime processed via NativeWindow.DebuggableCallback the message queue
    => reentrance
    - Why does AquireReadLock allows the windows messages to be processed and how I can prevent this?

    Thanks for your help!

  3. JeffreyR

    I know that Monitor allows this but I didn't think that the ReaderWriterLock allowed this. Monitor allows this to allow COM interop to work correctly. There are blog posts on the web that describe this.

  5. Venkatesu

    Hi Jeffrey,

    first of all thanks for writing such a wonderful power threading library.

    i am facing a small problem,when i am using AsyncEnumerator class in remoting(.NET 2.0),i got the follwing problem.

    Type 'Wintellect.Threading.AsyncProgModel.AsyncEnumerator' in Assembly 'Wintellect.Threading, Version=4.2.3323.23897, Culture=neutral, PublicKeyToken=167f00fdf109b063' is not marked as serializable.

    channel.BeginDownloadFile(FileFullName, Position, DownSpeed, ae.End(), null);

    it is working fine when i use WCF(.net 3.5) but i am facing problem in remoting(.NET 2.0).

    Please help me in this.

    i am waiting for your message.Thanks in advance.

Leave a Comment

Archives

Tags