Activity overview
Latest activity by Seth
Already done, @RichardL. I'm actually waiting to hear back from support regarding the results of a test I performed at their request. Thanks! / comments
Already done, @RichardL. I'm actually waiting to hear back from support regarding the results of a test I performed at their request. Thanks!
And I forgot to attach the error log like I said I would. Here it is. / comments
And I forgot to attach the error log like I said I would. Here it is.
KeyNotFoundException during WPF resource merging
Our company has been using SmartAssembly for a few releases to obfuscate our applications for a while now. In our new release, we've run through many obfuscation tests and keep getting an exception...
Hi Jessica R, that did work. Thanks! / comments
Hi Jessica R, that did work. Thanks!
Apologies for the late response.
We figured out that doing the obfuscation after the IncrementalClean and before the PostBuild was the best fit for us. Otherwise, the resulting project file looks quite similar to the documentation.
Thanks! / comments
Apologies for the late response.
We figured out that doing the obfuscation after the IncrementalClean and before the PostBuild was the best fit for us. Otherwise, the resulting project file looks q...
Was there ever a resolution to this issue? I am experiencing a similar problem where many of the assemblies I'm obfuscating via MSBuild integration hit the "Cannot find assembly... Make sure it's in the GAC" error. I've also tried using relative and absolute paths, I'm on the latest version of SmartAssembly (6.11.1.433), and I've verified that the assembly that it's having issues finding (CrystalDecisions.CrystalReports.Engine) is in the GAC. / comments
Was there ever a resolution to this issue? I am experiencing a similar problem where many of the assemblies I'm obfuscating via MSBuild integration hit the "Cannot find assembly... Make sure it's i...
After much testing, it seems that the issue is the BusinessObject.Licensing.KeycodeDecoder.dll is not a .NET managed assembly, which means that SmartAssembly has difficulty (if not outright refusal) processing it. It also seems the two issues were related, since solving the first solved the second one.
We got around the issue by making all CrystalReports dlls referenced by our code to be ignored, via the "NotAvailable" <Assembly> attribute in the .saproj file. This causes the MSBuild to pass, and performing a clean/rebuild on the dll in Visual Studio before running the build in SA GUI removes the second issue. / comments
After much testing, it seems that the issue is the BusinessObject.Licensing.KeycodeDecoder.dll is not a .NET managed assembly, which means that SmartAssembly has difficulty (if not outright refusal...
Is it possible to obfuscate as part of PostBuild rather than AfterBuild?
We are currently obfuscating our dlls using MSBuild integration with the latest version of SmartAssembly (v6.11.1.433), as part of the AfterBuild target in the dll's csproj file. Many of our projec...
I am also curious about this, though from an MSBuild integration stand point. Is this at all possible? / comments
I am also curious about this, though from an MSBuild integration stand point. Is this at all possible?
Because we have decided to obfuscate each assembly independent of the application that uses it, I believe we won't hit issues 2 and 3 anyway, no merging or embedding needed. Thanks for the response! / comments
Because we have decided to obfuscate each assembly independent of the application that uses it, I believe we won't hit issues 2 and 3 anyway, no merging or embedding needed. Thanks for the response!