14

F5 debugging is pretty cool, but for small and not complicated projects. You know, that by pressing F5 your solution will be deployed again, including all steps - add solution, install solution, activate features. And it often takes really long time. There is a couple of extensions for visual studio that makes your life easier. As for me, I use CKS DEV ...


9

Append ?contents=1 to the end of your query string to delete broken web parts from the page.


5

You best chance is to try at least four things while debugging: Use logging library "SharePoint Sandbox Logging" to log errors on feature activation, as you probably know logging capabilities on Sandbox are limited. Have Correlation Id with your error? contact Microsoft support Review SharePoint logs for on-premises Sandbox to check for any errors, warnings ...


5

According to this post How to debug Feature Receiver you can add this line of code to the method you are trying to debug: System.Diagnostics.Debugger.Launch();


5

For your issue, I recommend to follow the steps as below: Clear SharePoint Designer cache: How to Clear Your SharePoint Designer 2010/2013 Cache Deactivate all "Workflow" features at the Site Collection level. Enable all "Workflow" features at the Site Collection level. PSCONFIG (Not Necessary) (or run the SharePoint 2010 products configuration wizard) ...


5

This is because, when you stop debugging the solution get retracted from webapplication. Deploy the solution and you will find webparts in gallery.


4

This is why i only work from VM's, they're easily replaced, and my host OS (Server 2008R2) remains clean and fast. I have a whole domain running in multiple VM's and only have the bare minimum installed directly on my laptop (Only Office basically). Whenever a new version of a product is released, i create a new VM and test / try it in there. If it breaks, ...


4

I would check the ULS logs with a tool like the ULS Viewer. Start a trace, load the page again and check the viewer. It may reveal more details about what's happening to cause the problem. Here's a link: http://archive.msdn.microsoft.com/ULSViewer


4

You'd have to use something like .NET Reflector and its Visual Studio plugin in order to actually step through the code in the debugger. With something like ILSpy you can take a look at the code, but not step through it, which may well be enough to discover what's going wrong without spending money.


4

I am not pretty sure how you are debugging your SharePoint portals right now. But I would suggest you look at the Visual Studio 2010 extensions and different techniques that make debugging life easier. Please go through this post where all these are consolidated at one go. http://pholpar.wordpress.com/2010/05/20/visual-studio-2010-extension-for-helping-...


4

Try to do the following to hit your breakpoint Retract your solution. Perform IISRESET. Deploy it again. Set your breakpoint and make sure it's not disabled. Open SharePoint Portal. Attached Visual Studio project to the w3wp.exe processes Choose managed code in the attach to process dialog. Try to delete an item from your list , that should hit your ...


4

Attaching to multiple processes, while it will work, is a bit overkill and attaches unneeded processes. Look up the name of your app pool in IIS, open up a command prompt and then enter cd %windir%\system32\inetsrv\ appcmd list wps (or appcmd list wps /apppool.name:AppPoolName if you know your pool name and want to be specific) Your app pools will ...


4

You could check if there are any specific webparts that could contain any scripts. Add ?Contents=1 (http://example.com?contents=1 or http://example.com/sites/example?contents=1) to the end of your site url to see all the webpart that exists on the page that has the problem. If you find any Content Editor Web Part or Script Editor Web Part, those could ...


3

I have seen this behavior before when IIS is not cycled after VS builds and deploys to the GAC. In those cases, it is using a cached copy of the code and thus the breakpoints do not line up. An occasional IISReset will flush this through. The other thing to try is manually attach to ALL W3WP.exe processes and see if it hits your breakpoints then. If it ...


3

Just to be clear - you want to debug an already deployed Sandboxed solution, you need to attach the SPUCWorkerProcess.exe proccess manually and hit F5 to debug! Occasionally a VS restart helps as well as a good old stop/start of the Sandbox Service via SharePoint CA!


3

Please follow this tutorial, I have done it thousands of time and it always work the same way. http://msdn.microsoft.com/en-us/library/ff798479.aspx


3

If you are using VS2010 to deploy the feature, try changing the Active Deployment Configuration in the Project Properties\SharePoint tab to "No Activation". When you run the application with debugging (F5), it will deploy the package and activate it before the debugger attaches to the process. Turning off automatic activation will allow you to attach to ...


3

When the piece you are debugging can run from a sandboxed solution, F5 debugging is much faster. For one thing, you don't have to recycle the application pool. To me, that feels much more like the typical plain asp.net debugging situation. Not every solution can fit in the sandbox and benefit from this speed up. Sometimes, the incompatability with the ...


3

You have two options: Catch all errors in your web part and then log them to ULS, show in hidden div, ... Develop you web part in a Sandboxed solution, then SharePoint will take care of protecting the rest of the page To elaborate on the first. It can be implemented using this pattern: Add a string variable errorMessage string errorMessage; Write each ...


3

Napa was created with the objective to facilitate a 'lightweight, in-browser experience' to build SharePoint or Office web app in the same browser where they would run. Ergo, it was designed to kind of complement the inherent features of the browser. For advanced tooling, one would have to turn to Visual Studio 2012 You can debug code like any javascript: ...


3

As strange as it may seem, this error is often experienced when you are debugging a SharePoint App and you never had published your solution (so the solution package has not been created). Use the "Publish" command to create the package and debugging should work normally afterward. Notice that the deploy functionality works even without the publish step so ...


3

If it is a user control, you can just replace the .acsx file in the Layouts folder. But if it is a C# file, you need to build the project without changing the assembly version and copy that into the GAC (assembly folder). There are some third party VS tools such like CKSDev.


3

There are 3 solutions to this problem. Solution 1 1. Close down dev environments 2. Go to Documents folder and rename IISExpress. 3. Now set environment variable _CSRUN_DISABLE_WORKAROUNDS (ref: http://gauravmantri.com/2013/02/05/workaround-for-iis-express-crashing-when-running-windows-azure-cloud-service-web-role-with-multiple-instances-in-windows-azure-...


3

Based on the information found on this blog you actually have to attach to the PowerShell process if you upgrade your feature like you did. . Simply pressing F5 in Visual Studio will deploy the solution, launch the browser window and attach the debugger to the w3wp.exe process. However, upgrading the feature is done in PowerShell. Running the ...


3

In order to deploy your project from Visual Studio, go to the Solution Explorer and right click on the name of the project as shown below. Click the Deploy Solution button to deploy the project. Once your project is deployed, go to the page for which you have coded on the browser. Once this is done, go to the visual studio. Select Debug menu. In this ...


3

Rather than using $(document).ready() try this: <script> _spBodyOnLoadFunctionNames.push("ButtonFunc"); function ButtonFunc() { $('.ms-qcb-leftzone').append('<li class="ms-qcb-item"><a href="http://www.google.com">ButtonName</a></li>'); }) </script> If this doesn't work check that the selector $('.ms-qcb-leftzone') ...


3

you can install Debugger for Chrome extension in the VS Code and follow the step as described in Github Debug SharePoint Framework solutions in Visual Studio Code


3

They all run different IIS applications - check out the usernames attached to each one. I always attach to all the w3wp processes just in case - you can shift-click to select multiple processes.


2

Install-SPSolution starts a SharePoint Timer process, so try attaching to the owstimer process instead of w3wp.


2

Check the event logs for errors - after a week I noticed it started working again. I think it was taking too long, once it caught up it completed successfully again.


Only top voted, non community-wiki answers of a minimum length are eligible