469,271 Members | 1,324 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,271 developers. It's quick & easy.

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?
Jul 19 '05 #1
2 3002
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

--
Ed Smith, VBQA Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "nfr" <nf*@nospam.com>
Subject: Confused about build directories -- defaults different in C# and Visual Basic.NET
Date: Tue, 15 Jul 2003 09:52:29 -0700
Lines: 16
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <#1**************@tk2msftngp13.phx.gbl>
Newsgroups: microsoft.public.dotnet.general
NNTP-Posting-Host: adsl-216-101-221-60.dsl.lsan03.pacbell.net 216.101.221.60
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftn gp13.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:101227
X-Tomcat-NG: microsoft.public.dotnet.general

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?

Jul 19 '05 #2
nfr
"Ed Smith[msft]" <ed*****@online.microsoft.com> wrote in message
news:Rg**************@cpmsftngxa06.phx.gbl...
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.
Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

14 posts views Thread by Giovanni Bajo | last post: by
12 posts views Thread by Dr. Zharkov | last post: by
12 posts views Thread by David Murmann | last post: by
5 posts views Thread by maggie.nguyen | last post: by
7 posts views Thread by Leszek L. | last post: by
3 posts views Thread by =?Utf-8?B?Rmxhc2hwcm8=?= | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.