dnSpy | .NET debugger and assembly editor | Code Inspection library

Since "IntPtr.Size" checks the size of int's pointer based on the current process, is it the same as "Environment.Is64BitProcess"?

If yes, why can I only see "return true/false" (if you use dnSpy to refactor the code from "System")?

If not, any differences between them? Where to use what?

I have a dump of an executable file (Runtime: v2.0.50727). It works well without any mistakes. I could load it to DnSpy to debug or to ILSpy. Both of them tells that all references successfully resolved.

However, I can't load it using this code:

I have been looking through ways to **debug external projects like BaseLibrary **. So I haven't seen such a code structure or worked on it. I think I can debug those projects with the use of the .pdb file present in the output.

This is how the project structure looks like. And I will be debugging the last project which is being highlighted. I have gone through these links

https://docs.microsoft.com/en-us/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger?view=vs-2019

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/internals/sourcelink?pivots=windows

I have added references for pdb file. I'm not sure if it is incorrect format the reference of pdb file is C:\Workspace\Xamarin.IntegrationLibrary\Output\netstandard2.1 as you can see in the following image.

But they are not helping me with my requirement because it is talking about debugging the NuGet packages which I'm installing in my current project. I want to debug the external projects. Currently, I'm able to navigate to assembly of the base library but I'm not able to navigate to source code or methods. As you can see in the following image.

I even tried debugging in dnSpy but I'm not able to give the executable for that. Also, it is not exactly what I require because I have to debug within the project using pdb.

Some solution says double-clicking on the DLL in the module opens the source code. Well I tried that as well as you can see the following screenshot

I am able to load the .pdb symbols but I want to navigate and debug the source code of base library and integration library from xamarin.xyzApp project. I have no clue how to proceed with this. Any suggestions?

I am using dnLib to generate MSIL assemblies dynamically from a custom language I'm writing, named CSASM:

I'm currently researching a subject and I honestly lack the knowledge to even be sure whether it's possible at all.

I want to find out if it is possible to understand the process memory of a .NET application when I don't have the source / the PDBs. With understand I mean if I can reconstruct an object graph if I find some starting point, like a known string value.

We want to protect a program configuration that is deserialized from encrypted config files. It is unencrypted in memory. The single values in the configuration graph aren't really secret, but the graph itself is of value.

The questionis if it is possible to reconstruct the graph from the process memory only?

Given the attacker knows how to use something like dnSpy to reconstruct the assemblies (that we protect on disk too) and that we don't want to obfuscate the config assemblies (which would require a lot of changes), can the attacker reconstruct or understand the instances based on the raw memory of our process?

I tried researching this, but I cannot find the right direction / good keywords for what I'm looking for.

I understand that tools like CheatEngine exist or that I could simply dump out the whole memory and try to make sense of that.

But I'm trying to understand if there's a .NET tool that automates the process:

1. Read the decompiled assemblies with the config classes
2. Attach to the process and dump the memory
3. Make sense of the bits and bytes and combine with the decompiled classes to reconstruct the instance hierarchy

My main goal is to decide whether or not additional protection of the in memory config graph is needed. If it's not easy to reconstruct the graph, then I think it's not needed. But if it would be as easy as decompiling the source code of a .NET application, I think some protection would be required.

I decompiled some unity dll files in dnspy and got this line

I'm making an mod menu for a game called Ravenfield. It's an injectable DLL. I need to modify some things about the player, for example the speed, health, etc etc and for that I need to find the player object which contains all of that. With dnSpy I was able to find the player class which is called "Actor". When I try to find it in public void Start() by typing Player = FindObjectsOfType(); it says "The name "Player" does not exist in the current context.". I've added both UnityEngine.dll and Assembly-CSharp to my refrences.

I haven't slept very well and I'm sort of braindead ATM so if anyone could help me with this, I'd appreciate it very much. :)

Code:

I got a very specific case and I read tons of questions on StackOverflow about setting and getting private fields and properties of classes but they all do not seem to work.

I am modding a Unity game by injecting code with Harmony ( a library to inject code at runtime). I successfully changed a lot of things but as soon as values are private, I hit a wall since I cannot access nor change the values.

When inspecting the code with dnSpy: So there is the public class World {} which contains the field public static World inst as well as two private fields private int GridWidth and private int GridHeight. It also contains the properties GridWidth and Gridheight, both public but only with a Getter. It contains further fields which do not matter here. World.inst gets set in the private void Awake() method, a specific Unity method.

In short: