Before I reinvent the wheel trying to make it rounder this time (again), I find myself having to download and old copy of our repo and go down the rabbit hole of why our current version gives a different value than the version that worked last week, or last summer.
I have a tool that compares a solution or a project for code differences, but if something exists that logs the values of local variables in methods, events, etc. at runtime and where they change this would save me so much time in those 'What did I mess up trying to fix something else' situations.
Perhaps an extension isn't the way to go if there is Verbose logging or something that can be turned on?
And last question before I dive in and start developing (actually adding this to my to do list #1107; I am on #12 now), most of my extension development has been in Text manipulation of the current document. Is the Env.DTE the same object to interact with for a runtime logging situation, or is there something different?
I kind of feel like I did with my first package development; 'Where do I start', except for now I know how to add a Tool Window and create a UI, but I have never dived into the deep end of run time fun time, so could someone point me in the right direction or approach to what's possible with Visual Studio at interim variable values changing.
I didn't write my current work project, and I am slowly refactoring things to be read only properties that can be exported, but current things like keeping my clients' clients happy take priority over making my life easier.
And I don't know if this matters or not, but the app I am referring to is a C# MVC application.
Thanks for any advise, and I don't know if this was the best place to ask, but I know someone here has to know more than I do about this subject.