Interesting. It's often the case that making things simpler for some
people makes them more complicated (and less predictable) for others :(
Yes.
I would have assumed "optimize code' would apply to JUST the release.
I mean, why would you want DEBUG code to be optimized? Ever?
Because "Debug" is just an arbitrary label, I believe. There's nothing
really magical about Debug and Release as build configurations, as far
as I know. You can create your own, call them what you want and tweak
them however you want.
I understand. But, it appears that this 'simplified' project settings
for Express editions make clear decisions based on Release or Debug,
meaning that they are not just labels -- not in this context. The
settings specifically apply to one or both. It's too bad it doesn't
tell you which. :)
When I turn ON "show advanced build configurations", it shows
"optimize code" ON for Release and OFF for Debug, which is what I
expect (although, I may be the author of those settings).
Disallowing certainly combinations based on the name would be quite odd
IMO as well as presenting some UI difficulties.
Yes, but, as the article states... this is what they desired. The
point being: for the beginner who comes into C# Express who just wants
to build Debug and Release and not worry -- that's who it's for. And
I've grown to like it because it's simple, but I dislike it because it
does things like optimizing code for Debug when I didn't want it to.
Zytan