Torque3D Beta 1 Bug - Visual Studio solution files are Express ver
by Scott Burns · in Torque 3D Professional · 05/01/2009 (6:57 am) · 6 replies
This is something that isn't well known and I discovered back around 1.7 I think. The included Visual Studio solution files were created with an Express version, unfortunately this means that those solutions are locked into the features of the Express version.
Its an easy enough thing to fix for interim, all you have to do is open the solution file in a text editor and remove the Express references. However, GG really should include non-Express versions as that's going to become annoying thing to have to do fairly quickly.
I also just discovered that the solution files that are generated by the New Project Wizard are also Express versions.
Its an easy enough thing to fix for interim, all you have to do is open the solution file in a text editor and remove the Express references. However, GG really should include non-Express versions as that's going to become annoying thing to have to do fairly quickly.
I also just discovered that the solution files that are generated by the New Project Wizard are also Express versions.
#2
Out of curiosity, which feature(s) are you missing with the generated solution specifying Express?
05/01/2009 (10:58 am)
Hey Scott, doesn't changing this cause problems with Express being able to load the solutions? Most people are on the Express edition... If you save the solution from Standard/Pro does it change that line?Out of curiosity, which feature(s) are you missing with the generated solution specifying Express?
#3
The features that I know off the top of my head that are locked out in Express are the optimization features in Visual Studio.
Now if changing the solution version causes it not to load in Express, that I'm not sure of. I don't have an Express version installed anymore and I can't remember if me or Mich tested that case when we ran into the problem before.
05/01/2009 (11:14 am)
No, saving an Express solution does not change it to Standard/Pro, at least in 2005. Its possible this may have been fixed in 2008 but I don't have it to test against.The features that I know off the top of my head that are locked out in Express are the optimization features in Visual Studio.
Now if changing the solution version causes it not to load in Express, that I'm not sure of. I don't have an Express version installed anymore and I can't remember if me or Mich tested that case when we ran into the problem before.
#4
05/04/2009 (5:16 pm)
Logged for futher investigation.
#5
Visual Studio Standard/Pro will load a Visual Studio Express solution no problem. However, Visual Studio Express will not correctly load a Visual Studio Standard/Pro solution (it will usually prompt for you to select a Visual Studio Express product to open it with which gets annoying quick).
I just spent some time looking at this with a side-by-side comparison and I can't see any features that are disabled in a Visual Studio Express solution loaded into Standard/Pro. Can you point me at the setting/feature in the IDE that is disabled?
05/15/2009 (4:21 pm)
Quote:
Now if changing the solution version causes it not to load in Express, that I'm not sure of.
Visual Studio Standard/Pro will load a Visual Studio Express solution no problem. However, Visual Studio Express will not correctly load a Visual Studio Standard/Pro solution (it will usually prompt for you to select a Visual Studio Express product to open it with which gets annoying quick).
Quote:
this means that those solutions are locked into the features of the Express version
I just spent some time looking at this with a side-by-side comparison and I can't see any features that are disabled in a Visual Studio Express solution loaded into Standard/Pro. Can you point me at the setting/feature in the IDE that is disabled?
#6
Unfortunately I wasn't specific about the disabled features when I posted about it 2 years ago. I'll talk to Mich and see if he remembers exactly which optimization features it was.
05/15/2009 (5:38 pm)
I'll do some digging and see if I can figure out which ones they were, I just did a reinstall of Beta1 and the ones I thought were disabled seemed to be enabled but I may not be looking in the right spot.Unfortunately I wasn't specific about the disabled features when I posted about it 2 years ago. I'll talk to Mich and see if he remembers exactly which optimization features it was.
Associate Scott Burns
GG Alumni
In Tools\projectGenerator\templates\vc2k5_sln.tpl line 2 reads:
# Visual C++ Express 2005
it should be:
# Visual Studio 2005
The same would need to be done for vc2k8_sln.tpl as well.