Re: newbie configuration questions
From: Frank Hickman (fhickman_nosp_at_m_noblesoft.com)
Date: 03/12/04
- Next message: Kostatus: ".ini file problem"
- Previous message: Scott McPhillips [MVP]: "Re: data transfer"
- In reply to: Wayne Dernoncourt: "Re: newbie configuration questions"
- Next in thread: Wayne Dernoncourt: "Re: newbie configuration questions"
- Reply: Wayne Dernoncourt: "Re: newbie configuration questions"
- Reply: Wayne Dernoncourt: "Re: newbie configuration questions"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Mar 2004 18:36:10 -0500
The Knowledge Base on MSDN is a good source of information. The online help
for VC is also a good source of information about the workings of the IDE.
When you say integrate multiple libraries, are you talking about 3rd party
libraries that you would like to use in VC? There are several ways to let a
VC project know about additional libraries and their locations. Environment
variables and within the IDE under Tools->Options->Directories and simply
adding them to the project files tree control. As for where to learn about
this, sorry, I'm self taught so I cannot tell you anything about formal
training. I'm sure that the MSCD Certification program would be a good
start.
HTH
-- ============ Frank Hickman NobleSoft, Inc. ============ Replace the _nosp@m_ with @ to reply. "Wayne Dernoncourt" <wayned@panix.com> wrote in message news:c2t3uf$5gh$1@reader1.panix.com... > Frank Hickman <fhickman_nosp@m_noblesoft.com> wrote: > > > This is a good group for VC questions but depending on the > > specifics of the question, there may be a more appropriate > > group. For instance, the missing DLL problem your > > experiencing is MFC related while it can be answered here, > > there is an MFC specific group microsoft.public.vc.mfc. > > As for your problem...there are basically two types of > > builds, Release and Debug. When using MFC, they get linked > > to different versions of the MFC DLLs. The d on the end of > > the filename let's you know it's a debug DLL. The debug > > DLLs are not redistributable and therefore not on a > > non-development system. If your using CPPUnit on it's own > > system which does not contain the VC++ 6.0 development > > environment, then you'll need to build a Release version > > for testing. > > > HTH > > It's a start. After a couple of hours futzing with MSDN, > etc. we realized that the "D" was referring to the debug > version, which we didn't have. We didn't know we weren't > supposed to have it. When I get back to work on Monday, > we will be playing some more with this. > > What I'm looking for is some organized way of learning > about the configuration of Visual C++ to make this process > better. This seems to be as much a black art, complete > with potions and spells, as science. It seems that courses > teach about C++ with MS extensions (MFC & .Net, etc.) but > trying to integrate multiple libraries needs knowledge > that isn't readily apparent. Where is this kind of > knowledge available at? > > -- > Take care | This clown speaks for himself, his job doesn't > Wayne D. | pay for this, etc. (directly anyway)
- Next message: Kostatus: ".ini file problem"
- Previous message: Scott McPhillips [MVP]: "Re: data transfer"
- In reply to: Wayne Dernoncourt: "Re: newbie configuration questions"
- Next in thread: Wayne Dernoncourt: "Re: newbie configuration questions"
- Reply: Wayne Dernoncourt: "Re: newbie configuration questions"
- Reply: Wayne Dernoncourt: "Re: newbie configuration questions"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|