This post will help you when you want to identify which W3WP belongs to which application. It comes in handy when we need to debug Visual Web Parts and Event Receivers deployed as Farm Solutions. The basic approach requires the user to open Visual Studio, attach the W3WP processes and refresh your page to start debugging.

Well, it’s pretty common in our daily life tasks (not so much since we all should move to the Client-side of the force) to have more than one W3WP available to attach. Usually we have one for your site, other for SharePoint Web Services, another for the SharePoint Central Admin and even more for any other Application Pool process being used in your Server.

But if you want to attach to just one process and make Visual Studio more performatic and responsive, how can you do that?

Just follow the steps in this post!

Continue reading