DLL comparison after daily build

[Depechie]

Hey guys,

I'm stuck with something difficult... I would like to know if an
assembly has changed between 2 versions.

Little bit of detail... we have a daily build pc that will build all
projects and increases the build number. So when I do a binairy
compare of the output dll's they are different ! But it could be that
the original code base was exact the same as the day before... So any
way to tell if the code has actually changed while comparing 2
assemblies ?

Thanks for any advice
Glenn

 

[Michael Nemtsev [MVP]]

Hello Depechie,

I'd use the .NETReflector or ILDASM to disasemble it, extract the IL code
and compare the content

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


D> Hey guys,
D>
D> I'm stuck with something difficult... I would like to know if an
D> assembly has changed between 2 versions.
D>
D> Little bit of detail... we have a daily build pc that will build all
D> projects and increases the build number. So when I do a binairy
D> compare of the output dll's they are different ! But it could be that
D> the original code base was exact the same as the day before... So any
D> way to tell if the code has actually changed while comparing 2
D> assemblies ?
D>
D> Thanks for any advice
D> Glenn

 

[Depechie]

Hello Depechie,

I'd use the .NETReflector or ILDASM to disasemble it, extract the IL code
and compare the content

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

D> Hey guys,
D>
D> I'm stuck with something difficult... I would like to know if an
D> assembly has changed between 2 versions.
D>
D> Little bit of detail... we have a daily build pc that will build all
D> projects and increases the build number. So when I do a binairy
D> compare of the output dll's they are different ! But it could be that
D> the original code base was exact the same as the day before... So any
D> way to tell if the code has actually changed while comparing 2
D> assemblies ?
D>
D> Thanks for any advice
D> Glenn

Nice suggestion !
But a hard one... because the disassembler will not give an overall
overview. In other words I'll have to check each function manually.
Or is there an add in for Reflector that does this ?

 

[Michael Nemtsev [MVP]]

Hello Depechie,

see Addins page http://www.codeplex.com/reflectoraddins
"Diff" plugin

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

Hello Depechie,

I'd use the .NETReflector or ILDASM to disasemble it, extract the IL
code and compare the content

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

D> Hey guys,
D>
D> I'm stuck with something difficult... I would like to know if an
D> assembly has changed between 2 versions.
D>
D> Little bit of detail... we have a daily build pc that will build
all
D> projects and increases the build number. So when I do a binairy
D> compare of the output dll's they are different ! But it could be
that
D> the original code base was exact the same as the day before... So
any
D> way to tell if the code has actually changed while comparing 2
D> assemblies ?
D>
D> Thanks for any advice
D> Glenn

D> Nice suggestion !
D> But a hard one... because the disassembler will not give an overall
D> overview. In other words I'll have to check each function manually.
D> Or is there an add in for Reflector that does this

 

[Depechie]

Hello Depechie,

see Addins pagehttp://www.codeplex.com/reflectoraddins
"Diff" plugin

---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

Hello Depechie,
I'd use the .NETReflector or ILDASM to disasemble it, extract the IL
code and compare the content
---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog:http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo
D> Hey guys,
D>
D> I'm stuck with something difficult... I would like to know if an
D> assembly has changed between 2 versions.
D>
D> Little bit of detail... we have a daily build pc that will build
all
D> projects and increases the build number. So when I do a binairy
D> compare of the output dll's they are different ! But it could be
that
D> the original code base was exact the same as the day before... So
any
D> way to tell if the code has actually changed while comparing 2
D> assemblies ?
D>
D> Thanks for any advice
D> Glenn

D> Nice suggestion !
D> But a hard one... because the disassembler will not give an overall
D> overview. In other words I'll have to check each function manually.
D> Or is there an add in for Reflector that does this ?

Hey Michael,

Thanks and yes that is the one I was already testing
But like I said it requires me to go through all code, would be nice
to get a generated overview automatically !

I'll write an email to the writer of the add in for more detail.
Thanks again Michael for the fast reply !!

Greets
Glenn

 

[Andrew Faust]

Doesn't your source code repository give you the ability to see if the
source files were changed between the previous day and the current day?