Is there any way of finding out the difference between two wsp files that are created using the package option in visual studio, including the parameters like the change-set version , check-in and label details in VS 2010.

I have actually created two wsp files for the prod and pre-prod environment but wanted to ensure that they are ideally the same files created at different dates.

  • No metadata about TFS is saved in the WSP when it is compiled. Those details aren't even stored on the file system, all of that is only held on the TFS server.
    – James Love
    Jan 13, 2016 at 6:42

3 Answers 3


Your point is actually about comparing two binary files.

First, obviously, you can compare exact size of the files: if they don't match, you know they're different.

But the best would be to use any binary file comparator, like seen in https://stackoverflow.com/questions/8166697/tool-for-comparing-2-binary-files-in-windows. That would immediately tell you if the file are the same or not.

If they are different, to spot actual differences, you can rename your .WSP files as .CAB, extract their content, and compare the contents with a folder comparison tool.

  • Hi Evariste, I tried the file comparison using the beyond comparison software but still not able to get the expected difference like the changeset associated with the wsp, it only show the file version and size which are all the same expect for the date in which it is modified..
    – Arvind Raj
    Jan 12, 2016 at 19:19
  • 1
    A WSP is kind of a compiled file... No chance you can get from it code-source relates details like comments or change-set.
    – Evariste
    Jan 12, 2016 at 21:57
  • Yes Evariste converting to CAB and then disassembling and comparing the binary (dll) file seems to be the best method here. It is also clearly depicted in the following Microsoft link. ( social.technet.microsoft.com/wiki/contents/articles/… )
    – Arvind Raj
    Sep 5, 2016 at 15:12

How about you rename the two .wsp files to be .cab files, extract all contents by "extract all" or double clicking in Explorer, selecting all files, and copying them to another directory, and then using a tool like Beyond Compare to compare all the files?


Yes I accept your fact Evariste , I also checked around for some of the tools that can perform the comparison of the files but they too compare only the size of the file and other parameters that visible to normal eye (physical props of the file), what I literally wanted is to disassemble the wsp file and get the details required, so it seems it is not possible now :) .

Ideal Roundabout:

So the Ideal roundabout in this scenario would be to go with trial and error of the deployment of the wsp.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.