יום חמישי, נובמבר 12, 2009
EDIT: As of version 9.3.2 of CodeRush functionality similiar to that provided by this plugin is provided in the core product and support and builds for this plugin is discontinued... If you need assistance for earlier version of CR, just leave a comment and I'll get back to you.
Instead of posting a new a post every time a new build of CodeRush (and the plugin) becomes available, I’ll start to post the binaries here by updating this post. If you are interested in the source code, you can get it here. If you want a walk-through of how the plugin...
יום שלישי, נובמבר 10, 2009
Since I said in the last post that I would make the source available if there was interest, I’m doing that now.
The project structure is as following
All of the code for accessing the compilation service is in the GoogleClosure project. Initially I didn’t have a Winform project. I split the projects for this post, realizing that some people interested in the code might not have CodeRush.
The GoogleClosure project also contains the UI in a...
יום ראשון, נובמבר 8, 2009
2 hours later…
In this screenshot you can see some compiler statistics. (Yes, you can use the compiler service as a pretty-printer or...
יום ראשון, אוגוסט 30, 2009
For convenience, here are the binaries for the Navigate to Implementation CodeRush plugin. It is built against CodeRush 9.2.4. A detailed overview of the functionality of the plugin can be found here. The source code is available on Google Code: http://dxcorecommunityplugins.googlecode.com/svn/trunk/CR_NavigationContrib
יום חמישי, דצמבר 4, 2008
This is the last post in series on developing the navigate to an implementing method plugin. Here are links to the previous posts, part 1, part 2 and part 3.
Just to recap, the goal of the plugin is to be able to position the caret (what most people call the cursor), on a method call on an interface variable and navigate to specific implementations of the method.
In this post we’ll look at how we navigate to the correct method.
The call to navigate is made when the navigation provider (part of CodeRush) receives the navigation event.
יום שני, אוקטובר 20, 2008
In this part we’ll look at the Implementors class. As we described in part 1, a the Navigation Provider will call into our plugin twice. Once to give us the chance to make our plugin available to the user and a second time if the user selected one of our menu items. When the Navigation provider raises the event CheckAvailability we need to do two things.
Check if this plugin is available in the current context.
Alter the menu displayed so our options are available to the user.
In step one we will first check if we are positioned...
יום ראשון, אוקטובר 19, 2008
In the previous post we just defined what we want the plugin to do. Let's start to walk through the process of creating a plugin with CodeRush.
There's some plumbing that needs to be done every time you create a plugin and that is not directly related to the functionality of the plugin. For this part I'll just point you to a plugin tutorial by Mark Miller. Since our plugin will handle navigation it seems natural to hook into the Navigation provider system provided by CodeRush.
Open the plugin designer
The NavigationProvider does not show up in the toolbox by default...
In a post last week I mentioned a shortcoming of CodeRush navigation capabilities. On Friday (we don't work Fridays here) I decided that instead of sitting on my hands and complain I'll try to do something about it. I'll write a plugin for CodeRush that does this. I've written a few CodeRush plugins before, but I have never found the time to make something that I feel I can share with others. Not that the current implementation is a master piece, but it is small simple and works for what I want it to.
Because in my opinion it is...