Here's the text of e-mail conversation

tried to reproduce the behaviour in a small test application, but the refactoring works correct there.
So it seems to be only a problem in more complex environments. Unfortunately i'm not allowed to give you the source of our project. So i can only tell you what i have done in detail.

We are developing a multi tier application with a WindowsForms client which communicates with the server via .NET-Remoting.
The soulution consists of three projects (Client, RemotingInterface and server). All projects references the dll of a library with utility functions for error handling. The complete application has around 4000 classes.

We had defined some exceptions in the RemotingInterface which i had to move to the library. First i used the MoveType refactoring to move the exceptions to the namcepace of the error handling utility funtions and then i removed the exception classes from the project and added them to the library project.

What i have noticed is, that the refactoring of the last class lasts extremely long (around 30 to 50 seconds instead of 3 to 5 seconds for the other classes). And the other thing i have found is that the problem is reproducable. I have checked out a recent version from our repository and tried the refactioring again with the same result.

I will attach my test application to this mail so that you can see the structure of our solution. Maybe this will help you a little bit.

Regards
Klaus


Support - Andrey Serebryansky wrote:



Issue was closed