Printable View
http://blogs.msdn.com/blogfiles/sara...mage_thumb.png
I stumbled onto this while tooling around in the propertys of one of my projects.
I thought gave it a try just to see if there was any noticeable diffrence there wasn't but its a small project
I did however notice that i could no longer edit my code while debuging at runtime (like add comments or change values of strings)
So what is it exactly that this check box is supposed to do?
I believe that is used when you already need to deploy your application.
I guess. It just seems weird that it wouldn't do that for you already if it was thats simple
Without optimistions your code is compiled exactly as is. With optimisations enabled your code may be rearranged to remove redundancies and make memory usage and performance more optimal. That's why you can't edit the code while debugging: because what you see may not actually be what's getting executed.
Normally you disable optimisations while debugging and enable them when releasing. That is the default for the Debug and Release build configurations but if you add any new configurations of your own you'll have to decide which it's to be.
thats a great idea
How would you enable optimization for release and disable for debug automatically?
As JM said it should be the default when you build for Debug or Release, that said it should be automatic.