Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / July 2004

Tip: Looking for answers? Try searching our database.

Compiling a VS 7.1 project in VS .NET 2002 (7.0)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dean - 05 Jul 2004 17:17 GMT
Hi there,

My first post in this newsgroup. I've recently switched from Borland C++ to
VS C++ to work on a specific app written by someone else.

The "solution" projects and source code were written and developed on VS
7.1.

I only have .NET 2002 (7.0) and can't really justify spending more money
upgrading to 7.1.

When I try and compile a couple of the apps, I get a compiler error asking
for MFCS71.lib (file not found).

The original author tells me I should be able to compile his apps fine in
7.0. He mentioned that the setting to tell it to use my version of the
libraries is in project->settings, but I've been all the way through the VS
menus and can't find anything which lets me change this.

Can anyone help? The original author is now on holiday for a week and I'd
quite like to deploy these apps this coming weekend.

Many thanks,

Dean
David Mair - 05 Jul 2004 17:47 GMT
> Hi there,
>
[quoted text clipped - 19 lines]
>
> Many thanks,

Did you do a clean and build (rebuild)?  I can't find any references to
a version specific MFC or RTL import library or DLL in any of the
project files for one of my MFC projects so my guess is that the project
configuration option to enable MFC is an embedded feature that
automatically generates import library dependencies at compile time.  If
so then that would explain why I see lots of references to version
specific MFC libraries in my object files and executables but not in my
project files.  If that's it then a rebuild should suffice to cause all
references to be replaced by those appropriate to your compiler.  The
only other thing I can think of to mention is to consider whether or not
the v7.1 project files are completely compatible with the 7.0 project
loader.
Dean - 05 Jul 2004 21:11 GMT
Got it - I managed to open the project file in notepad and manually edit to
"7.0" from "7.1".

All compiling fine now.

Next thing is, where do I find the version number for a project (which I
need to change)?

Thanks,

Dean

> > Hi there,
> >
[quoted text clipped - 32 lines]
> the v7.1 project files are completely compatible with the 7.0 project
> loader.
David Mair - 05 Jul 2004 22:17 GMT
I've never noticed one in the project manager and, to be honest, I have
to hand edit project files to be able to build Apache for Win32 using
Visual Studio so unless someone can point out where to edit it in the
project manager you might just have to do it by hand each time.  I guess
the project upgrade message box that appears when you load projects for
older versions handles this for you but if the older versions don't
downgrade the version then there's only the hope that we've missed the
option.

> Got it - I managed to open the project file in notepad and manually edit to
> "7.0" from "7.1".
[quoted text clipped - 59 lines]
>>the v7.1 project files are completely compatible with the 7.0 project
>>loader.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.