Comments
Sort by recent activity
Speaking from my own experience, usually it's best if possible to merge the dll with the exe (in your SA project) that will be calling it. That's the ideal fix because then everything in the dll becomes internal. Otherwise everything in the dll that is public cannot be renamed or pruned because, by definition, being public they have to be accessible to any exe that loads the dll.
If you don't want to merge it then try to make as much as you can into internal classes etc and only leave the ones you really need to be accessed from outside the dll as public.
Hope that helps. I'm just another ordinary user of SA btw [image] / comments
Speaking from my own experience, usually it's best if possible to merge the dll with the exe (in your SA project) that will be calling it. That's the ideal fix because then everything in the dll be...