| T O P I C R E V I E W |
| rprouse |
Posted - Oct 28 2009 : 10:31:52 AM
With VS2010 removing Intellisense support for managed C++, we are looking for alternatives. We would like to move to 2010 and are setting our budget for next year, so I am now doing a bit of research.
Will Visual Assist X give us Intellisense for our managed C++?
Thanks. |
| 5 L A T E S T R E P L I E S (Newest First) |
| holedigger |
Posted - Oct 29 2009 : 7:47:09 PM
Yes, we support the newer (VS2005+) C++/CLI syntax in the current release of VA X, and we will continue to do this in VS2010. So if you are seeing any issues with it, we want to know about it. As for the older (VS2003) "Managed C++" syntax (I can't say I've even tried it in a while) we've assumed most devs have moved on to C++/CLI. If there are enough people still using the old syntax, we can revisit support for it.
|
| willdean |
Posted - Oct 29 2009 : 7:24:28 PM
quote:
Originally posted by drac
If you look at this blog entry http://blog.wholetomato.com/2009/09/15/va-x-in-vs2010/ you will see that the example is Managed C++.
I think you'll find that's "C++/CLI", not "Managed C++", which is the older "C++ with .NET syntax" which has been deprecated for some time.
I've no idea what Wholetomato's plans are, but I do remember that during the brief time I was writing managed C++ (urgh), VA wasn't particularly good at it.
If the OP is actually talking about C++/CLI, then I think VA is OK at it, and if MS really do drop it in 2010, then I'd guess VA will pick up the slack.
That is after all how they started, back when VC had completely unusable Intellisense in the late 1990s.
|
| rprouse |
Posted - Oct 29 2009 : 09:06:51 AM
Thanks for the info. |
| drac |
Posted - Oct 28 2009 : 11:31:41 AM
If you look at this blog entry http://blog.wholetomato.com/2009/09/15/va-x-in-vs2010/ you will see that the example is Managed C++. |
| rhummer |
Posted - Oct 28 2009 : 10:47:05 AM
VA X supports managed C++ now, I wouldn't see why they wouldn't going forward. :) |
