Hide this comment

It works fine for me, with no setup. Since it's just a .NET Framework API call, I can't imagine why it wouldn't be working...

(Nice - I had not used DbgView.exe before, cool tool! [link:live.sysinternals.com] )

By on 7/6/2010 11:32 AM ()Reply
Hide this comment

Thanks for the impressively quick reply. Good to hear that it works on your computer with no additional setup. I will have a try on a different computer and see if I have somehow messed the installation up on this one [:)].

By on 7/6/2010 11:46 AM ()Reply
Hide this comment

Hello again

Somehow I must have managed to either remove or not have either of the TRACE constant or the DEBUG constant defined in the first place, and not just on my home computer either.

Well at least I'm consistent in my setups [;)].

For anyone else that might have fallen into this trap - it's easy to mend if this is all that is wrong:

  • When building debug from Visual Studio: If you are using the debug build and want to use the trace and/or debug functions, go to the project's properties, the build tab and make sure "Define DEBUG constant" and "Define TRACE constant" are checked.
  • When running FSI do not just start it by typing "fsi.exe"; instead type e.g. "fsi.exe --define:DEBUG". This allows you to actually get a response in DebugView when next issuing System.Diagnostics.Debug.WriteLine "Now it works!";; .
  • The FSI running as a tool in a window inside Visual Studio can be configured from the menu item "F# Tools" -> "F# Interactive" -> Misc. At the "F# Interactive options" line I had "--optimize"; now I have "--optimize -d:DEBUG".

Best regards
Robert

By on 7/16/2010 4:38 PM ()Reply
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper

Logging in...