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 :)!!!

After that I will begin targeting Code Style Enforcer against the new version 3 of DXCore, in order to use some new nice features of that release. This means that DXCore version 3 will soon be a requirement instead of version 2.

I’ve now redesigned when and how the code rule violations are checked, by utilizing the DXCore Parse event together with asynchronous calls. I’m almost done with the optimization and hopefully we can try it out in our team in the upcoming week.
A new release can therefore be expected in early January, which will perform a lot better, but unfortunately won’t have a lot of new features, if any at all.
Happy New Year!!!

I'm not sure if this has something to do with Visual Studio 2008, DXCore 2.5.8, Code Style Enforcer 2.1.32 or if it only happens to me.
Please comment on this blog post if any of you experience the same problem and in which environment. I will look more into it when I get back from DevConnections.

Back Next