Tool lag

| 6 Comments

One of the problems of having a collection of tools that interoperate is that there's often a lag between when a tool will interoperate with the latest version of another tool. I'm hardly a bleeding-edge tool junky, I wait until RTM before I start using the latest Visual Studio on a daily basis, and in the case of VC 6 I stuck with it (as did most of my clients) until VS2005 came out and actually improved life for unmanaged C++ development... However, it seems that some tools take a long long time to catch up with Visual Studio. Take DevPartner Studio, for example, it seems that it's always lagging by just enough that I spend more time using it in my "legacy" compiler builds than I do in my day to day builds. It's cool that it works on x64 now but it's less cool that I have to use VS2005 or VS2008 to use it...

The problem with tools that lag is that no matter how useful they are the lag and the lack of daily use affects the usefulness of the tool and that always gets evaluated when I have to pay more money for another year of 'support'...

When a tool isn't in the tool box that you use daily you tend to use it less often than you should... Yes, the reason for this rant is that I've just found a couple of leaks with DevPartner that lived a little longer than they should because I'm developing the code in VS2010 and DevPartner isn't there in the toolbar nagging at me to use it. And, yes I know that I'm the one at fault for not using the tool anyway even though it's easier to ignore right now...

This kind of thing usually isn't actually too much of a problem for me as using these kinds of tools is on my release check-list but as I get clients that only want VS2010 builds it gets more likely that the tool lag will bite.

So, in summary, a version of DevPartner Studio for Visual Studio 2010 would be nice and, even better, if you can't ship with the RTM of the compiler then a roadmap that gives a hint about when you might ship, or even a hand wavey indication of an intention to ship, would be nice...

6 Comments

I had so many problems with DevPartner I finally gave up on that piece of junk. Unfortunately, I never found a replacement.

Agree that DevPartner is junk. I've found Visual Studio Profiler to be pretty decent these days.

Hello again, Len.

I am surprised to read your blog entry about compatibility between DevPartner Studio and the lack of Visual Studio 2010 support. The fact is that DevPartner Studio sim-shipped with VS2010. Meaning, that we announced support for VS2010 in cooperation with Microsoft at their world-wide launch events and had our RTM available simultaneously with the VS2010 release. You need version 10.0 for this support. Thank you for your kind words in other regards and keep your eyes open for much more in the future. Trust me, the lab is hard at work on areas of the product that are strongly desired in the development community.

If you have not seen them, you can catch up on some of the release announcements here:

http://vs2010.microfocus.com/
http://msdn.microsoft.com/en-us/vstudio/ff625827.aspx
http://blogs.msdn.com/b/terryclancy/archive/2010/05/07/vsip-partners-light-the-vs-2010-launch-afterburners.aspx

Thanks,


Cliff

Cliff,

That's interesting to hear since I've got a support contract and nobody has bothered to contact me to tell me how to get the later version (and it's not available from my support downloads...).

Support has been pretty dire since the change to MicroFocus, *I* had to chase you guys to get my contract renewed, etc...

Len,

I hear you and will make sure that your comments are passed along. Being in the lab, I hope you can appreciate that I am removed from those processes but I do have great respect for the feedback and I WILL make sure it gets to the right people.

~Cliff

Thanks Cliff.

Leave a comment