addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [dotnet-120] CodeRush Plugin Debug

From: Noah B.
Sent on: Thursday, October 8, 2009 10:12 AM
Thanks to Steve and James for the info.  The DnrTV episode was what actually got me pumped up about creating this plugin originally, and while the vid has some great information (and some cool little tidbits that probably would have taken me a lot of time to figure out) it also lacks a lot more.

I'll take a look at some other links and keep at it.

In regards to debugging, this is the response I got from DevExpress:

Hi Noah,

Please do the following:

1) Open your plug-in the project's properties.
2) Go to the "Build" tab and change the "Output path" to the folder, containing Community plug-ins. By default, the following folder is used:

%userprofile%\Documents\DevExpress\IDE Tools\Community\PlugIns\

3) Go to the "Debug" tab, in the "Start Action" group, activate the "Start external program" option, and specify a path to your devenv.exe (C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe).

Hope this helps.

Thanks,
Vito

Just what I was hoping not to do.  I responded to him:

That's what I was afraid you were going to say. This means that my other instances of VS will have this plugin that could be potentially really buggy.

Here's what I suggest for future releases:

There should be a flag that allows me to load plugins from an arbitrary directory. Then when I build I can run VS with this flag specifying my build output directory. In this way I can isolate the test plugin from the rest of my day-to-day coding activities.

- Noah

FYI.  So for now debugging a CodeRush plugin has side effects :(.

- Noah

Steve Bohlen wrote:
I recommend the following resources for getting started with this (not in any particular order)...
  • Mark Miller's blog
  • Rory Becker's blog
  • the http://dxcommunityplugins.googlecode.com site (for 50+ examples of other OSS plugins)
  • the dnrtv episode referenced already as well as a few other dnrtv episodes (search the past episodes list for 'mark miller' and you will find them)
  • my own blog (ref. in my e-mail sig) for some high-level concepts about DX/CR plugins (not much code posted there)
You can google all of the above resources to find them easily.  As a developer of several of the OSS plugins found on the DXCommunityPlugins site as well a few that aren't (like http://dxsourceoutliner.googlecode.com ), I have to agree that the dearth of any decent documentation is a *huge* impediment to widespread plugin development by CodeRush users so I feel your pain acutely, trust me :)

But its a huge productivity boost to anyone trying to develop tools for Visual Studio so you should certainly *try* to stick it out until you master it.

Best of luck~!

Steve Bohlen
[address removed]
http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen


On Wed, Oct 7, 2009 at 4:11 PM, James Curran <[address removed]> wrote:
On DotNetRocksTV, Mark Miller had a tutorial on building a CodeRush plug-in

http://www.dnrtv.com/default.aspx?showNum=5


On Wed, Oct 7, 2009 at 3:48 PM, Noah Blumenthal
<[address removed]> wrote:
> I'm trying to write my first CodeRush plugin for some MVC stuff that I think
> would be helpful.  I haven't got very far -- just created a new plugin,
> added a CodeProvider and clicked F5 to debug so I could play around with
> QuickWatch and try to see where I'm going with this.  However, F5 opens a
> new Visual Studio instance but my plugin is not loaded.
>
> I was thinking maybe I have to set the build output directory to my VS
> plugin directory, but I'd really rather not because I don't want my other VS
> instances to have an in-development plugin.  How should I be doing this?
>
> CodeRush is a great tool but there is way too little plugin documentation!
>
> Thanks,
> Noah
>
>
>
>
> --
> Please Note: If you hit "REPLY", your message will be sent to everyone on
> this mailing list ([address removed])
> This message was sent by Noah Blumenthal ([address removed])
> from New York .NET Meetup Group.
> To learn more about Noah Blumenthal, visit his/her member profile
> To unsubscribe or to update your mailing list settings, click here
>
> Meetup Support: [address removed]
> 632 Broadway, New York, NY 10012 USA



--
Truth,
   James



--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
http://www.meetup.com/NY-Dotnet/
This message was sent by James Curran ([address removed]) from New York .NET Meetup Group.
To learn more about James Curran, visit his/her member profile: http://www.meetup.com/NY-Dotnet/members/6362719/
To unsubscribe or to update your mailing list settings, click here: http://www.meetup.com/account/comm/
Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA






--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Steve Bohlen ([address removed]) from New York .NET Meetup Group.
To learn more about Steve Bohlen, visit his/her member profile
To unsubscribe or to update your mailing list settings, click here

Meetup Support: [address removed]
632 Broadway, New York, NY 10012 USA

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy