• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2411
  • Last Modified:

How to debug EXE outside of project?

I have an EXE with an associated PDB file.  Is there a way to point VS.NET 2005 to these files so I can debug the app?  There isn't any project.  Just the two files.
0
brettr
Asked:
brettr
1 Solution
 
AlexFMCommented:
PDB file is not enough, it is necessary to have source code. Having PDB file without source code you can see only Assembly code.
To start debugging running executable, use Attach to Process Visual Studio command.

Assuming that this is legal, you can use Reflector http://www.aisto.com/roeder/dotnet/ to create source code from .NET executable. AFAIK, there is some Reflector enhancement which allows to create all source code at once from executable.
0
 
brettrAuthor Commented:
Ok, thanks.  I don't want to get that involved with it.  I obsfucated an EXE with .NET Reactor and now it crashes before any GUI loads. I do actually have the project but I don't think .NET Reactor uses it.  I wanted to check to see why the EXE crashes but I'll never know because there isn't any process to attach to.  I have it set to obsfucate minimually an not embed DLLs.  I don't want to get all wrapped up in it so I'll probably just try the community edition of Dotfuscator.

I mainly wanted to use .NET Reactor because it keeps people from decompiling your code.  Do you recommend any obsfuscators?
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now