Spell checker fails after <code source="..." region="..."> tag

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use the code tag in your comment with the sandcastle attributes source and 
region.
2. Have spelling mistakes after that line.
3. Agent Smith doesn't check the errors after that line.

What is the expected behavior? What do you see instead?
I expect the spell checker to continue to work

What version of ReSharper, Visual Studio and Windows do you use?
5.1

Please provide any additional information below.
Sandcastle allows code blocks to be pulled in from a #region of a source file 
see:
http://www.ewoodruff.us/shfbdocs/html/7f03ba39-09f8-4320-bdbd-ed31a3bd885f.htm

Example:
/// A bitt of code with badd spelling where errors highlighted
/// 
/// <code source="MySampleCodeFile.cs" region="Example"/>           
/// 
/// The resst of the comment block / possibly file doesnt get spel checked :(

Original issue reported on code.google.com by kri...@gmail.com on 1 Jul 2011 at 10:24

[GoogleCodeExporter]

As far as i can tell, it's not the "source" or "region" property that breaks 
it, it's the lack of content. Using:

/// A bitt of code with badd spelling where errors highlighted
/// 
/// <code source="MySampleCodeFile.cs" region="Example"></code>         
/// 
/// The resst of the comment block / possibly file doesnt get spel checked :(

works correctly

Original comment by cds...@gmail.com on 9 Jan 2012 at 12:27

• Changed state: Accepted

[GoogleCodeExporter]

Thanks

Original comment by kri...@gmail.com on 9 Jan 2012 at 12:30

[GoogleCodeExporter]

BTW I'm leaving it open - i'll try and work out why the < /> version breaks.

Original comment by cds...@gmail.com on 9 Jan 2012 at 12:32

[GoogleCodeExporter]

Thanks so much :)

Original comment by kri...@gmail.com on 9 Jan 2012 at 12:40

[GoogleCodeExporter]

This is now fixed in 1.5 beta 4.

Original comment by cds...@gmail.com on 15 Jan 2012 at 12:38

• Changed state: Fixed