i'm having this problem too. any luck?

Mark Salsbery wrote: If you have the code for the DLL, I would think proper error handling in the DLL is a much better solution. Yes. And if you don't have, and since it sounds like it's a pile of garbage, the next thing to consider is replacing it with your own code. led mike

Hi, K.L.K wrote: I did what you said, and got it to work - so now I can get debugging output sent to the console. Thanks! Fine. You're welcome. K.L.K wrote: It still feels like the old "printf" cycle of debugging (bug -> add printf -> recompile -> pray). Are there any guides on using WinDbg or another debugger to debug code that crosses managed->unmanaged boundaries? I'm not an expert on WinDbg. I tend to include such log statement right from the start, and feel it saves me lots of hassles. :) Luc Pattyn [Forum Guidelines] [My Articles] Voting for dummies? No thanks. X|

You're welcome. :) Luc Pattyn [Forum Guidelines] [My Articles] Voting for dummies? No thanks. X|

using application/ user settings in c# is at least as easy as properties in java. however, c# settings are serialized in xml, whereas properties are not.

I dont know dnsjava, but there are some functionality for DNS in .NET. System.Net.Dns xacc.ide - now with TabsToSpaces support IronScheme - 1.0 alpha 3 out now

>>would still involve a method invocation (albeit an empty one). You can mark the refactored code with the "ConditionalAttribute" eg: [Conditional("Debug")] public void DoStuff() { } This lets the compiler know that it should only _emit calls to that method if we are in debug mode_ So the method will still be present in release mode, but no calls to it will be present in the IL code. (And if your debug statements are output stuff only. then just use "Debug.WriteLine(text)" , those will also be removed in release mode) Blog: http://www.rogeralsing.com Projects: http://www.puzzleframework.com

I figured this problem out: http://ubuntuforums.org/showthread.php?t=781257[^]

This might be a different approach to the problem, but... What immediately comes to mind is the use of some custom attributes. You might also want to check out the Spring.NET framework. There's a lot you could do with some of the functionality in that framework. This very much sounds like a cross-cutting concern, for which aspect-oriented programming would be well suited. BW

I should mention that viewing the generated config file in Internet Explorer does not do any XInclude processing. In other words, the XML displayed is exactly that of the .config input file. Am currently trying a solution using ENTITY, will post fix if I find.