In Visual Studio place a breakpoint in the code and start debugging. When it breaks, open the Disassembly window (Debug > Windows > Disassembly or Alt+Ctrl+D).
More Related Contents:
- When is a method eligible to be inlined by the CLR?
- Does the .NET CLR JIT compile every method, every time?
- Deciphering the .NET clr20r3 exception parameters P1..P10
- Why Large Object Heap and why do we care?
- A definitive guide to API-breaking changes in .NET
- LINQ on the .NET 2.0 Runtime
- What are the roots?
- How do I detect at runtime that .NET version 4.5 is currently running your code?
- Resolving MSB3247 – Found conflicts between different versions of the same dependent assembly
- How do the .NET Framework, CLR and Visual Studio version numbers relate to each other?
- Equivalent of Class Loaders in .NET
- How to call managed code from unmanaged code?
- Is it possible to get parameters’ values for each frame in call stack in .NET
- No AppDomains in .NET Core! Why?
- Get Current .NET CLR version at runtime?
- Retrieve JIT output
- Is the CLR a virtual machine?
- Where is the .NET JIT-compiled code cached?
- Where is the .NET JIT-compiled code cached?
- How to do SQL Like % in Linq?
- Case insensitive string compare in LINQ-to-SQL
- How can I add a hint text to WPF textbox?
- .NET convert number to string representation (1 to one, 2 to two, etc…)
- Create a hashcode of two numbers
- Is it necessary to add a @ in front of an SqlParameter name?
- Accessing imgUr thru OAuth (uploading to user account)
- Making DataGridView rows a certain color based on a column value
- How does Copy-local work? log4net.dll is not being copied to MyProject output directory
- Using entity framework on multiple databases
- Using SharpZipLib to unzip specific files?