New answers tagged debugging
It works attaching iisexpress manually and then starting an app project.
I suggest you to use this code: string strUrl = "http://url"; SPSite siteCollection = newSPSite(strUrl); SPWeb web = siteCollection.OpenWeb();
SPWorkflow.CreateHistoryEvent() works fine. The problem was, I was using it in an onTaskChanged event that was not getting hit. Specifically, my workflow had two tasks and two of these task-changed methods. I was simply putting my code in the wrong event.
Yes you have a farm. I would presume that you should be looking on the server that holds central admin. Goto the logs and check there, the logs is located within the hive files: sharepoint 2007 C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS sharepoint 2010 C:\Program Files\Common Files\Microsoft Shared\Web Server ...
I use Debug -> Start Debugging and for Visual Web Parts at least Visual Studio deploys and then attaches without me having to do anything else. This doesn't work for timer jobs or event receivers though.
You can do Debug -> Attach to Process and select the process with name w3wp.exe. If there are multiple w3wp.exe then you should attach all of them. In case of debugging timer jobs, you can attach process owstimer.exe
Top 50 recent answers are included