Home

Badly formed XML comment

Just in case anyone else comes across this, I was just browsing the generated MyExtensions.FW46.xml file, which contains all of the extracted code comments for my MyExtensions, and noticed that a number of the comments show up as badly formed:



The problem in all of the cases was including generic types and specifically the angle brackets within the XML comments. The fix, according to StackOverflow seems to be to use curly braces instead.

I guess a nice feature for LINQPad would be to flag any errors on save of the MyExtensions file so that I could fix them at that point.
Sign In or Register to comment.