i have a problem with a DLL.
i have created an DLL agent snmp extension with visual studio and for testing debug DLL i connect it to snmp service, but if open Debug->Module my DLL is not present in the list, so the breakpoint are not avaible.
Can anyone help me?
If you want to Debug your DLL you had to debug SNMP.EXE. for that Debug->Attach to process. Keep the pdb file close to the DLL.
Related
I've successfully injected an arbitrary DLL into a foreign process. But this DLL seems that the injected DLL has errors. I can attach a second Visual Studio session to that process but Visual Studio doesn't show me any disassembly of the crash. Doesn't Visual Studio look for debug information on the crashed code in the same folder of that module ?
I have a .net dll. For some reasons I have registered it for COM. I tried a lot of options to debug the code of this dll but nothing has worked. Someone please suggest a way to debug the code of COM registered .net assembly.
You'll need to debug the client, either by starting it from the debugger or by attaching to the running process. You'll need to have managed debugging enabled. You'll need to have the .pdb file accessible to the debugger (in all cases where I've done this, the .pdb file is in the same folder as the COM component).
I have the following scenario:
Visual Studio 2010 solution with one WPF-project, output file is "Tool.exe"
Eclipse Shared Library project, output file is "Tool.dll"
I place the dll in the same folder as the exe and then I try to debug using Visual Studio; but I get the following error:
Error while trying to run project: Could not load file or assembly 'Tool' or one of its dependencies. The module was expected to contain an assembly manifest.
I have managed to find a solution to the problem, rename the dll, apparently the exe and dll cannot have the same name. My question is, why is this error occuring in the first place? Why does the name of the dll affect Visual Studio? The error occurs before even trying to pinvoke the dll. If I run my application without Visual Studio it works perfectly, but I want to be able to debug it of course.
Right now renaming the dll is plan B, but before I do that I would like to know if there is anything else I can do to fix this problem?
Thanks in advance.
I found simple steps to solve this error.
1- change your windows.
2- install Symantec Endpoint Protection Client 12.1.6318.6100 x32 or x64 bit.
You can geting it software(32 bit) from link: (ftp://192.168.168.215/Public/Antivirus/Symantec/Symantec Endpoint Protection Client 12.1.6318.6100 x86.rar)
drag and drop it to your software(IE ,....) to work.
3- install all driver on your computer.
4- install Visual studio.
End
How can we trace a compiled application from windows 7. I can see in the event viewer that some DLL files which my program is trying to fetch are causing problems but I can't figure out why.(This is with qtcored4.dll)
You can solve DLL loading problems with Dependency Walker, either by looking at the exe (just open it) or tracing DLL load process by starting profile.
I'm trying to use VS's attach to process tool to debug add-ins I'm developing for Sql Server Reporting Services.
I am able to correctly debug it with attach to process when I copy dll's and pdb's in my project debug/bin dir to the ReportServer/bin dir. But, if I use my msbuild script and copy those dlls and pdbs to the ReportServer/bin dir I get the wrong version.
1) How do I check the current version of a dll/tell if a dll is incompatible with another version?
2) And how do I tell what dll's/versions are loaded by the ReportServer process?
Thanks!
I don't know anything about Sql Server Reporting Services, but
1) you can inspect the version of a DLL with ildasm.exe
2) when you use VS 'attach to process', in the 'Modules' window it shows the version numbers of all the loaded assemblies