What steps will reproduce the problem? 1. Install CR_Documentor 2.6.1 for Visual Studio 2008 2. Start Visual Studio 2008 3. Open a source file with comments

What is the expected output? What do you see instead? When I click on a comment section in the source, Unhandled .NET exception dialog pops up. I click continue and the comments are rendered normally in a tab. The unhandled exception dialog shows up subsequently every time I click or change to a different comment section (figuring every time CR_Documentor renders)

What version of the product are you using? On what operating system? CR_Documentor 2.6.1 on Visual Studio 2008 Pro/Windows XP Pro SP3

Please provide any additional information below. Unhandled .NET exception dialog pops up with following information:

System.NullReferenceException: Object reference not set to an instance of an object. at CR_Documentor.Diagnostics.Logger.<>c__DisplayClass6.<InitializeLoggingDelegates>b__0(String message)

DevExpress changed the logging interface in CodeRush/DXCore 11.2.8, which is what caused that issue. I cut one final version of CR_Documentor for DXCore 11.2.7 (CR_Documentor 2.6.1) and then started supporting 11.2.8 after that.

Problem is, I no longer have a test system for VS2008 or Windows XP, so I can't directly support any of that configuration. I haven't been able to support VS2008 for almost a year now. However, it sounds like you have a version of CodeRush/DXCore installed that's 11.2.8 or later, yielding this exception.

You can try version 3.1.0.1 of CR_Documentor to see if that fixes the problem. I say it's only VS2010/2012 because I started compiling against .NET 3.5 and VS2008 didn't (at that time, at least) work with .NET 3.5 plugins. That might be a CodeRush thing that they enabled; I don't know.

Point being... you're sort of in this weird spot where you've got a new(er) version of DXCore but really old VS/Windows and it's a combination of software I can't test or support.

If one of the built versions of the plugin doesn't work, you can always get the source and try back-porting it for VS2008. I don't know exactly what that would entail; that'd be "an exercise left to the reader." I can't really do anything at this point to fix it. Sorry.