Steve: is this simply creating the RoleModel.xml file correctly?
Before you gave me the above tip, I set the environment variable _CSPACK_FORCE_NOENCRYPT to true so Visual Studio would not encrypt the package and I also passed in the /noencrypt parameter to cspack. Using winmerge (http://winmerge.org/) – I
had just found out:
1) There were no issues of dependent 3rd party dlls – they were present in both packages.
2) The main difference seemed to be the “RoleModel.xml” file, which was empty on the tfs build version.
Marked As Answer byEmmanuel HunaThursday, October 07, 2010 7:23 PM