VS 2003 upgrades results in C2872: 'CONNECTDATA' ambiguous symbol

[Lee Gillie]

I have a VS6 project which I brought into VS .NET, and all has been
building fine. Then I upgraded to VS 2003 and I have one source which
will no longer compile. Any clues?

Compiling...
DotNetManagedEx port.cpp
C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\atlmfc \include\atlcom .h(5529) : error C2872: 'CONNECTDATA' :
ambiguous symbol
could be 'C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\Platfo rmSDK\Include\O CIdl.h(395) : tagCONNECTDATA
CONNECTDATA'
or 'C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\includ e\vcclr.h(15) :
System::Runtime ::InteropServic es::CONNECTDATA '
C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\includ e\xmemory(136) : while compiling class-template member
function 'HRESULT
ATL::IConnectio nPointImpl<T,pi id,CDV>::EnumCo nnections(IEnum Connection
s ** )'
with
[
T=CKeyBuild,
piid=& _GUID_d74f30ea_ 21d1_4857_b8d2_ 75ba604fc8a1,
CDV=ATL::CComDy namicUnkArray
]
d:\ODP\PPS\PPS System\PPSLibNE T\_IKeyBuildEve nts_CP.h(6) : see
reference to class template instantiation
'ATL::IConnecti onPointImpl<T,p iid,CDV>' being compiled
with
[
T=CKeyBuild,
piid=& _GUID_d74f30ea_ 21d1_4857_b8d2_ 75ba604fc8a1,
CDV=ATL::CComDy namicUnkArray
]
d:\ODP\PPS\PPS System\PPSLibNE T\KeyBuild.h(17 ) : see reference to
class template instantiation 'CProxy_IKeyBui ldEvents<T>' being
compiled
with
[
T=CKeyBuild
]
C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\atlmfc \include\atlcom .h(5530) : error C2872: 'CONNECTDATA' :
ambiguous symbol
could be 'C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\Platfo rmSDK\Include\O CIdl.h(395) : tagCONNECTDATA
CONNECTDATA'
or 'C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\includ e\vcclr.h(15) :
System::Runtime ::InteropServic es::CONNECTDATA '
C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\atlmfc \include\atlcom .h(5537) : error C2872: 'CONNECTDATA' :
ambiguous symbol
could be 'C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\Platfo rmSDK\Include\O CIdl.h(395) : tagCONNECTDATA
CONNECTDATA'
or 'C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\includ e\vcclr.h(15) :
System::Runtime ::InteropServic es::CONNECTDATA '

[Arjun Bijanki [VCPP MSFT]]

--------------------

From: "Lee Gillie" <AN************ *******@odp.com >
Subject: VS 2003 upgrades results in C2872: 'CONNECTDATA' ambiguous symbol
Date: Wed, 6 Aug 2003 07:55:26 -0700
Lines: 62
I have a VS6 project which I brought into VS .NET, and all has been
building fine. Then I upgraded to VS 2003 and I have one source which
will no longer compile. Any clues?

Try moving your "using namespace System;" directive down after the
#includes. Does that solve the problem?

--
Arjun Bijanki, Microsoft Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

[Lee Gillie]

Ajun -

Thanks for replying. I tried what you suggested, but it made no
difference. I tried also moving the #using <xxx.dll> statements.

- Lee

"Arjun Bijanki [VCPP MSFT]" <ar****@online. microsoft.com> wrote in
message news:18******** ******@cpmsftng xa06.phx.gbl...

--------------------

From: "Lee Gillie" <AN************ *******@odp.com >
Subject: VS 2003 upgrades results in C2872: 'CONNECTDATA' ambiguous symbol Date: Wed, 6 Aug 2003 07:55:26 -0700
Lines: 62

I have a VS6 project which I brought into VS .NET, and all has been building fine. Then I upgraded to VS 2003 and I have one source which will no longer compile. Any clues?

Try moving your "using namespace System;" directive down after the
#includes. Does that solve the problem?

--
Arjun Bijanki, Microsoft Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no

rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

[Tanveer Gani [MSFT]]

--------------------

From: "Lee Gillie" <AN************ *******@odp.com >
References: <ug************ **@TK2MSFTNGP09 .phx.gbl> <18************ **@cpmsftngxa06 .phx.gbl>Subject: Re: VS 2003 upgrades results in C2872: 'CONNECTDATA' ambiguous symbolDate: Tue, 12 Aug 2003 09:13:32 -0700
Lines: 37
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <ei************ *@tk2msftngp13. phx.gbl>
Newsgroups: microsoft.publi c.dotnet.langua ges.vc
NNTP-Posting-Host: user.odp.com 204.130.175.250
Path: cpmsftngxa06.ph x.gbl!TK2MSFTNG P08.phx.gbl!tk2 msftngp13.phx.g bl
Xref: cpmsftngxa06.ph x.gbl microsoft.publi c.dotnet.langua ges.vc:27149
X-Tomcat-NG: microsoft.publi c.dotnet.langua ges.vc

Ajun -

Thanks for replying. I tried what you suggested, but it made no
difference. I tried also moving the #using <xxx.dll> statements.

- Lee

"Arjun Bijanki [VCPP MSFT]" <ar****@online. microsoft.com> wrote in
message news:18******** ******@cpmsftng xa06.phx.gbl...

--------------------

> From: "Lee Gillie" <AN************ *******@odp.com >
> Subject: VS 2003 upgrades results in C2872: 'CONNECTDATA'ambiguous symbol > Date: Wed, 6 Aug 2003 07:55:26 -0700
> Lines: 62

>
> I have a VS6 project which I brought into VS .NET, and all hasbeen > building fine. Then I upgraded to VS 2003 and I have one sourcewhich > will no longer compile. Any clues?
>

Try moving your "using namespace System;" directive down after the
#includes. Does that solve the problem?

--
Arjun Bijanki, Microsoft Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no

rights.

Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Lee,

The ambiguous symbol error simply says that the compiler has seen a symbol
called "CONNECTDAT A" and it can't determine whether it's the one from the
namespace System::Runtime ::InteropServic es or the one from the global
namespace. Presumably you have a using namespace
System::Runtime ::InteropServic es directive somewhere in your code. Try
doing one of these:

1. Localize the directive. Instead of putting it in the global namespace
move it to a local scope where you need it.

2. Use a *using declaration* instead of a using directive:

using System::Runtime ::InteropServic es::CONNECTDATA ;

If there's any ambiguity at this point, you'll get an immediate error.

3. Remove the using directive and use the fully qualified name.

Option (3) should solve your problem if (1) and (2) don't work.
--
Tanveer Gani, Microsoft Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm