References in VS2005

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Slide-O-Mix - 29 Nov 2005 19:30 GMT

I am currently converting a large solution from vs2k3 to vs2k5. The
conversion went smoothly, however I am getting a lot of warning about
duplicate imports of items in my Managed C++ projects. I removed all the
references and re-added them (they are to other projects in the solution),
but I still get tons of warning like the following:

c:\ccviews\acearl_hci_v300_2\sv_tools\hci\boardmanagers\plxboardmanager\bin\rele
ase\plxapi.net.dll : warning C4945: 'Win32' : cannot import symbol from
'c:\ccvi
ews\acearl_hci_v300_2\sv_tools\hci\boardmanagers\plxboardmanager\bin\release\plx
api.net.dll': as 'PlxApiNet::Win32' has already been imported from another
assem
bly 'PlxApi.Net'

I didn't have these warnings in 2k3 and am wondering why I am getting them
in 2K5, they don't seem to make sense to me.

Is there something I should look for in my project setup that might be
causing these?

Thanks

Reply to this Message

Holger Grund - 30 Nov 2005 15:26 GMT

> c:\ccviews\acearl_hci_v300_2\sv_tools\hci\boardmanagers\plxboardmanager\bin\rele
> ase\plxapi.net.dll : warning C4945: 'Win32' : cannot import symbol from
[quoted text clipped - 6 lines]
> I didn't have these warnings in 2k3 and am wondering why I am getting them
> in 2K5, they don't seem to make sense to me.

This suggests that you have imported two different versions (or the
same version from different locations)

I don't know whether you looked at the full diagnostic. The Task/
Error List View in the IDE doesn't show context information.
Make sure you switch to the Build Output window to see context
information. Make sure that the paths match.

-hg

Reply to this Message

Peter Oliphant - 30 Nov 2005 18:47 GMT

Just a heads up, probobaly not at all related to anything causing you a
problem. BUT...

How did you convert your 2003 source to 2005? Did you let the language do it
(i.e., when you tried to open the source in 2005 it gave you a warning
saying it can't be converted back to 2003 and then gave you an option to let
it do the conversion)? Or did you open a new 2005 project and manually
import your source files?

The automaric method is a lot faster and very convenient - but can cause
problems! When I did just that the source converted just fine in the sense
it compiled - for the next 2 weeks! Then, all of a sudden, it started
reporting errors in source locations where there was no source (like
comments and blank lines!). A lot of phantom bugs too - like adding a line
of code that does nothing (int x = 0 ;) causing a line of code elsewhere to
generate an error.

I solved my problem by doing the second method - opened up a new 2005
project, manually copied the source files into the project directory
manually, imported them via 'Add Existing Item", and then compiled. Never
had a problem (that I didn't put in via programming - known as bugs ---hehe)
since... : )

[==P==]

>I am currently converting a large solution from vs2k3 to vs2k5. The
> conversion went smoothly, however I am getting a lot of warning about
[quoted text clipped - 17 lines]
>
> Thanks

Reply to this Message

Slide-O-Mix - 30 Nov 2005 19:08 GMT

> Just a heads up, probobaly not at all related to anything causing you a
> problem. BUT...
[quoted text clipped - 20 lines]
>
> [==P==]

Yes, I used the conversion assistant, I'll give the "fresh project" idea a
try and see if that works. Thanks for the idea.

slide

Reply to this Message

Rate this thread:

References in VS2005

Free Magazines