Comments
3 comments
-
Hello tcberry_oxinst,
That's puzzling, 8.2 should have addressed that, it did for other customers with this issue.
When you say .NET SDK project format, is that in place of the MSbuild format? -
We still see this problem with the 8.3 release of SmartAssembly. It usually seems to happen when multiple assemblies are being processed towards the end of the build.
By .NET SDK format project, I mean the new project schema that was first introduced for .NET Core, the one that usually starts with <Project Sdk="Microsoft.NET.Sdk">. We are using this for our .NET Framework 4.8 projects in addition to those that target newer .NET releases.
-
Thanks for clarifying, I don't know if we've tested the .NET SDK format project with parallel assembly processing, I know we did for MSbuild.
We solved the parallel processing issue there by instantiating multiple instances of CLRTools so it didn't block itself. Based on your error message, that's clearly not occurring here for some reason.
As a quick fix, yes removing the parallel builds should allow you to proceed.
Add comment
Please sign in to leave a comment.
We have occasionally seen the same error with our existing codebase, but it seems much worse when using the .NET SDK project format.
We are currently using SmartAssembly 8.1, but the same issue happened when I tried updating to 8.2. Obfuscating an assembly with the SmartAssembly GUI does not produce this error.