History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: RSRP-30915
Type: Usability Problem Usability Problem
Status: Open Open
Priority: Normal Normal
Assignee: Sergey Shkredov
Reporter: Vladimir Reshetnikov
Votes: 0
Watchers: 1
Operations

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

Type becomes invalid after move

Created: 01 Nov 06 13:38   Updated: 08 May 08 16:03
Component/s: Refactorings - Move Type
Fix Version/s: Future Versions
Security Level: Everybody (All jira users)

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

Build: 300


 Description  « Hide
When I apply 'Move' refactoring to a type in 'Type Hierarchy' window, it becomes invalid in this window.

 All   Comments   Work Log   Change History      Sort Order:
[ Permlink | « Hide ]
Ilya Ryzhenkov - 01 Nov 06 13:38
Move where?

[ Permlink | « Hide ]
Vladimir Reshetnikov - 01 Nov 06 13:44
Move to another namespace.

[ Permlink | « Hide ]
Ilya Ryzhenkov - 01 Nov 06 13:48
When type is moved neither element pointer, nor CLR name makes it possible to restore type element. Thus, type element is lost.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.10-#260) - Bug/feature request - Contact Administrators