Lambda expressions -- often refer to non-renamed types

There may be another issue underlying this one (lambda expressions turn into 
private classes, yes?), but if I have a fairly complex lambda expression such 
that it's capturing variables, etc., often things it references will not be 
renamed. For example, if my complex lambda references 
AudioManager.Instance.SomeMethod(), Instance and SomeMethod will never get 
renamed to the obfuscated type.

To work around this I have had to add quite a lot of SkipMethod tags, but it 
would be nice if Obfuscar would instead be smart and rename these methods as it 
should.

Thanks

James

Original issue reported on code.google.com by xoc...@gmail.com on 3 Apr 2011 at 5:41

ossecsoft / obfuscar

Lambda expressions -- often refer to non-renamed types #43