Confused about build directories -- defaults different in C# and Visual Basic.NET

[nfr]

Default build directories seem to be somewhat different between C# and
Visual Basic.NET. Both have "Debug" and "Release" directories under "obj".
However, Visual Studio.NET defaults to a single "bin" directory whereas C#
appears to duplicate the "Debug"/"Release" pattern under bin.

This is creating problems for me in regards to browsed "References" added to
a project. With C# I need to pick one, which is going to be bin/Debug during
development, and then change it to bin/Release when compiling the entire
solution as a Release version.

It seems that having a single bin directory with no subfolders for
Debug/Release would be more flexible.

Am I wrong?

 

[Ed Smith[msft]]

If you would like to build to the same directory in C#, you can change the output path project property in the project properties dialog's build page (you will need
tro change in for both configurations).

Hope this helps;
-Ed

 

[nfr]

If you would like to build to the same directory in C#, you can change the

output path project property in the project properties dialog's build page
(you will need

tro change in for both configurations).

I realize that, but two things:

1. I'd rather change the default on this so that when I create a new project
I don't need to remember to go in and modify the bin build directories.
2. The pros/cons of one vs. the other insofar as C# and VB handle it
differently. My inclination is to think the VB approach makes more sense,
but would like to know if there are issues I haven't considered that
contributed to the difference.