views:

52

answers:

0

I am distributing with VS 2008 .NET and obfuscation.

I am up against the frustrating problem of not being able to see line numbers in stack traces.

Whilst there are workarounds eg. http://stackoverflow.com/questions/1328836/include-line-numbers-in-stack-trace-without-pdb

when the stack traces are returned (holding PDB files locally etc) this is not what I am looking for.

I am looking for a way to get the line number embedded some way at compile time.

In my view this is a major oversight on the part of MS. There is no logical reason why we should not be able to opt to include a macro for the line number at compile time. In my view this is a major oversight of MS which is leading to major headaches for developers all over the place.

I have no experience whatsoever of writing add-ins or mods for Visual Studio and am calling on the community for any ideas, specifically, any way to get the line number included at compile time so that we can deliberately output it to logging with our stack traces in exception reports.

Its such a simple feature that the builder could easily do. We used to have something like double-underscore-LINE-double-underscore in C++.

Surely we can find a way to mod VS.NET in order to get this information at compile time for .NET apps.