Installing torque in Visual Studio.NET
by Jim Spear · in Torque Game Engine · 02/11/2004 (8:37 pm) · 37 replies
I read that .NET isn't officially supported but some have sucessfully installed it. I would be eternally grateful if one of those kind souls would give me a step-by-step on how they did it.
Thanks in Advance,
Jim
Thanks in Advance,
Jim
About the author
#22
This I am absolutely sure of.
The way CVS works guarantees this.
I have done both, and gotten the same results. I get the EXACT same resulting files and the vs7 project works fine.
If you are getting differences in files then there is something wrong on your machine or the process by which you are using cvs.
Whom ever gave you the "use vs6" advice was mistaken, I never got the vs6 to up-convert to vs7 correctly. I am using vs7.1 ( 2003 ).
There is a 2002 compatiable ( vs7 ) in cvs somewhere. That would make a better place to start than the vs6 files. Just update the vs module using the last date BEFORE vs7.1 ( 2003 ) was released to find the 2002 ( vs7 ) file.
02/19/2004 (2:02 pm)
NO - it does NOT make a difference whether it is a fresh "check out" or an "update" of an existing "check out", you get the EXACTLY the same files and result from a fresh checkout vs update to HEAD ( or any other TAG ) in CVS.This I am absolutely sure of.
The way CVS works guarantees this.
I have done both, and gotten the same results. I get the EXACT same resulting files and the vs7 project works fine.
If you are getting differences in files then there is something wrong on your machine or the process by which you are using cvs.
Whom ever gave you the "use vs6" advice was mistaken, I never got the vs6 to up-convert to vs7 correctly. I am using vs7.1 ( 2003 ).
There is a 2002 compatiable ( vs7 ) in cvs somewhere. That would make a better place to start than the vs6 files. Just update the vs module using the last date BEFORE vs7.1 ( 2003 ) was released to find the 2002 ( vs7 ) file.
#23
I did not know there was a 2002(vs7) compatiable in cvs, thanks. My problem is using 2002(vs7) with HEAD release vs7 solution as I stated. You cannot download HEAD and use vs(2002) without modification.
My point was using an older Torque release (before 2003 vs7) and just updating will work fine. Downloading HEAD and using 2002(vs7) does not work fine.
Hence my reasoning in why there is a difference in fresh download and updating.
I wish they had made VS.net compaitable between versions atleast. Or have a patch so that 2002(vs7) could read 2003(vs7).
02/19/2004 (2:17 pm)
Ah thank you for clarifying that. The vc6 advice was in this thread near the top.I did not know there was a 2002(vs7) compatiable in cvs, thanks. My problem is using 2002(vs7) with HEAD release vs7 solution as I stated. You cannot download HEAD and use vs(2002) without modification.
My point was using an older Torque release (before 2003 vs7) and just updating will work fine. Downloading HEAD and using 2002(vs7) does not work fine.
Hence my reasoning in why there is a difference in fresh download and updating.
I wish they had made VS.net compaitable between versions atleast. Or have a patch so that 2002(vs7) could read 2003(vs7).
#24
Then you are talking about a partial cvs update that would not include getting the latest solution file. Which may or may not work, since so much stuff has been re-organized and moved around lately.
Doing a cvs update on the entire project will indeed get the exact same files at doing a check out. If you do as you suggest, without excluding the vs directory, you will still get the vs7.1 solution file regardless.
Everything that WAS in CVS still IS in CVS, that is the ENTIRE point of using a Version Control System!
02/19/2004 (2:32 pm)
Quote:My point was using an older Torque release (before 2003 vs7) and just updating will work fine. Downloading HEAD and using 2002(vs7) does not work fine.
Then you are talking about a partial cvs update that would not include getting the latest solution file. Which may or may not work, since so much stuff has been re-organized and moved around lately.
Doing a cvs update on the entire project will indeed get the exact same files at doing a check out. If you do as you suggest, without excluding the vs directory, you will still get the vs7.1 solution file regardless.
Everything that WAS in CVS still IS in CVS, that is the ENTIRE point of using a Version Control System!
#25
This being the getting started forum, I'd assume most users are new to this. Thus they would be getting a fresh download of the ENTIRE code.
Anyhow, I don't know how you turned this into a cvs debate. My post was to state that fresh downloads or "out of the box" as some would say, won't work with VS7(2002).
1. You can't use latest HEAD with VS7(2002)
2. You can't use Release_1_2_0 with VS7(2002)
3. You can't convert VC6 dsw to VC7(2002)
I needed help getting those problems fixed.
Any new user will have those same problems if he is using VS7(2002).
02/19/2004 (5:06 pm)
Why do update if you are getting all the files? Just get the whole thing. Update is to save bandwidth by only getting files that changed. In fact I just changed the VC7 SLN file and then did a full update from release_1_2_0 to HEAD and the SLN file was not updated. I chose the FULL directory update as well. Please try it before preaching how cvs works.This being the getting started forum, I'd assume most users are new to this. Thus they would be getting a fresh download of the ENTIRE code.
Anyhow, I don't know how you turned this into a cvs debate. My post was to state that fresh downloads or "out of the box" as some would say, won't work with VS7(2002).
1. You can't use latest HEAD with VS7(2002)
2. You can't use Release_1_2_0 with VS7(2002)
3. You can't convert VC6 dsw to VC7(2002)
I needed help getting those problems fixed.
Any new user will have those same problems if he is using VS7(2002).
#26
02/19/2004 (9:04 pm)
Now you have me confused. Are we talking about VS7 or VS.NET?
#27
in 2002 they came out with VS.net, it was the 2002 version.
In 2003 they came out with a new version of VS.net
its called VS.net 2003
and you can't open projects saved with vs.net 2003 with vs.net 2002
02/19/2004 (9:08 pm)
VS7 is VS.netin 2002 they came out with VS.net, it was the 2002 version.
In 2003 they came out with a new version of VS.net
its called VS.net 2003
and you can't open projects saved with vs.net 2003 with vs.net 2002
#28
02/19/2004 (9:28 pm)
Ok, can you tell I'm new to Visual C++ ;) I just found out that my symbols folder is pointed to nothing. Where should I direct it to? I'm sure that this is where all the problems are caused
#29
You don't have to mess with symbols if you are using vc7
If you are using vc6, then read 7th post down by Gonzo.
Otherwise I wouldn't mess with it unless you are having trouble with it.
02/19/2004 (9:43 pm)
Which are you using? VC6? VC7?You don't have to mess with symbols if you are using vc7
If you are using vc6, then read 7th post down by Gonzo.
Otherwise I wouldn't mess with it unless you are having trouble with it.
#30
02/19/2004 (9:51 pm)
I am using Visual C++.NET 2003. I get loads of errors saying no symbols loaded. The folder is blank so I haven't installed the symbols or something.
#31
02/19/2004 (10:05 pm)
Also I'm using Release_1_2_0 and the VC7 files
#32
C:\WINDOWS\SYMBOLS\DLL (WinXP)
or
C:\WINNT\SYMBOLS\DLL (Win2K)
and give that a shot, there should be symbol files already loaded in those folders.
if you still have problems, read through this resource and see if it can help you get setup. You guys make me wish I had .Net so I could check this out myself, lol.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtskinstallingdebugsymbols.asp
02/20/2004 (4:35 am)
James, you can default your symbols to this folder to start...C:\WINDOWS\SYMBOLS\DLL (WinXP)
or
C:\WINNT\SYMBOLS\DLL (Win2K)
and give that a shot, there should be symbol files already loaded in those folders.
if you still have problems, read through this resource and see if it can help you get setup. You guys make me wish I had .Net so I could check this out myself, lol.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtskinstallingdebugsymbols.asp
#33
02/20/2004 (4:50 am)
Thanks, I don't have any symbols loaded on my pc :(. The download is too big for my computer to handle so I'll look for them on my cd. Also, is there any diffrence from the Torque SDK compiled and the pre-compiled version? It seems that there are diffrent folders.
#34
http://www.garagegames.com/mg/projects/torque1/downloads.php
and the SDK source, then yes, big difference. (Unless they have changed the pre-compiled in the last 6 days)
02/20/2004 (5:56 am)
If you are refering to the pre-compiled found here....http://www.garagegames.com/mg/projects/torque1/downloads.php
and the SDK source, then yes, big difference. (Unless they have changed the pre-compiled in the last 6 days)
#35
02/20/2004 (6:00 am)
Yep, that's the one. Its the same as the public demo (so far anyway). So there is a big diffrence?
#36
but I must need to get another one. Which one should I get (for XP)?
Thanks
02/22/2004 (1:51 am)
Ok, I have gotten some symbols and have gotten rid of a lot of the no symbols found errors. I have downloaded the first pack from here: http://www.microsoft.com/whdc/ddk/debugging/symbolpkg.mspx#Windows%20symbol%20packages but I must need to get another one. Which one should I get (for XP)?
Thanks
#37
02/22/2004 (9:56 pm)
Here are the errors, hope this helps in which pack to get ;-)'torqueDemo.exe': Loaded 'C:\torque\example\torqueDemo.exe', No symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\ntdll.dll', No symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll', Symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\user32.dll', No symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\gdi32.dll', Symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll', Symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll', No symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\winmm.dll', Symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\wsock32.dll', Symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\ws2_32.dll', No symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\msvcrt.dll', Symbols loaded. 'torqueDemo.exe': Loaded 'C:\WINDOWS\system32\ws2help.dll', Symbols loaded. The program '[2996] torqueDemo.exe: Native' has exited with code 0 (0x0).Also, could someone just look in Project Properties at the path to the symbols? Is there any other path besides C:\WINDOWS\Symbols\DLL?
Torque 3D Owner Jason Nabors
I assume you didn't do a fresh download of the head and you are updating, and yes it does make a difference.