This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 83%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
I am developing a Solution with a good few VB.NET projects in it.
In the x86 and x64 configurations I have made sure that "Enable Optimizations" is checked in the Release configuration and unchecked in the Debug configuration.
In the AnyCPU configurations, however, it doesn't seem to be able to have different settings between the Release and Debug configuration. When I check the checkbox, it will show as checked both in the Release and Debug configuration. When I uncheck it, it will show as unchecked in both.
This wouldn't be a big deal as I could just as easily debug the software in an x86 or an x64 configuration, except for the fact that the software is using Add-In Express and it MUST be built for AnyCPU.
Is this a known bug? Can it be addressed? Am using Visual Studio 2019 and keeping it up to date.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hi @Pino Carafa , did you match and choose the Active(Debug) and Active(Release) when you changing the Configurations?
I didn't, but even when I do the settings don't persist.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
When you go to the Compile tab and change the Configuration you are switching to the settings for that configuration so you can edit them, it doesn't impact which configuration the build is using. This is simply giving you access to the settings to change, it doesn't have any impact on the build. To change which configuration you are building you have to use the combo at the top. That allows you to bounce back and forth between configurations to build. Depending upon which configuration you are building (from the toolbar) the compiler uses the settings defined by the corresponding configuration in the Compile tab of the project properties.
In your example you're looking at the Release configuration settings but you're building in Debug. The only issue I see is that the project UI isn't properly reflecting the active configuration when you reopen it. That is a minor issue that has no effective on what is used during build.
I'll also mention it might not even be a bug. The toolbar is selecting the solution configuration to build, not the project configuration. It is common to have a single solution configuration that builds different configurations on a per-project level. It is possible in this solution your Debug solution configuration builds the Release configuration of your project. To view this information right click the solution in Solution Explorer and select Configuration Manager. In this dialog you can see what solution configuration/platforms are defined and for each one what projects will and won't be built and what configuration/platform they will be using.
Sure, but in my x86 and x64 configurations it keeps whatever I selected when I save the Solution. The next time I go to that Solution configuration the project configurations are presented as they were the last time I saved the solution in that Configuration. Except when I pick the AnyCPU configuration. Then it seems to save the solution configuration as if "Debug" and "Release" are identical. Regardless whether I open Debug or Release, it shows me the last project configuration I saved.
Open the project file and verify the configuration are correct. Again I think this is just a UI issue in the project properties. You can verify the build is using the right settings via a decompiler to verify the release build is generating optimizations.
Ok guess who feels like a complete eejit right now? THIS GUY -->SELF
I just realised where I'm messing up.
Why do you believe the settings are the same? I created a quick VB console app in 16.8.4 and the Debug configuration does not enable optimizations and the Release configuration does as I would expect. Decompiling the generated code for both debug and release builds indicates the assembly has the appropriate optimization flags set for the JIT when it runs later on.
I accepted @Michael Taylor earlier answers but the real "aha" moment came when I was looking at his or her comments on @Tianyu Sun-MSFT 's earlier answer.