Comments for != : Bang Equals

Comment on Stubborn Services II by Richard Lee

Richard Lee — Sat, 03 Mar 2012 16:16:15 +0000

I use this method too – I use the following trigger mechanism:
private readonly string APPLICATION_DIRECTORY = Path.GetDirectoryName(Assembly.GetExecutingAssembly().CodeBase); private bool _isDebugMode = false; . . . protected override void OnStart(string[] args) { // If the Debug.debug file exists in the install directory then Debugger will be automatically attached { if (File.Exists(Path.Combine(APPLICATION_DIRECTORY, "Debug.debug"))) _isDebugMode = Debugger.Launch(); }

//Do whatever }

I then have a file called Debug.debug which can be empty, with a Copy Always setting in VS. That way it is copied over for each build. When I’m ready, I simply delete (or rename) the file file and do a clean and rebuild.

Comment on Stubborn Services II by MyName

MyName — Thu, 19 Jan 2012 10:13:40 +0000

Thanks, great post !

Comment on Should I Be Ashamed… by pamela

pamela — Fri, 26 Jun 2009 07:42:31 +0000

Late but better than never!

HAPPY BIRTHDAY, OMAR!

I guessed that you were rather brilliant!

Comment on Overriding ToString() Makes Debugging Easier by JMS

JMS — Thu, 18 Sep 2008 19:53:21 +0000

…never mind the fact that some of us old fuddy-duddies make the assumption that we won’t always have the debugging environment available to us, so decorating with an attribute that changes how the data gets displayed is nifty in the short term, all the fancy debug windows aren’t always there to save you. Generally speaking, using stream output to debug in context is the oldest (and most bullet proof) method of debugging if the stuff hits the fan. What better to support this sort of tracing than ToString()?

Comment on Overriding ToString() Makes Debugging Easier by JMS

JMS — Thu, 18 Sep 2008 19:48:08 +0000

Agree with Matt…the only thing you should ever use ToString() for is to get, um, a string that somehow makes an object human readable. I’ve used it in debugging environments and for logging purposes with great success for quite a while now without a hiccup.

Using it for reflection, with the Activator or type checking is totally dangerous. What happens if it’s an Int? You won’t get the fully qualified class name, just a string conversion of the data. Makes no sense.

Comment on Stubborn Services II by Adrian Aisemberg

Adrian Aisemberg — Wed, 17 Sep 2008 12:45:29 +0000

You can use the start arguments:

if (args.Length > 0 && args[0]==”DEBUG”)
{
Debugger.Launch();
}

That way, the debug option is always there. No need to re-build when we want to debug.

Comment on Stubborn Services. by != : Bang Equals » Blog Archive » Stubborn Services II

!= : Bang Equals » Blog Archive » Stubborn Services II — Wed, 17 Sep 2008 09:23:39 +0000

[...] my last article on Stubborn Services I was having issues uninstalling a service that I had installed. Today I was having a problem with [...]

Comment on Overriding ToString() Makes Debugging Easier by Matt

Matt — Mon, 15 Sep 2008 16:31:53 +0000

ignu,

I sure hope you aren’t depending on ToString() to return an object’s fully qualified type name. That’s what Type.FullName is for.

ToString() is just that, a string representation of an object. And like all strings, is subject to being loose, inaccurate, difficult to parse, containing a typo, null, etc and should be treated as such.

Comment on Overriding ToString() Makes Debugging Easier by RyanOC

RyanOC — Mon, 15 Sep 2008 12:14:09 +0000

Good stuff, thanks!

Comment on Overriding ToString() Makes Debugging Easier by ignu

ignu — Sun, 14 Sep 2008 20:54:45 +0000

“Overriding ToString is seldom a good idea. ”

i agree. lord knows what’ll happen if you try to write an object and you don’t get its fully qualified type name.

scary.

DebuggerDisplayAttribute for helpful debuging info
override ToString() for something that makes sense to display in a ui.