There's no tooling for this refactoring; use a careful text search-and-replace.

By on 9/28/2010 12:01 PM ()

Any document/direction for build the refactoring tool by ourselves?

By on 10/3/2010 11:26 PM ()

My advice would be to wait for the open-source release of the compiler, which is likely to come with more help for such hacking.

If you're extremely eager, then have a look at vs\service.fsi (which is the interface out the compiler consumed by the Visual Studio language service). The TypeCheckInfo.GetDeclaration* methods provide the functionality needed for "Go To Definition", which navigates from 'use' to 'source'. Refactoring needs to go the other way (a la Find All References). There's no API for this, but you can e.g. walk every identifier and GTD to discover FAR info. Thus renaming "foo" 'here' means walking every other "foo" in the program, doing a GTD, and if it lands 'here' then renaming it too.

By on 10/4/2010 9:28 AM ()

So there's still not a schedule for the compiler to be open source released?

So if I want these functions now, I must do these? Or is there any alternative, better selection? Anyway.

By on 10/29/2010 2:44 PM ()

Is there some alternative design in F# could replace the rename refactoring function in VC#?

For example type alias name? As I know there are not.

By on 10/29/2010 4:51 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper