Here are the known issues for v0.6. I’ll be doing my best to solve these quickly. If you find life unbearable with any particular issue, comment this post or write at the forums and I’ll do my best to release a fix ASAP.
- Comments in member declaration are not supported. For example:
public void Foo() // comment
{
}
– or –
public /* comment */ string Foo
{
get
{
return “foo”;
}
}
- (Updated: Fixed) No support for #ifdef blocks.
- (Update: Fixed) Attributes with line breaks inside are split. for example
[ Attribute( "I", "Cause",
"Problems" ) ]
public void Foo() { }
- (Update: Fixed) Strings containing single “{” or “}” characters drive the construction mechanism nuts. for example:
public void Foo() { string whoops = “}”; }
- Comment sections that start with “(” cause inconsistent behaviour. for example:
///
/// ( Whoops.
///
- Multiple fields declared in a single line are not recognized as fields (meaning, they are left out of Field regions), For example:
public string a,b;
Note: Multiple fields declared in single line is not recommended. Read section 5.1 from this style guide.
- (Update: Fixed) Code inside comments is interpreted as actual code.
- When the “Auto-Collapse” feature is turned off in the Visual Studio add-in, The cursor does not follow selection after Regionerating.
No Responses to “Known Public Beta Issues”