Click here to Skip to main content
15,881,380 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi experts,

I have a project on my development machine (VisualStudio 2008 Standard) that is set to Debug|Any CPU. I copied it to the live machine (with other hardware, drivers, etc) that has Visual Studio 2008 Express installed.

The selector for Debug vs Release is grayed out, just like the one for Any CPU vs Konfigurations Manager.

On the live machine, I can no longer see the "Symbols for conditional compilation" (roughly translated from German) in the project's "Build" tab.

Therefore I cannot remove some symbols that need to be removed on the target machine.

What shall I do to get thos dropdowns populated and the configurations visible?
Posted

Visual Studio Express does not support all the features of the standard version so you will have problems moving this way. Your best option is to create a new empty project in the Express version and add your source modules into it manually.
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 15-Nov-12 10:36am    
Really?! Not even configurations? If so, could you tell me what happens to debug information options? Or maybe the debug information option is directly available, as well as optimization switch?

I'm not using Express version, but you see, many recommend using them to the people who cannot obtain full VS versions. If Express version merely lacks some tools, it would be fine, but configurations... If configuration cannot be modified, what the compilation does: always available debugging, or what? Or still there is a way to switch debugging/optimization on/off?
Could you explain if VS Express is fully usable in this respect or not?

(5 anyway, by the way; I guess you know what you say -- and Express limitations is not your fault :-)
--SA
Richard MacCutchan 15-Nov-12 11:10am    
I said Visual Studio Express does not support all the features of the standard version; so some parts of a project file may confuse it. I think they tried to fix this with VS2010 when they moved to XML based project files.
Sergey Alexandrovich Kryukov 15-Nov-12 11:17am    
You see, the project files themselves are universal (but different versions of Studio work with different versions of project schema, as you know) -- please see my answer.

So, a limited version of the VS (Express) can only disable some changes, but hardly change the way the project is built. (I'm not sure though; that's why I'm trying to ask you.) My worry is the ability to produce assemblies with debug info on/off, optimization on/off...
--SA
Richard MacCutchan 15-Nov-12 11:27am    
The project files are not universal, I came across this problem some time ago. The early Express version files were different from the standard version ones. As I say, I think they tried to fix this with 2010 by moving to XML based project files.
Sergey Alexandrovich Kryukov 15-Nov-12 13:26pm    
Thank you.

Interesting, could you please explain what do you mean? How they are different?

Actually, if they are different in content, this is not what I mean. The format and schema should be the same. Event Mono uses the same project files created by Studio, as well as MonoDevelop and SharpDevelop -- and visa versa. Well, if something is wrong here, it indeed can be a big problem. So, could you remember what was the problem and what kind of differences?
--SA
In addition to Solution 1:

If Visual Studio Express limitation is a critical issue (please see my comments to Solution 1: I'm not sure), you should understand that you can always build any project without Studio at all. As a matter of fact, Visual Studio itself does not build anything, it only provide input to the build system.

Everything needed for build is bundled not with Visual Studio, but with .NET Framework itself, which is freely distributed and is a re-distributable. At the very least, you always have C# and VB.NET compilers and build system (used via MSBuild) — for free. And this way of build has absolutely no limitations. Please see:
http://en.wikipedia.org/wiki/MSBuild[^],
http://msdn.microsoft.com/en-us/library/0k6kkbsd.aspx[^].

In case of critical problems, you can always learn the structure of project files and modify such file directly. I can only recommend it as a last resort. Also, you can build very custom project files to build anything at all, related to .NET or not. This build project language is purely declarative and very powerful. If you do it, you can develop very robust build system fully automating required configuration twists is a fully safe way (in particular, by passing custom options in command-line parameters of MSBuild), without touching the project files manually after they are developed and debugged. I could provide very good alternative project/solution maintenance.

—SA
 
Share this answer
 
Comments
lukeer 19-Nov-12 3:49am    
Thanks, those links may come handy some time.
For now, I've been pointed to a solution and posted it here.
Sergey Alexandrovich Kryukov 19-Nov-12 11:39am    
You are welcome.
--SA
Thanks to all that tried to help, but the solution this time was so much more profane: A collegue told me that there was a switch to activate in Express editions to enable configuration and platform dropdowns. See here[^].
Having those options hidden intentionally by default puzzles me.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900