problem when converting project from vc6 to vc7

  • Thread starter Thread starter Daylor
  • Start date Start date
D

Daylor

hi.
i got a sample project written in vc6.
when i compile and build the exe (debug mode ) , the exe file size is 221KB,
and the program work ok.

if i open this project in vc7 , build the exe, the exe file is 156KB
and the program load, but not works well.

what im missing here.. ?
 
Take care that there is a bug in Visual Studio 2002 with the functions
isspace, isalpha, ... These functions always display an assert when they
receive in parameter a character higher than 128. i.e: isspace('?'); does
not work!!! you must use isspace((unsigned) '?');

Take care that there is a bug with Visual Studio 2003 with the function
double pow(int, int) that always returns 0 if the exponent is negative =>
1^(-3) return 0 instead of 0.001 !!! You must use a prototype that takes in
parameter a floating point value for the exponent.

I don't remember well but if you use Custom build, Post Build Event, ... the
define $(TargetDir), ... have the path terminated by '/' but that was not
the case in VS 6 !
 
Ok, the newsgroups does not accepts characters higher than 128 too! ;-)

Replace in "i.e: isspace('?'); does not work!!! you must use
isspace((unsigned) '?');" the character '?' by the symbole EURO (AltGr-E on
my computer) or another character higher than 128.

Lionel Schiepers
 
Daylor said:
well , i didnt explain what is not working , cause i dont think ,it can help
to explain the details.

the code is the same code.

my question was, what things i should take care when converting from vc6 to
vc7.

about the specfic application :
this is sample of telephony application that using dll.
in vc7 , when u ring , the call isnt answer at all.
Click to expand...

Do you have the latest service pack for VC7? Do you check for error
codes everywhere in your code? I haven't worked with TAPI (if that's
what it is), but all functions have some return code you must check.

Can you debug both version of the app (with appropriate debuggers) and
pinpoint the location where their behaviour differs? Are you
absolutely sure two versions have _identical_ code, without the
changes even in whitespace characters? Compare them with WinDiff (I
hope you kept the old project). Are both versions of the same
configuration (Debug)?

Try setting warning level for the whole project on the highest
possible (Level 4), and reset overridden settings for individual
source files. This'll give you the clues of what's safe in VC6 and not
in VC7. Also, search the code for #pragma directives which disable
warnings.

HTH
 
Back
Top