CODEWITHSUNDEEP
.netassembliesversion
Ant
Ant

Reputation: 3459

.NET Assembly Version

The scenario is as follows. Developers compile the projects and deploy assemblies to production. eg, deployment contains 10 assemblies. Out of 10, they actually change the source code only in 5 assemblies and they recompile other 5 assemblies without changing the source code. Before deployment, I want to trace which assemblies are actually changing and which are just recompiling. I can add version info or something in the project or build process. I can also access assemblies of previous build. But this process must be automated.
Thanks,
Ant.

Upvotes: 0

Views: 483

Answers (1)

arbiter
arbiter

Reputation: 9575

You can convert both (previous and current) assemblies pdbs to xml (because pdb files for just recompiled source will differ) and binary (or ascii) compare them. If source was not changed then xml files will be the same.

Converting a managed PDB into a XML file.

Using this (not ideal, but anyway) approach you can fully automate changed source detection.

Upvotes: 2

Related Questions