Comments
Sort by recent activity
WARNING WARNING WARNING Although this works , having the core framework paths in the search path will screw up subsequent DotNet Framwwork builds in a BAD way. DNF builds complete without warnings but the application will not run and will crash silently on startup due to missing references to version 6 DLL's on client machines. Needless to say, this will really ruin your day if you deploy both Net6 and DNF applications and you must manually alter the reference paths -- ie remove NET6 reference paths from smartassembly before obfuscating Ditnet framwork applications. note that the SA Configuration for search paths is kept in "C:\ProgramData\Red Gate\SmartAssembly 8\SmartAssembly.settings" / comments
WARNING WARNING WARNING Although this works , having the core framework paths in the search path will screw up subsequent DotNet Framwwork builds in a BAD way.DNF builds complete without warnings...
Followup : I found this file 'WinFormsApp1.runtimeconfig.json' in the output folder along with the dll ?? may be of use contents {
"runtimeOptions": {
"tfm": "net6.0",
"frameworks": [
{
"name": "Microsoft.NETCore.App",
"version": "6.0.0-rc.1.21451.13"
},
{
"name": "Microsoft.WindowsDesktop.App",
"version": "6.0.0-rc.1.21451.3"
}
],
"configProperties": {
"System.Reflection.Metadata.MetadataUpdater.IsSupported": false
}
}
} / comments
Followup : I found this file 'WinFormsApp1.runtimeconfig.json' in the output folder along with the dll ?? may be of use contents{
"runtimeOptions": {
"tfm": "net6.0",
"frameworks": [
...
OK. hacking in to this Pointed the UI at dll in the obj folder not bin folder SA UI then complained about not able to find dependencies added these dll search paths (dont point to individual files) C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\6.0.0-rc.1.21451.3 C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.0-rc.1.21451.13 can now obfuscate a basic forms app with smartassembly note that the SA Configuration for search paths is kept in "C:\ProgramData\Red Gate\SmartAssembly 8\SmartAssembly.settings"
/ comments
OK. hacking in to thisPointed the UI at dll in the obj folder not bin folderSA UI then complained about not able to find dependenciesadded these dll search paths (dont point to individual files)C:\...
I found that the path from my "SetEnv.cmd" did not include C:\Program Files\Microsoft SDKs\Windows\v7.0A only C:\Program Files\Microsoft SDKs\Windows\v7.1 which somehow did not contain resgen.exe. So in effect the resources were never compiled into the final assemblies.
Interestingly when build with VS it was OK, so only commandline builds failed. / comments
I found that the path from my "SetEnv.cmd" did not include C:\Program Files\Microsoft SDKs\Windows\v7.0A only C:\Program Files\Microsoft SDKs\Windows\v7.1 which somehow did not contain resgen.exe. ...