Steve Cothern

Show:

What's happening?

  • Followup: RE: Working toward 1.2...

    Well, the setup stuff was instructive from the standpoint of looking at the registry settings. I noted that the LoadBehavior DWORD flag (under the NAntRunnerAddIn.Connect key) is set to 1 in the setup project, and was 0 in my registry. I changed it to 1, and Voila, I have a persistent NAntRunner! Interestingly, the value was subsequently 3, so it appears there may be some error checking requi.

    2006-05-05 20:56:14 UTC in NAntRunner

  • Followup: RE: Working toward 1.2...

    I agree -- the code is tweaky. I think this is in large part due to the fact that is has been "tinker-toyed" to some extent -- assembled from the ProcRunner CodeProject submission, and bits and pieces of the MS Automation Samples, with a dash of deployment project thrown in for spice! No dis intended to the authors -- I really appreciate the work that has been done so far. I have...

    2006-05-05 17:44:58 UTC in NAntRunner

  • Followup: RE: Working toward 1.2...

    I thought I remembered it working that way... Whether I tab-dock NAntRunner, or tile-dock it, it does not come up in that state again when I re-open VS (i.e., it comes up as a floating window). In addition to this behavior, it seems to be inconsistent in terms of its position and size information--I can get it to "remember" where it was and its previous size (in floating mode) by...

    2006-05-05 15:51:49 UTC in NAntRunner

  • Followup: RE: Working toward 1.2...

    Hi Nick-- I am not seeing this. Maybe I don't understand what you mean. Here's what I did to try and set it up: (1) open vs 2003 (2) using either the start page or the File|Open mechanism, I open my project. I have no file in the project open from a previous session. (3) Note that at this point I do NOT have the NAntRunner toolwindow open, even though it was open when I last...

    2006-05-04 19:06:14 UTC in NAntRunner

  • Followup: RE: Working toward 1.2...

    Hi J, One comment on your fix for the path bug. Correct me if I am wrong, but this appears to be a VS 2003-specific fix; i.e., the ref to the VS71COMNTOOLS env variable will not work in 2005 for the same reason the .reg file has problems w/2005 (see my comments in the Open Discussion|Visual Studio 2005 support thread). I'm wondering if we shouldn't handle this in an app config file or...

    2006-05-03 21:40:21 UTC in NAntRunner

  • Followup: RE: Ping

    Hey Nicolas, Glad to see you're still around -- don't be a stranger! best regards, Steve.

    2006-05-03 16:03:43 UTC in NAntRunner

  • Followup: RE: Making Modifications

    Hey J -- Checked in the changes; VSS no longer yelps due to Perforce refs in the proj files. I also modified the Connect class to add the NAntRunner icon to the window when docked. cheers, Steve.

    2006-05-02 03:01:45 UTC in NAntRunner

  • NAntRunner

    jstevenco committed patchset 6 of module nantrunner to the NAntRunner CVS repository, changing 6 files.

    2006-05-02 02:48:21 UTC in NAntRunner

  • Followup: RE: Making Modifications

    Hey Jeremiah, Thanks for the update. I spent a little time this morning getting hooked up via TortoiseCVS. I'll throw this open to "all" but for the mo' looks like you and me: any objections to getting rid of the Perforce references in the project files? Makes opening the solution a bit less painful. I've done so, and I'll checkin the updates if no one objects. cheers...

    2006-05-01 20:25:08 UTC in NAntRunner

  • Followup: RE: Ping

    Woops -- my bad; seems to have been created a while ago -- I just never noticed it.

    2006-04-26 17:20:31 UTC in NAntRunner

About Me

  • 2006-04-12 (4 years ago)
  • 1500987
  • jstevenco (My Site)
  • Steve Cothern

Send me a message