This seems to be a false positive, based on the following reasons.
I've scanned my computer without any viruses being found, but as soon as I build the installation in Visual Studio, Avast reports a worm in the setup.exe.
I've uploaded the setup.exe to Virus Total, see report, where 2 out of 35 virus scanners reports a possible worm.
I've now sent the setup.exe file to the Avast team, in order for them to verify that it indeed is a false positive, so that they can update their virus definitions for the future.
So What's New?
• Support for Visual Studio 2008.
• Optimizations of the code rule validation engine, which now utilizes background threads and incremental parsing.
• Rules were not always loaded when opening a solution in Visual Studio 2008.
• Context menus in code editor and on solution item didn't show.
• Name refactoring didn't work in Visual Studio 2008.
• bool.TryParse(stringValue, out boolValue) no longer reports a name violation (fix in DXCore 3.0).
• Steps taken to assure that the MSI setup works with UAC in Vista, according to this blog post
• Code Style Enforcer doesn't work well when UAC is turned on in Windows Vista, but for how long can you stand it anyway :).
Please send me feedback and comments about this new version, especially about the optimizations to the code rule violations engine, since it might have introduced a bug or two.
I first thought there must be some problem with my data template, but when showing it from a WPF application everything worked just fine. My next instant thought was that there must be some message filter, in the Windows Forms application, stealing the keyboard input.
I then created a new Windows Forms application and brought up the modeless WPF Window from there, by calling Show, only to notice the same problem. I then changed to a modal window, by calling ShowDialog instead, and suddenly everything responded as it should.
It was time to start some Google:ing…
The solution, to my big surprise, was to explicitly enable keyboard input from Windows Forms, by calling the static method ElementHost.EnableModelessKeyboardInterop. This call takes a Window as parameter and essentially registers an input hook with the Windows Forms application object, running the message loop, and calls ComponentDispatcher.RaiseThreadMessage. The call to EnableModelessKeyboardInterop can be made in the constructor, if the Window is inherited, or simply before calling the Show method.
For more information read about Sharing Message Loops Between Win32 and WPF.
I now hope that they will merge these changes into DXCore 3.0+ also.
I was then informed by DevExpress that the new DXCore 3.0+ version was supposed to have special support for background thread analysis through the new code issue provider model. This, on the other hand, proved to be too much beta still since it didn’t behave as expected.
Right now I’m waiting for the DevExpress support team to analysis my code and the threading issues with DXCore 2.5+. The other alternative is to wait for a newer and more final version of DXCore 3.0+ and hopefully the background thread analysis will be good enough there, even though I’m rather skeptical about it right now.
The optimization release is therefore put on hold for now, so I might look into some other issues first. Right now I feel in need of a good vacation though and therefore I’m leaving for Florida on Friday. I can only hope that I’ll get back with a lot of new enthusiasm :)!!!