Posted in Customization, masterpage, MOSS 2007, Productivity, tips, tagged cannot complete this action, different webparts, error, exception, identical id's, page layout, SharePoint 2007, sp designer 2007, webpart, webpart id on September 17, 2010|
7 Comments »
It’s time for a new trouble report. It is a minor issue, but getting behind it was not trivial (in fact, I got there by chance 😉 ).
So, we had the following problem: When creating a page which was using a page layout with pre-added WebParts, it would throw an exception everytime we were trying to access that page, stating:
Cannot complete this Action.
Not much information, is it? Also, the stack trace did not really provide any helpful points for resolving the issue.
So, the next step clearly was to investigate the page layout in question. Using SP Designer 2007 I accessed the page layout and looked through the corresponding aspx.
Oh, wonder! I found two (different) webparts with the same id! Actually, this was the cause for the exception.
Solution: I just replaced the trailing “1” of AnotherWebPart’s id with a “2” (manually). And make sure the id you are giving won’t interfere with another existing web part (in our case, “YetAnotherWebPart’s id”).
I am aware there are multiple causes for the exception “Cannot complete this action.” – but if your pages show the same symptoms (exception occurs when trying to access the page with a specific layout, layout containing various webparts), then you might give it a shot!
Best regards and stay tuned till the next time!
Read Full Post »
Posted in Automation, c#, Debugging, News, Unit testing, visual studio, tagged application pool, attach, attach process, debugger, Debugging, identities, w3wp, web development on September 3, 2010|
Leave a Comment »
Once again about WADA, but this one will be short. I’ve added a new functionality, which is:
- Filter W3WPs by related Identity (as of the application pool)
Thanks to my colleague Patrick for suggesting this functionality!
The UI has changed a little, offering the new drop down for the identities:
The WADA 1.1 download is still available at the Visual Studio Gallery.
Please note: The Application Pool- and Identities-Filters are mutually exclusive.
Read Full Post »
Posted in c#, Debugging, Productivity, Uncategorized, visual studio, tagged attach, attach process, debugger, Debugging, Extensions, IDE, integration, VS 2010, w3wp, web development, worker processes, wpf on September 2, 2010|
18 Comments »
Today I released the first version of the WADA Visual Studio 2010 extension for web developers – it enables you to being able to attach processes to the VS debugger – not simple processes, but the w3wp. I guess, some of you know the issue:
- > 1 application pools
- > 1 w3wp processes
How could we know which process is right for being debugged by us? First, we could use one of the numerous scripts out there (like iisapp.vbs for Windows 2k3), but they provide poor integration into the VS2010 IDE (actually none at all). This is where the strengths of using WADA come into play.
What this Tool Can Do:
- List all w3wp processes, along with the application pool names
- List w3wp processes for a specific application pool
- Attach a selected process to the debugger
Why should I Choose This over Scripts?
- You can remain in the IDE
- Directly attach W3WP to the Debugger (not possible with e.g. iisapp.vbs)
- Filter by Application Pool of Interest (not possible with e.g. iisapp.vbs)
- No more need for manually matching IDs (from script output) against the “Attach to Process” window’s process list
Is it Bulletproof?
No. Not at all. Please be aware that this extension comes in its first version and may contain errors and/or undesired behaviour. It also assumes that you have administrative rights on the machine you are working with it (also VS must be run in administrator mode). Hence, I’d like to emphasize that I cannot be held liable for any usage of the code causing undesired behaviour, loss of data, any damages caused to any soft- or hardware (including source code) of the user. Please do not try it in production environments. It is intended for testing purposes only.
In case you intend to test it, it would be really nice if you provided some feedback on it using the post.
- Go to View -> Other Windows -> WADA Advanced Attacher
- Select Application Pool of Interest (optional, otherwise all will be considered)
- Click “Get Procs” (ensure that “Only W3WP” is checked)
- Select Process from list
- Click “Attach”
WADA 1.0 (Visual Studio Gallery)
Installation is done simply through double-clicking on the downloaded .vsix package.
I hope you enjoy it!
Read Full Post »