Problems with conversion of VC6 projects to VS.Net 2003 project

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Mark A. Me » Sun, 27 Jul 2003 11:52:12


Hello,

I suppose I'm doing something rather stupid, but I can't for the life
of me figure it out.

I've converted a VC6 project to Visual Studio.Net 2003, and i can't
get it to compile at all. I was hoping someone here could help me.

I'm running windows 2000, sp4, I installed VS.Net 2003 yesterday. I
have a VC6 installation also on this machine, and have not removed it.
I've tried using the vcvars32.bat files from both versions of VC to no
avail, as well as trying a host of changes to the project.

I've tried this on a number of projects I have( this one is the
simplest) and I get the same behavior for all of the projects, from
static library builds, to dll builds, to executable builds.

Thank you for your time,

Mark

For the build output I get:

------ Build started: Project: cfgexbtnt, Configuration: Debug Win32
------


Build log was saved at
"file://g:\DevNT\CfgexbtNT\Exe\Debug\BuildLog.htm"
cfgexbtnt - 1 error(s), 0 warning(s)


---------------------- Done ----------------------

Build: 0 succeeded, 1 failed, 0 skipped

and for the buildlog I get:

Build Log ------- Build started: Project: cfgexbtnt,
Configuration: Debug|Win32 -------

Command Lines Creating temporary file
"g:\DevNT\CfgexbtNT\Exe\Debug\RSP000009.rsp" with contents
[
/Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /FD /EHsc /MTd
/Zp1 /Fp".\Debug\cfgexbtnt.pch" /Fo".\Debug" /Fd".\Debug" /W3 /c /ZI
/TP /showIncludes
\DevNT\CfgexbtNT\Src\Main.cpp
]
Creating command line "cl.exe
@g:\DevNT\CfgexbtNT\Exe\Debug\RSP000009.rsp /nologo"
Output Window Results Build log was saved at
"file://g:\DevNT\CfgexbtNT\Exe\Debug\BuildLog.htm"
cfgexbtnt - 1 error(s), 0 warning(s)
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Ben Taylo » Sun, 27 Jul 2003 20:01:29

don't expect it to.

 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Mark A. Me » Mon, 28 Jul 2003 01:59:48

Do you have any suggestions as to what I might do, or is there a way
to get more error information out of the compile step so that I can
try to figure out where the compile step may be going wrong?


On Sat, 26 Jul 2003 12:01:29 +0100, "Ben Taylor"
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Nick Savoi » Mon, 28 Jul 2003 12:45:34

Understanding a compiler error message is not always easy. It can sometimes
hinge on obscure programming language aspects. Work out as many error
messages as you can then cry for help here.

If you're not using Windows headers I'd suggest turning on warning level 4.
It might point out some things you didn't consider.

HTH,
Nick
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Aaron Quee » Tue, 29 Jul 2003 20:18:41

I must be going blind because I can't see any error messages in your email.
:-D

Could you please post the actuall errors, and the few lines of code around
where the problem occurs?

The main problem going from VC6 to VS.NET is improved standards conformance,
i.e. "stuff that worked is now broke". Usually, it's something minor like
needing a const somewhere.

Regards,
Aaron Queenan.
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Kyle Alon » Tue, 29 Jul 2003 22:00:55

I suspect this problem is not with your existing projects, but a general
problem with VS.NET that some others have also encountered. Maybe this post
will give you some clues:
http://www.yqcomputer.com/

---------------------------------------------------
Automate your software builds with Visual Build Pro
http://www.yqcomputer.com/
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Walter Bri » Tue, 29 Jul 2003 22:40:26

In message <uemM1F$ XXXX@XXXXX.COM > of Sat, 26 Jul 2003
20:45:34 in microsoft.public.vstudio.general, Nick Savoiu
<savoiu@ics_uci_edu.?.invalid> writes
I find it grotesque that windows.h does not compile silently at warning
level 4. Meanwhile, with VC 6, I find the following is silent,
reasonably economical, and usually adequate:
#define WIN32_LEAN_AND_MEAN
#pragma warning(disable: 4100 4115 4201 4214 4514)
#include <windows.h>
#pragma warning(default: 4100 4115 4201 4214)

