Long story short, Im writing a WSS 3.0 workflow and deploying it on a remote SharePoint server.To debug the workflow, in theory, what I need to do is to attach to the ASP.NET process on the server (w3wp.exe).From there, I should be able to debug the workflow code.
In practice, what happens is that VS complains about symbols not being loaded, and Im not able to debug. My workflow assembly is being loaded -- I can see it in the modules window. However, for symbol status, I get Cannot find or open the PDB file. If I go through the symbol load information, I get this: C:WINDOWSassemblyGACMSILSimpleWorkflow3.0.0.0d0af882641d96b1aSimpleWorkflow.pdb: Cannot find or open the PDB file. D:HomempenkovMy DocumentsVisual Studio 2005ProjectsSimpleWorkflowSimpleWorkflowobjDebugSimpleWorkflow.pdb: Cannot find or open the PDB file.. Its looking for the PDB file everywhere, including the project obj directory. The Symbol File Ntdll Pdb Does Not Match The Module .Dll In ModulesSo next, I decide to try and load the symbols manually (right-click on SimpleWorkflow.dll in Modules window, Load Symbols) and point it to the PDB file in the obj directory. I get the following error: The symbol file SimpleWorkflow.pdb does not match the module. At this point, I have a number of questions for those who are more knowledgeable in the ways of VS 2005 debugging. Why is this happening 2) How does VS determine that the PDB file doesnt match the assembly What does it look at 3) How can I rectify this Can I somehow force it to load the symbols from the PDB file anyway Lastly, a few points that can clarify my position: 1) The project is being built in Debug mode 2) The assembly is signed. This is a requirement for deploying stuff to SharePoint -- it needs to have a strongname I hope I havent missed anything. So, does anyone have any suggestions It would be really great, as this thing has me really pinned down at the moment. The Symbol File Ntdll Pdb Does Not Match The Module Install And ThenCommon caauses are that updates are not propogated to the GAC properly (for instance did you uninstall and then install the assembly in question after your last rebuild. For a project solution (mainly C) created with VS2005, I have rebuilt (using Incredibuild) the solution from outside the IDE. When trying to manually load the symbols, I get: The symbol file.pdb does not match the module This is the first time I have seen this happen. To fix the problem, I closed and re-opened the IDE then loaded the same solution. ![]() No matter where I put my symbols (or used symstore in a vain hope that it was something to do with my dir structure). The PDB files were the ones compiled at the same time as the EXEDLL (in 1 project so all together). ![]() Is there a solution I am running visual studio 2008 and cannot debug Javascript. Ive tried several possible solutions to this problem that Ive come across in forums to not avail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |