Posted - Jul 29 2014 : 1:27:06 PM At least its not just us. That does not help you much, but it is a small consolation from my point of view. Thankfully this is not a massive problem for you.
If you only need to reference a small number of functions from this namespace, have you considered creating VA Snippets for them? You would need to remember the shortcuts, but you could create them all with the same initial shortcut, and then turn On this setting:
so that the snippets will be suggested after typing the common prefix.
xMRi
Posted - Jul 29 2014 : 06:01:51 AM I Just turned VAX off and it is correct that even VS-2010 doesn't recognize the namespace.
No this isn't an option, because of internal class names. But in fact it isn't real great problem, because there are just a few functions that I need to call. Sometimes it is possible to live without intellisense, even it is hard :)
feline
Posted - Jul 28 2014 : 11:54:40 PM Thank you for the update, this is indeed case=6261, unfortunately for now the only known solution is to remove the rename_namespace. I am a little surprised that "Get content from default Intellisense" is not helping, by the sounds of it the IDE is not handling the renamed namespace that well either.
Hopefully removing the rename_namespace is an option for you for now.
xMRi
Posted - Jul 28 2014 : 06:37:26 AM I just verified it. Using the #import statement without rename_namespace works. I can use the defined interfaces freely. The check on "Get content from default Intellisense" is already set.
As a test can you please try removing the "rename_namespace("AGComDebug")" part of the #import line, and after VA has finished parsing this change, see if this makes any difference?
In case 6261 removing the rename_namespace allowed the imported symbols to be suggested correctly.
Depending on your IDE, you may find that turning On:
VA Options -> Listboxes -> Get content from default Intellisense