If I used VS.Net 2003, I would deduce and apply something similar as a
priority. The OP should not expect to changing compiler to be a painless
procedure. The following has at least 3 different diagnostic patterns in
different versions of VC.
#include <stdlib.h>
int main(void) { exit(0); }

I find it better to use specialist products to validate code.
My favourite is PC-Lint from www.gimpel.com It is a well spent 250USD.
It uses active comments to allow messages to be filtered in a more
coherent fashion than with just the command line and #pragma directives.
(Macro definitions can't contain #pragma directives.)



My standard method of dealing with obscure errors is to simplify the
problem. Half the problematic code until the code is minimal and the
problem remains. Light usually dawns then.
Probably easier in C than C++. :-)



--
Walter Briscoe
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Mark A. Me » Wed, 30 Jul 2003 00:28:07

n Mon, 28 Jul 2003 13:18:41 +0200, "Aaron Queenan"
< XXXX@XXXXX.COM > wrote:


This is the only output I can see from the build steps. It's what is
on the output tab, and the contents of the buildlog.html file, cut and
pasted into my original email (see below). If there is any other way
to get *more* information, I'd like to know. I have wanring levels
set to 4, and still no more information.

If you look below, in the buildlog.html that I cut and pasted into my
original email, you can seel the actual commandline that the compiler
is building for execuation by cl.exe. What is mysterious about it is
that it looks like cl.exe is never executed. I've checked my
environment variables, and they are all set up properly, and cl.exe
executes ok from a DOS box opened at a number of locations on my
varieous drive locations.

Strange.

I will be out of town until thrursday, but when I get back into my
office, I'll get one of the sample apps from the help and try to
compile it. My guess is that the same behavior will occur.

Looking at Kyle Alons post, it seems that the problem I'm having may
be an install issue, and/or rights/permissions issue with vcspawn.exe.
I'll check that out also on thursday. I'm an logged in with admin
priveleges on the machine I'm working on, so don't understand why
there may be a problem with vccspawn.exe.


I can't determine where inside the code an error is occurring because
I can't get any further diagnostic information. It's a very simple
one file console app. There are a number of header files for external
libraries, though. However, I've made all of the changes to the
project that the online help says to make for an update/upgrade
(iostream lib, WINVER etc.).



Thank you vor your help!

Mark Merrell

 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Mark A. Me » Wed, 30 Jul 2003 00:30:16

Hello Kyle,

I just checked the link you sent me. Thank you very much for your
assistance. I will be out of town and away from my development system
until thursday, but will try the solution the link points to then. It
looks exactly like the problem I seem to be having.

Thank you very much for your help!

Best Regards,
Mark Merrell

On Mon, 28 Jul 2003 07:00:55 -0600, "Kyle Alons" < XXXX@XXXXX.COM >
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Larr » Wed, 30 Jul 2003 02:30:26

Why not? All of mine converted fine. IDE and command line builds alike,
.exes, .dlls. SDK code and DDK code.

I don't have the guys answer since the conversions all just worked for me
and I've not had to debug this particular situation, but "Don't expect to"
is neither helpful nor correct.

Larry









-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.yqcomputer.com/ - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by xTen » Wed, 30 Jul 2003 06:31:18


sometimes
4.


I would add #pragma warning(disable : 4786) as well, at least in my typical
abuse of Microsoft's compiler.
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Ben Taylo » Fri, 01 Aug 2003 17:14:37

Yes - don't use .NET. It's fancy, but just generally
unreliable. I have VS.NET 2002 installed on my machine and
VC6, and I only use VS.NET for the documentation, which in
most cases is also correct for VC6 - ridiculous I know,
but I don't have the MSDN CD for VS6.

there a way
that I can
wrong?
 
 
 

Problems with conversion of VC6 projects to VS.Net 2003 project

Post by Ben Taylo » Fri, 01 Aug 2003 17:15:34

ell, I just find .NET quite poor generally and I only use
the documentation, I don't use the actual IDE.

builds alike,
just worked for me
but "Don't expect to"
wrote in message
can't for the life
2003, and i can't
could help me.
2003 yesterday. I
have not removed it.
versions of VC to no
project.
one is the
projects, from
builds.
Configuration: Debug Win32
cfgexbtnt,
contents
EHsc /MTd
/W3 /c /ZI
at
----
the World!
----