Cannot get VS2010 to compile release version

[!NoItAll]

I just updated to VS2010 SP1, but I cannot be certain this problem didn't exist prior to the update.
When I build my project the version in /bin/debug builds, but nothing builds in /bin/release. I do not remember making any changes that would affect this, but nothing I do now will get the release version to build.
In the Application settings under "Compile" I have Configuration set to Release and the Build output path is "bin\Release\
For Debug I also have Configuration set to Release.
There doesn't seem to be anything else left to change/adjust - but no matter what I seem to do nothing builds in the bin/release folder.
I'm pulling my hair out...

[!NoItAll]

Well - there appears to be some new behavior with VB.NET in VS2010 SP1.
Previous to SP1 whenever I built my project it would build BOTH the debug and release versions. After talking to some C# friends this was apparently unique to VB.NET.
Now - with SP1 VB behaves the way C# does and you have to use the configuration manager to work in either debug or release mode. It appears you can no longer do both at the same time.
As in C# you work on the project in debug mode and when you are ready to do an actual release build you open the Configuration Manager (menu Build --> Configuration Manager) and switch to Release mode and do a build.
By default the debug version is built in ..\bin\debug and the release version is built in ..\bin\release.
You can add an easy shortcut to your toolbar to quickly switch back and forth from debug to release. This shortcut seems to be a default setting in C#, but in VB you have to go through several steps to manually get it on the tool bar.
Rant: So if MS went to all the trouble to make VB more consistent with C# then why on earth did they not automatically add this shortcut to the VB default toolbar? It took me nearly half a day to work through this issue. What a crock!
Also - I notice now that the debug and release versions are built in both locations (..\bin\debug & ..\bin\release). That's odd and appears that MS goofed up on this. I'm kinda thinking that this may be more of a bug now then a purposeful change...