Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This is probably a silly question but here goes:
I like to be able to see the source code of third party (OSS) libraries from within my projects. I always setup my projects like this when using java. Is this possible in Visual Studio? I am not interested in building them! Only have them available for reference if lets say an exception stack trace points to a third party component…
Debugging a third-party DLL in Visual Studio.NET? covers much of the details if you’re trying to do this for debugging purposes. But in general, two points to take away. First, it’s unfortunately a little bit harder than it would be in Java. Second, it depends heavily on what language you’re using.
Essentially, you do the following if it’s a .NET assembly you’re working against.
Decompile the source code with something like Reflector, then treat the decompiled source code as a new library within your project and set breakpoints in the source.
Remove all references to the 3rd party library so that it is the decompiled code that is executing.
Don’t forget to remove references to the source elements later.
If it’s an existing open-source library, you can just compile the source yourself into program database (PDB) files, assuming there’s a corresponding VS project. More on that here.