Better debugging for extensions

On our radar
Right now, debugging the code extensions seems to be impossible, unless I am missing something. This really needs to be improved somehow.

Created on 30 Apr 2010
Comments (6)
30 Apr 2010

If you have the platform installed on your computer you can attach the Visual Studio debugger to the IIS process.
30 Apr 2010
Good to know that! All the same, that needs to be improved so it is a smoother workflow. I've been using AP for a while now, and that was quite non-obvious to me.

30 Apr 2010
Yes, it's not obvious and maybe not easily discoverable through the documentation.

And if you're working in more than one platform version at the same time, it's not reasonable to expect that you have different platform installations in your computer.

And besides the extension might not be runnable in a local machine for some reason or another, like for instance if it needs to be in a remote server to connect to a legacy system.

And it's not usual to find a visual studio installation in a development server.

20 Apr 2011
Merged this idea with 'Debug an Extension!' (created on 2011-04-14 19:10:49 by Nuno Baptista)
14 Apr 2011
Inside SS, call Visual studio and debug the extension code.

Merged from 'Debug an Extension!' (idea created on 2011-04-14 19:10:49 by Nuno Baptista), on 2011-04-20 09:43:08 by Rodrigo Castelo
19 Jul 2011
We must be able to debug an extension without having to attach it to the server's process instance.

Merged from 'Simplify the extensions debug process' (idea created on 2011-07-19 10:01:16 by André Ramos), on 2015-12-01 12:29:12 by Goncalo Borrega