Team System Developer Center >
Visual Studio Team System Forums
>
Team Foundation Server - Build Automation
>
CI Build is not creating DLL with strong name
CI Build is not creating DLL with strong name
- Hi,
I have created CI Build which runs at every hour.
In the Build, My last project is "Install.sln" which is WIX Project.
On compiling of "Install.sln", It gives me the following errors.
C:\BuildDir\Sources\Install\ABC\Feature\aaa1.wxs(25,0): error LGHT0282: Assembly C:\Workspace\Sources\BinDir\<<DLL NAME>>.dll in component TEMP1_ENTITY has no strong name and has been marked to be placed in the GAC. All assemblies installed to the GAC must have a valid strong name.
C:\BuildDir\Sources\Install\XYZ\Features\bbb1.wxs(18,0): error LGHT0282: Assembly C:\Workspace\Sources\BinDir\<DLL NAME>.dll in component TEMP2_ENTITY has no strong name and has been marked to be placed in the GAC. All assemblies installed to the GAC must have a valid strong name.
------------
<?define ASSEMBLIES="..\..\BinDir"?>
<Component Id="TEMP1_ENTITY " DiskId="1" Guid="{544F3455-6TG8-45qw-ST6G-88FR62TRU9C5}">
<File Id="PROJECTA_ENTITY" Source="$(var.ASSEMBLIES)\<dllname>.dll"
KeyPath="yes" Vital="yes" Checksum="yes" Assembly=".net" />
</Component>
--------------------
So to investigate, I checked in the "BinDir" where I found the dll which are not sign with strong name.So, I opened the Bin Directory of the corresponding project, Dll is created without strong name.
So, I open the project from the "BuildDir\Source\Projects\PROJECTA.sln" and run the project manually, this time dll is created with strong name.
If anybody has idea then let me know because I am facing this error from last 3 weeks :(.
Regards
Hiren Patel
Answers
- Finally got solutions :).
In my .rsp file I was using parameter SignAssembly=True, I just remove this parameter and tried to build and it's working fine.
Hiren Patel- Marked As Answer byHirenPatel Monday, November 09, 2009 3:50 AM
All Replies
Hi,
Thanks,
It may be posible that the settings for the build are different from the ones you used to build it locally (e.g. it compiles Release on the server, but you did a Debug build on the client). Hence, I would make sure the configuration the server is using is properly set-up to strong sign. Another item to check is that the key file used for signing is checked-in TFS, so it is available on the build server.
Alin,
PRAKTIK Consulting
TFS Hosting and TFS Consulting Services.- Hi Alin,
I have checked once again it's Compiles Release on the server and Key file is already checked in TFS
Regards,
Hiren Patel - Finally got solutions :).
In my .rsp file I was using parameter SignAssembly=True, I just remove this parameter and tried to build and it's working fine.
Hiren Patel- Marked As Answer byHirenPatel Monday, November 09, 2009 3:50 AM


