[Resolved] Any Success Using Visual Studio 2010?
by Charlie Patterson · in Torque 2D Beginner · 05/24/2013 (8:22 am) · 3 replies
Before I dig deep I wanted see if anyone else has run into this. I don't normally use VS2010.
Quick Version:
I'm using Visual Studio 2010 Express on Win7. I load the VS2010 solution and build. When I try to run T2D ("development" branch if it matters), I get no window and it exits quickly.
More Thorough Version:
The compile phase seems fine. It says something about "alwaysCreate" mode, which I don't know anything about at this point.
Then when I try to run T2D from within VS2010 it always says "the program is out of date, would you like to build it?" so I say yes. It asks this even if I click run twice in a row. That is, even if I didn't rebuild it and get the "alwaysCreate" stuff.
Once the program runs, I see no Window. The following is in the output window (clipped for size):
[code]
'Torque2D_DEBUG.exe': Loaded 'C:UserscharliepDocumentsprjTorque MITTorque2DTorque2D_DEBUG.exe', Symbols loaded.
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64ntdll.dll', Cannot find or open the PDB file
...
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64oleaut32.dll', Cannot find or open the PDB file
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64dwmapi.dll', Cannot find or open the PDB file
--------------------------------------------------------------------------------
Processor Initialization:
AMD (unknown), ~3.53 Ghz
(timed at roughly 3.52 Ghz)
FPU detected
MMX detected
3DNow detected
SSE detected
--------------------------------------------------------------------------------
Math Initialization:
Installing Standard C extensions
Installing Assembly extensions
Installing FPU extensions
Installing MMX extensions
Installing 3DNow extensions
Installing SSE extensions
--------------------------------------------------------------------------------
Input Initialization:
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64dinput8.dll', Cannot find or open the PDB file
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64hid.dll', Cannot find or open the PDB file
...
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64Wldap32.dll', Cannot find or open the PDB file
DirectInput enabled.
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64dinput8.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64setupapi.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64devobj.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64hid.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64winmm.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64cfgmgr32.dll'
The thread 'Win32 Thread' (0x264c) has exited with code 0 (0x0).
The program '[6988] Torque2D_DEBUG.exe: Native' has exited with code 0 (0x0).
[/endcode]
Anyone else seen this?
Quick Version:
I'm using Visual Studio 2010 Express on Win7. I load the VS2010 solution and build. When I try to run T2D ("development" branch if it matters), I get no window and it exits quickly.
More Thorough Version:
The compile phase seems fine. It says something about "alwaysCreate" mode, which I don't know anything about at this point.
Then when I try to run T2D from within VS2010 it always says "the program is out of date, would you like to build it?" so I say yes. It asks this even if I click run twice in a row. That is, even if I didn't rebuild it and get the "alwaysCreate" stuff.
Once the program runs, I see no Window. The following is in the output window (clipped for size):
[code]
'Torque2D_DEBUG.exe': Loaded 'C:UserscharliepDocumentsprjTorque MITTorque2DTorque2D_DEBUG.exe', Symbols loaded.
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64ntdll.dll', Cannot find or open the PDB file
...
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64oleaut32.dll', Cannot find or open the PDB file
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64dwmapi.dll', Cannot find or open the PDB file
--------------------------------------------------------------------------------
Processor Initialization:
AMD (unknown), ~3.53 Ghz
(timed at roughly 3.52 Ghz)
FPU detected
MMX detected
3DNow detected
SSE detected
--------------------------------------------------------------------------------
Math Initialization:
Installing Standard C extensions
Installing Assembly extensions
Installing FPU extensions
Installing MMX extensions
Installing 3DNow extensions
Installing SSE extensions
--------------------------------------------------------------------------------
Input Initialization:
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64dinput8.dll', Cannot find or open the PDB file
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64hid.dll', Cannot find or open the PDB file
...
'Torque2D_DEBUG.exe': Loaded 'C:WindowsSysWOW64Wldap32.dll', Cannot find or open the PDB file
DirectInput enabled.
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64dinput8.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64setupapi.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64devobj.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64hid.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64winmm.dll'
'Torque2D_DEBUG.exe': Unloaded 'C:WindowsSysWOW64cfgmgr32.dll'
The thread 'Win32 Thread' (0x264c) has exited with code 0 (0x0).
The program '[6988] Torque2D_DEBUG.exe: Native' has exited with code 0 (0x0).
[/endcode]
Anyone else seen this?
#2
However, ultimately it allows you to test changes across multiple script projects pretty easily without having to copy-paste the .exe's around.
05/24/2013 (4:25 pm)
Yeah, it's kind of a pain at first to have to set your Working directory to your work directory. I think a wise old sage once mentioned that this is part of user settings and cannot be shipped with the solution.However, ultimately it allows you to test changes across multiple script projects pretty easily without having to copy-paste the .exe's around.
#3
05/25/2013 (3:55 pm)
Doesn't T3D manage to set it automatically somehow? Unless the project generator generates user files as well.
Associate Charlie Patterson
Default Studio Name
So you have to right click on Torque2D in the "Solution Explorer" and go to the debugging tab. Then set the working directory to ../../..
I knew that.