Is old assembly Oxygene fault or msbuild?

Elements Oxygene
1

I have a solution with 55 projects. There are 5 main programs. There are, as an example, two program projects that reference the same project. I made a change to the referenced project’s source code. I did a Build. One program’s bin folder contained the new version of the referenced assembly. The other, did not.

I checked that all projects are being compiled in the configuration. I checked that both program projects had dependencies on the referenced assembly. Everything looked good.

There was actually more than one assembly that was not updated in the bad project bin folder. I went into the referenced project’s code and changed something. Then I recompiled with Build again. Now, both referenced assemblies have the correct new versions.

Was this an MSBuild problem? Something off with Oxygene compiler? Something else?

The only fly in the ointment that confuses the situation is that when it was bad, it was probably an older version of Oxygene. Yesterday, PROBABLY before updating the compiler, was when the old assemblies were being left in the folder. So I’m not sure if just compiling with the new compiler version fixed things, or it was something else.

Unfortunately, I’m not sure when I did the install of the new version and when I had the bad files.

Any clues? Anyone else ever have such a thing happen?

2

I’ve never had that (when the project was actually set to build); yes msbuild does this, but it does a (time) compare of all input, including the compiler target (so updating the compiler forces a rebuild), to the target executable. Do you still have the log ?

3

I didn’t even know there WAS a log. I probably don’t have it from when it was bad. Where would it be and what is it called? (for future reference)

4

msbuild logging is off by default. It would require enabling it & setting it to Diagnostic output, then copy/pasting the stuff in Output so you won’t have that. But if it happens again that info will be useful.