Menu

See what a .NET assembly depends on and calls with Glass.NET
πŸ“°

See what a .NET assembly depends on and calls with Glass.NET

DEV Community: dotnetΒ·Zero HeartbeatΒ·13 days ago
#BwH6G4jP
#devtodotnet#devto#dev#assembly#call
Reading 0:00
15s threshold

You are about to ship a third-party DLL inside your own product, and you want one thing settled first: what does it actually reach out to? Not what the README claims β€” what the binary is wired to do. Which other assemblies and packages it pulls in, what framework it expects to run on, whether it calls into native code, and whether it opens a socket, writes a file or launches a process anywhere in its body. That is a dependency's external surface , and it is exactly the thing you cannot see from the package page.

You can see all of it without running the DLL. A compiled .NET assembly records its dependencies and its calls in metadata and IL, and Glass.NET reads that and reconstructs readable C#. It is free, and it is strictly static β€” it reads metadata and IL and reconstructs C#, and never executes the assembly it inspects. That is the whole reason this is safe: auditing a dependency you are unsure about means reading it, not running it, and reading is all Glass ever does.

Let's make it concrete.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.