Does ConsoleApplication87 sounds familiar to you? If so, I’ve got some great news for you – a tip that will help you keep your disk clean of all the test code that you check out.
Recently I was debugging a Web Part which had an issue with applying its changes. It required clicking the Apply/OK button twice in order to apply the changes. While this problem is quite commonly seen in different examples on the Internet, the solution is very simple.
One of the cool things about the new Visual Studio SharePoint development tools is the ability to communicate with SharePoint to retrieve and work with SharePoint content. Running SharePoint code in the context of a Visual Studio SharePoint development tools extension is pretty simple, but you do have to know one thing in order to be able to debug it.
One of the many great things that the Visual Studio SharePoint development tools allow you to do is to help you automate and simplify working with SharePoint content without leaving Visual Studio. Knowing how to retrieve a document opened in Visual Studio using its name, is one of the basic things you need to know to make your extension really powerful.
While extending the new Visual Studio SharePoint development tools, you can create extensions that do various things: from retrieving content of a SharePoint Site and its properties to manipulating it and exporting into SharePoint Project Items (SPI). As some of these operations might take a while to run, it is considered a good practice to let the user know what the extension is doing at the moment.