>>>Hi all,
>>>
>>>Has anyone run into any issues running a WPF multi threaded application on a VM? We have an application that is in QA cycle now and one of the testers is having some issues at startup where the startup code is in a background thread. I found some references on the web regarding some known issues surrounding VM's but not real specific. We cannot duplicate this on a non-VM.
>>>
>>>Just curious if anyone has any discoveries or information about this.
>>
>>Can you be more specific about the problems being experienced?
>>Are you using BackgroundWorker or managing your own threads?
>>At a guess the most likely problems will be if the thread attempts to interact with the UI and you use the wrong DispatcherObject...
>>UPDATE: Oh, and VM - Virtual Machine or ViewModel :-}
>
>I am using a BackgroundWorker in part because it handles the interaction better to the UI thread. I am raising an event within the Worker_ProgressChanged event of the Background worker to raise an event on the application of when it is at specific stages. This does not seem to be happening in as the stage does not get notified. What I have discovered however, is I can now duplicate this on my machine if I run the exe from the directory directly. It does not happen if I run the application from within VS either in debug mode or in release mode.
>
>What would be different specifically if running the exe or running within VS in release mode? I can post some code if it helps to understand what is happening.

Code would be good (especially if it is repro code :-} )
I must admit I've not come across anything the implies behaviour will differ between running from the IDE and an EXE directly but I suppose it's not impossible.....