Home > Archive > VC Language > May 2006 > MFC project looking for mfc70d.lib when converted to VS2005
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
MFC project looking for mfc70d.lib when converted to VS2005
|
|
|
| Hi,
I have a MFC-based project that was initially developed using VS 7.0.
I've migrated it to VS 2005 using the initial conversion wizard that
comes up. On compiling, I got a set of deprecation warnings (like for
strcpy), which I supressed using the _CRT_SECURE_NO_DEPRECATE
preprocessor definition. I now get a linker error saying "cannot open
file 'mfc70d.lib'". I thought it would link to the new version
(mfc80d.lib?) automatically, but looks like I'd need to do something for
it. How do I get rid of this error?
TIA,
SD
| |
| Abdo Haji-Ali 2006-05-31, 8:15 am |
| "SD" <SD@discussions.microsoft.com> wrote in message
news:9FA943CC-61E7-4CBA-A65C-5F029651BCD4@microsoft.com...
> Hi,
>
> I have a MFC-based project that was initially developed using VS 7.0.
> I've migrated it to VS 2005 using the initial conversion wizard that
> comes up. On compiling, I got a set of deprecation warnings (like for
> strcpy), which I supressed using the _CRT_SECURE_NO_DEPRECATE
> preprocessor definition. I now get a linker error saying "cannot open
> file 'mfc70d.lib'". I thought it would link to the new version
> (mfc80d.lib?) automatically, but looks like I'd need to do something for
> it. How do I get rid of this error?
Did you try a "Rebuild All"?
--
Abdo Haji-Ali
Programmer
In|Framez
| |
| Tom Serface 2006-05-31, 7:15 pm |
| Make sure you don't have it included in another library that you're using
that hasn't been converted and recompiled to the newer (8.0) version.
Tom
"SD" <SD@discussions.microsoft.com> wrote in message
news:9FA943CC-61E7-4CBA-A65C-5F029651BCD4@microsoft.com...
> Hi,
>
> I have a MFC-based project that was initially developed using VS 7.0.
> I've migrated it to VS 2005 using the initial conversion wizard that
> comes up. On compiling, I got a set of deprecation warnings (like for
> strcpy), which I supressed using the _CRT_SECURE_NO_DEPRECATE
> preprocessor definition. I now get a linker error saying "cannot open
> file 'mfc70d.lib'". I thought it would link to the new version
> (mfc80d.lib?) automatically, but looks like I'd need to do something for
> it. How do I get rid of this error?
>
> TIA,
> SD
|
|
|
|
|