By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,066 Members | 1,841 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,066 IT Pros & Developers. It's quick & easy.

Debugger visualizers - about as much use as a chocolate teapot?

P: n/a
I'm becoming increasingly frustrated with debugger visualizers (VS 2005). It
seems virtually impossible to write one which doesn't cause a timeout when
trying to view the data.

I'm guessing that part of the problem may be the time required to generate
the temporary serialization assemblies. So, he thinks, set the project flag
to build serialization assemblies. Does this work? Of course not. Further
investigation, found only by Google, not via any Microsoft documentation,
reveals that this setting only works for web service proxies. So, he thinks,
let's try creating a post-build command line to call sgen.exe. Only now I
get "exited with code 9009" or "exited with code 123" and so on. Is there
any documentation on these error codes? Of course not. So it seems that this
line of investigation in trying to improve the speed of visualizers has come
to a grinding halt.

Seriously, has anyone else been having no end of problems trying to create
debugger visualisers which actually work, or is it just me?
Nov 21 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Nov 21, 2:57*am, "Clive Dixon" <clived at digita dot comwrote:
I'm becoming increasingly frustrated with debugger visualizers (VS 2005).It
seems virtually impossible to write one which doesn't cause a timeout when
trying to view the data.

I'm guessing that part of the problem may be the time required to generate
the temporary serialization assemblies. So, he thinks, set the project flag
to build serialization assemblies. Does this work? Of course not. Further
investigation, found only by Google, not via any Microsoft documentation,
reveals that this setting only works for web service proxies. So, he thinks,
let's try creating a post-build command line to call sgen.exe. Only now I
get "exited with code 9009" or "exited with code 123" and so on. Is there
any documentation on these error codes? Of course not. So it seems that this
line of investigation in trying to improve the speed of visualizers has come
to a grinding halt.

Seriously, has anyone else been having no end of problems trying to create
debugger visualisers which actually work, or is it just me?
I'm glad others are having this problem too. I don't even use the
step-through debugger anymore hardly; I just write to sdout or file,
or use a MessageBox. It's a loss in productivity but it gets the job
done.

RL
Nov 21 '08 #2

P: n/a
"Clive Dixon" <clived at digita dot comwrote in message
news:OJ**************@TK2MSFTNGP05.phx.gbl...
Seriously, has anyone else been having no end of problems trying to create
debugger visualisers which actually work, or is it just me?
I wrote an image viewer way back when 2005 was still in beta and it worked
great. I guess it depends on the complexity of your visualizer.
Nov 21 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.