How to order builds?

[Brett Romero]

I'm using a custom Configuration to build four of eight projects under
the same solution. For this configuration (call it ConfigA), I have
the four projects set to build. However, the order is important. When
I update a DLL that happens to start with the letter "u", the EXE,
which happens to build first and depends on the DLL, never gets this
update.

I'm not using project dependencies. Everything is via file reference.
Is there a way to set the build order for this configuration?

Thanks,
Brett

[rmacias]

If you link your assemblies by project, you will see a new option when you
right click on your solution from your Solution explorer. A new option will
appear called "Build Order . . .". This will let you set the build order.
Since you are not refencing them by project, and not by file, the "Build
Order" option will not be present when you right click on your solution.

Is there any reason why you are referencing the file, and not the project?
In my experience, doing it by file causes issues, especially if you are
still developing it.

"Brett Romero" wrote:

I'm using a custom Configuration to build four of eight projects under
the same solution. For this configuration (call it ConfigA), I have
the four projects set to build. However, the order is important. When
I update a DLL that happens to start with the letter "u", the EXE,
which happens to build first and depends on the DLL, never gets this
update.

I'm not using project dependencies. Everything is via file reference.
Is there a way to set the build order for this configuration?

Thanks,
Brett

[Brett Romero]

Because these DLLs may or may not go along with the EXE. They are
generic and work with many EXEs. That's why I'm doing it by file.
When I deploy, I want the EXE to reference a DLL file, not a project.

Perhaps I misunderstand how that works. What is the difference in
referencing by file and project post development (or deployment wise)?

Thanks,
Brett

[rmacias]

It doesn't matter when you deploy your EXE. Whether you reference the file
directly, or the Project (which eventually references the dll file), it is
still referenced the same.

Add the DLL the project to your solution. Then on your EXE project, right
click and then click on "Add Reference". Choose the "Projects" tab and then
add the DLL project to your references. This will not affect your
deployment, because ultimately, it is referencing the *.dll file after you
compile. The only difference is that your DLL will get compiled AND you will
be able to set the build order, which was your question.

"Brett Romero" wrote:

Because these DLLs may or may not go along with the EXE. They are
generic and work with many EXEs. That's why I'm doing it by file.
When I deploy, I want the EXE to reference a DLL file, not a project.

Perhaps I misunderstand how that works. What is the difference in
referencing by file and project post development (or deployment wise)?

Thanks,
Brett