|
- DnSpy shipping malware? : r dotnet - Reddit
DnSpy shipping malware? I downloaded dnspy as an alternative to ilspy, and virustotal lists the zip as fine I ran it, went to open an assembly, and it alerted errors, my device became unresponsive and stuttery About a minute later windows defender came up noting it had noted a Trojan
- [DnSpy] how do I compile while ignoring errors? : r dotnet - Reddit
r frontend is a subreddit for front end web developers who want to move the web forward or want to learn how If you're looking to find or share the latest and greatest tips, links, thoughts, and discussions on the world of front web development, this is the place to do it
- Newest dnspy Questions - Stack Overflow
Stack Overflow | The World’s Largest Online Community for Developers
- [DnSpy] How do I ignore compiling errors? : r HowToHack - Reddit
[DnSpy] How do I ignore compiling errors? I opened up a DLL and I am trying to change a variable Unfortunately the file this variable is in has hundreds of compile errors I want to ignore the errors and just change this variable I don't want to go through thousands of lines to fix their code
- dnSpy archived, anyone know why? : r dotnet - Reddit
It would appear that 0xd4d uploaded dnSpy (or the GitHub page?) to Archive org around when it was archived on GitHub I can't tell if this is the actual repository but it's certainly strange
- dnSpy: how to start 32 bit version - Reverse Engineering Stack Exchange
But I am unsure if the 32-bit version is included I also cant find any information on flags or parameters dnspy is able to take My question is if dnspy 32 bit is installed by using choco or if one has to install the 32-bit manually And if dnspy 32 bit is installed with choco, how do I start it in 32 bit
- dnSpy showing strange disassembly code for async methods
dnSpy For the old dnSpy (which is archived as of now) there is no way to see it as normal code, instead you should check the View->Options->Decompiler->C#->Show hidden decompiler generated classes and methods otherwise the code will be missing at all
- How to use dnSpyEx or some other . NET debugger to attach to a . NET . . .
Here's how it looks from the Detect-It-Easy tool: I can open the image file for that process (from disk) with dnSpyEx, but when I try to attach to it with a debugger while it's running (after it was process-hollowed), my breakpoints don't hit: Any idea how to attach to such process with a debugger - dnSpy or some other one?
|
|
|