[210] Move Type is horked

I'm trying to move a couple of files in the project I'm working on. This isn't as easy as Resharper makes me think it is.

I've tried moving a class named EPR.TabControl (inheriting windorms.TabCOntrol) to EPR.Controls.TabControl.

- All references to the windows Tabcotnrol were moved aswell (which caused nuemrous errors)
- The constructor call to EPR.TabControl wasn't changed which caused more errors.

Trying to move another class to the new Controls namespace caused yet more errors. I've sumbitted them all. The last exception resulted in a complete disappearance of VS 2003 from my screen (no dr watson, no nothing).

2 comments
Comment actions Permalink

I tried to reproduce it but could not do that. Is it reproducable for you?
For example, if you take your TabControl class and move to some other namespace.

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'm trying to move a couple of files in the project I'm working on.
This isn't as easy as Resharper makes me think it is.

I've tried moving a class named EPR.TabControl (inheriting
windorms.TabCOntrol) to EPR.Controls.TabControl.

- All references to the windows Tabcotnrol were moved aswell (which
caused nuemrous errors) - The constructor call to EPR.TabControl
wasn't changed which caused more errors.

Trying to move another class to the new Controls namespace caused yet
more errors. I've sumbitted them all. The last exception resulted in a
complete disappearance of VS 2003 from my screen (no dr watson, no
nothing).



0
Comment actions Permalink

I uninstalled 210 as project pressure is too high at the moment. It happened twice to me till now, so it wasn't a one-off issue.

I'll try to find some time in the next week.

Jesse

0

Please sign in to leave a comment.