How can we help you today? How can we help you today?
PatrickG
Activity overview Badges (0) Posts (0) Comments (2)

Activity overview

Latest activity by PatrickG

Hi Jessica R, thanks for your answer and I am glad you could reproduce it! Sounds great, thanks for the workaround, but this is a temporary solution. It would be of course really nice if this bug is fixed in the next version of SA. (Note: Thanks for the tip, we will look at this.) This POST could be closed, but it would be really nice if you could update the post as soon as the new bug fixed version of SA is released. Thanks, Patrick / comments
  1. Community
  2. SmartAssembly
  3. When already strong named my assemly, SA says it is not the same strong name
Hi Jessica R, thanks for your answer and I am glad you could reproduce it! Sounds great, thanks for the workaround, but this is a temporary solution. It would be of course really nice if this bug i...
0 votes
Hi @Jessica R, thanks for your answer! My mistake, just with the signing by Visual Studio the message will not appear. So, it must be the ILMerge: We have included in the .csproj file a MSBuild task which does the expected work with ILMerge. We use following NuGet package for that: https://github.com/wade/ILMerge.Tools The ILMerge.exe version what we are using comes also with a NuGet package: https://www.nuget.org/packages/ILMerge.Tools/2.14.1208/ Our task is executed in a target with attribute BeforeTargets="CopyFilesToOutputDirectory": <ILMergeTool InputAssemblies="@(ILMergeInputAssemblies)&quot; OutputFile="obj\$(AssemblyName).dll" KeyFile="$(SolutionDir)Resources\Strong Name\my.snk" SearchDirectories="@(ILMergeSearchDirectories)&quot; LogFile="..\ILMerge.log" Internalize="True" Closed="True" AllowDuplicateTypeNames="True" TargetPlatformVersion="4" TargetPlatformDirectory="C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0" ToolPath="$(SolutionDir)packages\ILMerge.Tools.2.14.1208\tools\ILMerge.exe" /> See this screenshot, what I mean that the target assembly shows the Public Key instead of the token: [image] Thanks, Patrick / comments
  1. Community
  2. SmartAssembly
  3. When already strong named my assemly, SA says it is not the same strong name
Hi @Jessica R, thanks for your answer! My mistake, just with the signing by Visual Studio the message will not appear. So, it must be the ILMerge: We have included in the .csproj file a MSBuild tas...
0 votes
Total activity
3
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1