Click Finish.Īfter creating the list, a tab with the list instance settings opens. In the settings window, select: Create a list instance based on an existing list template, namely Custom List. To do this, perform the following steps: right click on the title of the project RERDemo -> Add. Let’s add Report list to our application. RERDemo – is the actual application (app) for SharePoint, the second RERDemoWeb – is a website service that is responsible for receiving events. In our case we used Azure Access Control Service.Ĭlick Finish. Window with a choice of the authentication type will appear. Our example – Asp.Net MVC Web Application. To create the application, we also need an account in Office 365 (you can purchase a licensed version from the developer, or use a 30 days trial).Įnter the website address where our application will be accessed.Ĭhoose the type of web application. Remote event receivers are supported only by Provider-hosted applications, that is why we choose this type. As an example, we will create a project, which will have an event receiver that is triggered on item creation in Report list.Ĭreate a project in Visual Studio 2013. The only thing that works for me is rebooting.In this post we will describe how to create and debug Remote Event Receivers for SharePoint Online (Office 365). I have tried restarting Visual Studio and other things and that simply does not work. It's annoying but it does fix the problem. So how do I resolve this issue when it occurs? Reboot the client machine. I am using the same account which is local administrator on both, so that is not the issue. Most articles point to making sure that the account the remote debugger is on also has access to the client machine. By the error it's obviously an authentication issue.
If you do a Google search, you will find that this is because the remote computer cannot connect back to the desktop for some reason. Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. However, every couple of days when I show up for work, I encounter the following error. I have an environment that works great for remote debugging most of the time. This error has been pissing me off for a long time. Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor SharePoint PowerShell Community Toolkit.