History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-44079
Type: Bug Bug
Status: Open Open
Priority: Normal Normal
Assignee: Sergey Shkredov
Reporter: Greg Law
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
ReSharper

Encapsulate field in nested class

Created: 24 Jun 07 00:59   Updated: 05 Feb 08 20:35
Component/s: Refactorings - Encapsulate Field
Fix Version/s: Future Versions
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

Build: 468


 Description  « Hide
When encapsulating a field in a nested class or structure that contains the same name as a property in the parent class, ReSharper complains that the name conflicts. As an example, given this class:

public class A
{
private int _field;

public int Field
{
get { return _field; }
set { _field = value; }
}

private struct B

{ internal int _field; }

}

Attempting to encapsulate B._field with a property named Field results in the message "Conflict on property A.Field" even though the names do not conflict.



 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.