Migrating vc++6 to .NET

  • Thread starter Thread starter Dale Bourne
  • Start date Start date
D

Dale Bourne

I'm trying to migrate a VC++6 program to VC++2005.

This program solution consists of projects A, B, and C. Project B
depends on project A, and project C depends on project B. Project B
utilizes a third party library compiled under version 6. I also have a
new version of the library compiled under VS2005. I've tried both
versions, changing the library and include directories, and the
additional dependencies, and get the same compile error. So, I don't
think it has anything to do with the library, must be some difference
in the way version 6 and 8 utilize(?) 3rd party libraries.

The program compiles and functions properly under VC++6. After
correcting errors remaining after conversion process, solution fails
to compile with the following error:

fatal error C1083: Cannot open source file: 'FixTools.lib': No such
file or directory

The 'include' & 'library' directories are correct in options. The 3rd
party library is listed as Linker->Input->Additional Dependencies.

The only changes I've made to the code are correcting errors due to
stricter type checking, changes in some library calls, etc..

Any help would be greatly appreciated.
 
fatal error C1083: Cannot open source file: 'FixTools.lib': No such
file or directory

That's strange - you've got a compiler error referring to a .lib file
as though it's a .cpp file. It sounds to me as though something's
caused you to have a corrupted project.

Dave
 
David said:
That's strange - you've got a compiler error referring to a .lib file
as though it's a .cpp file. It sounds to me as though something's
caused you to have a corrupted project.

Yeah, lib files aren't used by the compiler, but by the linker. Did someone
type

#include "FixTools.lib"

?
 
That's strange - you've got a compiler error referring to a .lib file
as though it's a .cpp file. It sounds to me as though something's
caused you to have a corrupted project.

Dave

Yeah, I felt that was strange, but, I am QUITE new to the .NET scene
and thought that maybe it was some new way VS handled libs.

Dale
 
Yeah, lib files aren't used by the compiler, but by the linker. Did someone
type

#include "FixTools.lib"

?

After grep'ing the entire source tree, nothing like that was found.
Guess I'll start over with original source and be more observant of
the conversion.

Thanks guys.

Dale
 
David Lowndes said:
That's strange - you've got a compiler error referring to a .lib file
as though it's a .cpp file. It sounds to me as though something's
caused you to have a corrupted project.

Dave

Not true - you can include .lib files in the project and set up the project
to link to them. It works correctly. I am at home now and can't provide
the setup details offhand but we do that all the time for almost every
..vcproj at work.
 
Back
Top