Problem when trying to resolve a dependency using SearchPath.
We are using Smart Assembly 7 to obfuscate a .Net Standard assembly. When we try to resolve a .Net Standard dependency, the tool is not able to find nestandard.dll 2.0. Using Smart Assembly 6.13 we resolved this dependency by adding a new SearchPath entry to the configuration file.
In Smart Assembly 7, we have checked that a new SearchPath element is added in the settings file when we use the option "Add a new search path" from the GUI, but this does not seem to be working to solve the dependency and the interface keeps asking us to provide other paths to find the missing assembly. This doesn't work either if we try to create the project for the assembly from the command line.
On the contrary, if we use the option "Browse" in the GUI and select the assembly to load from the same path we set using SearchPath, the dependency is solved Ok and we can complete the obfuscation process without further issues.
Our idea is to provide the extra search paths just once, and then use the command line each time we need to obfuscate a new version of our assemblies. For this reason, using the option "Browse" is not a valid solution for us. Is there anything we can try to get this working?
0 · Share on Twitter