New answers tagged asp.net
The key is to have both SharePoint and your app use the same authentication source. So, either your app must change to Windows Auth (aka Integrated NTLM), or SharePoint must use forms (or claims that is based on the same user store).
Are you sure you're attaching to the right w3wp process? Its identity should match the app pool identity for the web application to which you are deploying. (Are you deploying to the same web app from Visual Studio that you are attaching to?) Any reason you aren't just hitting F5 to deploy and attach automatically?
several things here! one make sure that your building the debug dll and not the release dll. 2, when attaching: goto -> debug -> attach to process -> click on select button and uncheck all appart from "managed (v2.0, v1.1, v1.0) code". and click ok, now look towards the bottom and select "show processes from all users" and "show processes in all ...
Apart form doing IISRESET, make sure that you are attaching to all w3wp.exe instances. Click on Show processes from all users checkbox and attach to all w3wp.exe services.
If its your development environment, try IISReset.. Also if that doesn't work, restart SharePoint Timer Job.. You can restart SPTimerV4 service for restarting SharePoint Timer Job, write following in Command Prompt: net stop SPTimerV4 net start SPTimerV4
If you don't need any integration with SharePoint but just want to host your Web API in the same site you can create an application off the root of the SharePoint site. Then just add the correct subdirectory to your path. If you where using http://sample.com/api/value, use http://sharepoint.com/subapp/api/value.
In SharePoint 2010 if you click on the workflow status 'In progress' it takes you to the workflow history page. There you will find 'Add or update assignees of . You don't have to custome code this OOTB feature. Carlene S.
Top 50 recent answers are included