n
nLast few days I wasnplaying much with MS word add ins and its development, Yes you are right,nwhen the word ‘develop’ comes into the picture , each and every developer needsnto think some logic and then they let the figures do the remaining job. Therenare many times when run-time error occurs and developer go ahead and track/findnthem using debugger.
n
nMost of us use VisualnStudio, the developer’s heaven as IDE for the .NET based applicationndevelopment and Microsoft has given way too good features to debug your code. (Linknhere)
n
nSome examples:
n
n· nWhen debugging webnbased projects / SharePoint farm solutions , one attaches the debugger tonthe w3wp.exe (IIS process)
n
n· nWhen debuggingnsandboxed solutions one needs to attach the debugger to the SPUCWorkerProcess.exen(SPUC)
n
n· nAnd againnwhile debuggingnthe timer jobs in SharePoint debugger needs to be attached to Timernservice. (OWSTimer.exe)
n
nOk ok, before I getnthe question like – come on we know all of these.. I will come to the pointndirectly.
n
nI learnt a lessonnthat if you need to debug the MS Office Addins then you must attach thendebugger to the appropriate MS Office Client.
n
nIn my case, as I wasnworking with MS Word Addin – so I needed to attach the debugger to WINWORD.exe service,nlike this
n
n
n
n
n
n
n
nIf you do not see WINWORD.exe process , make surenthat you have launched the MS Word Client and selected – Show all process ,nshow process from all users/sessions in the attach debugger window.
n
nAlso If the debugger is not getting attached, thennmake sure that the add-in is referring to the dll is latest in the respectivenlocation. (For example If add in is referring to the dll somewhere in releasenfolder of your solution then make sure that the dll is latest)
n
n
n