| T O P I C R E V I E W |
| Uniwares |
Posted - Jan 14 2008 : 08:12:13 AM
VAX is showing me symbols from the .Net assemblies, although I am NOT using any of them, in fact its not even a managed C++ project. |
| 7 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Apr 10 2008 : 12:53:11 AM
case=11391 is fixed in build 1632 |
| Uniwares |
Posted - Jan 14 2008 : 2:20:50 PM
I guess its possible. Although why would anybody do that with IJW available? No, I am talking here about pure ISO C++ projects contra Managed C++ projects. While I expect the first to NOT show any symbols from the .Net framework, I hope they will show up in the other (if referenced). |
| feline |
Posted - Jan 14 2008 : 1:59:58 PM
You probably know more about this than me. Is it possible to reference / use .NET from pure unmanaged C++ code?
The simplest method of "break VA" is clearly not going to work here. VA is designed to treat C++ and CLR C++ differently, so ignoring .NET symbols while in pure C++ sounds doable on paper, assuming the symbols are actually tagged as coming from .NET.
I am trying to keep the idea as simple as possible, and would like to avoid project specific settings, or anything like that if possible. |
| Uniwares |
Posted - Jan 14 2008 : 1:31:29 PM
Yes, I do use .Net but not in all projects. So I would like to keep it out when not used. |
| feline |
Posted - Jan 14 2008 : 1:18:53 PM
That makes sense. This is an interesting question, and I have asked:
case=11391
Do you work with C# or .NET ever? The "simplest" solution might just be to break VA's knowledge of .NET, but that is likely to do bad things if you ever code in C#, etc. |
| Uniwares |
Posted - Jan 14 2008 : 08:42:05 AM
Basically symbols that exist in my code, but also in the .net libraries. It happens usually when there is a problem with MY namespace, like forgetting to add the correct namespace when using a symbol.
You can repro that probably by defining a symbol like feline::Exception and then use it without specifying the namespace. VAX should show it then as System.Exception instead.
Quite confusing when you have many symbols, many namespaces, and are transitioning legacy code, moving old code into namespaces. |
| feline |
Posted - Jan 14 2008 : 08:36:42 AM
Which symbols? Is this easily triggered?
I am not aware this is happening to me, but it could be I am just not noticing. |
