471,337 Members | 888 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,337 software developers and data experts.

Serious Batch Build Bug!!

If I rebuild all my projects (for each configuration: debug & release)
using batch build, the WRONG referrenced DLLs are copied into the bin
folder for the main project.

If I do a batch build, I expect the RELEASE versions of my referenced
projects to be in the RELEASE bin folder of my main project, however,
if the configuration dropdown in my toolbar says DEBUG, then the DEBUG
versions will be copied to the RELEASE bin folder.

Likewise, if RELEASE is selected in the dropdown, the RELEASE versions
of the reference DLLs are put into the DEBUG bin folder.

This is a very serious problem. Am I doing something else wrong?

Is this a known bug?

Thanks!

Dec 6 '05 #1
3 1577
Can you zip up a solution which the rest of us can use to confirm this?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"GoogleNewsReaderMan" <lo***********@hotmail.com> wrote in message
news:11*********************@g49g2000cwa.googlegro ups.com...
If I rebuild all my projects (for each configuration: debug & release)
using batch build, the WRONG referrenced DLLs are copied into the bin
folder for the main project.

If I do a batch build, I expect the RELEASE versions of my referenced
projects to be in the RELEASE bin folder of my main project, however,
if the configuration dropdown in my toolbar says DEBUG, then the DEBUG
versions will be copied to the RELEASE bin folder.

Likewise, if RELEASE is selected in the dropdown, the RELEASE versions
of the reference DLLs are put into the DEBUG bin folder.

This is a very serious problem. Am I doing something else wrong?

Is this a known bug?

Thanks!

Dec 6 '05 #2
Unfortunately, I can't attach anything. However, I really appreciate
your help.
If you currently have a solution with a windows app and at least one
other class library project, you can easily test this with your own
stuff.
Just put something like what I typed below into a class defined in a
supporting class library and call it from your windows app and show in
a message box. (Try simply running the debug config, then run the
release config. Then set the config to whichever and do a batch buld
and rebuild all -- then go directly to the output folders and run the
windows app from there. You will see that the supporting DLLs will all
be based on the dropdown.)
I'd really appreciate hearing what you find. Thanks!!!

public static string GetVersion()
{
#if DEBUG
return "Debug";
#else
return "Release";
#endif
}

Dec 6 '05 #3
No takers??!!

Okay... let me make it even easier for those at home to see this
problem.

You should be able to do this with any solution that has multiple
projects.

Start by "cleaning" --- select batch build and select all and click
clean.
Now, from the configuration dropdown, select either debug or release.
Then do a batch build, but select all projects with the opposite of the
dropdown selection. (i.e. if you picked debug from the dropdown, in
batch build, select all release projects). Do a rebuild from this
dialog.

You should see errors as the build tries to use the wrong DLLs -- and
you'll probably end up with nothing in the bin folder.

Try it, please.

Dec 7 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by Tim | last post: by
reply views Thread by Lynn Gasch | last post: by
5 posts views Thread by Colonel Kernel | last post: by
reply views Thread by Ioannis Vranos | last post: by
5 posts views Thread by David++ | last post: by
3 posts views Thread by Floris van Haaster | last post: by
reply views Thread by cmk128 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.