SharpMT

SharpMT 3.0

9 Comments

SharpMT 3.0 is good to go.

Download SharpMT: EXE | MSI

View SharpMT FAQ: FAQ

Download: .NET Framework, version 2.0 (required to run SharpMT 3)

What’s new? From the product announcements from Beta 1, 2, and 3:

.NET Framework 2.0: More for me than for you, but you’ve benefited from it too. A complete rewrite as the application was ported, which should include the use of some new controls on the way. For example the menu and toolbars are now common controls within VS2005. Other little things here and there; I also got to clean up a good deal of the code on the way so things should be tighter in this release.

RSS Aggregator support: Somewhere along the line we picked up support from within FeedDemon which is neat.

Bookmarklet support: This is something people clammered for but no one ever told me if I got it write with Beta 2 and Beta 3. What you see is what you’re getting now :)

Hey… it’s new, it’s shiny, it still supports spell checking… how wrong could it be?


9 thoughts on “SharpMT 3.0”

  1. Haven’t downloaded this yet, but am running a beta of version three, and I have a question/feature-request: Does this version support MT 3.2’s basename field so we can change the basename before it goes online?

  2. Beats the hell outta me: I haven’t seen the basename field :)

    Is there a field on the MT forms that needs to be filled out when posting or something?

  3. got this long error trying to run SharpMT. Windows 2000 with SP4 and .NET 2.0.

    See the end of this message for details on invoking

    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************

    System.NullReferenceException: Object reference not set to an instance of an object.

    at SharpMT.MainForm.DrillDownEdit(Control control)

    at SharpMT.MainForm.genericToolStripMenuPopup_Click(Object sender, EventArgs e)

    at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

    at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

    at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

    at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

    at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

    at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

    at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

    at System.Windows.Forms.Control.WndProc(Message& m)

    at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

    at System.Windows.Forms.ToolStrip.WndProc(Message& m)

    at System.Windows.Forms.MenuStrip.WndProc(Message& m)

    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    ************** Loaded Assemblies **************

    mscorlib

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.50727.42 (RTM.050727-4200)

    CodeBase: file:///C:/OSW2K/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

  4. Randy – I’m getting the same JIT error under W2K. It seems to work fine under XP. Any ideas?

    Thanks!

  5. What’s Windows 2000? OK, OK, sorry, bad joke.

    Can you email me the call stack? Also, can ya tell me if you have a draft open already, before you see the error?

  8. Bloody feckin’ shit!

    This is the resurfacing of an old bug: I know I’ve fixed this once before, but it looks like it returned to my code base at one point or another… too many rebuilds of the same version number, I’m guessing. So it’s looking like this happens when there are no drafts open in the main window… no big deal as most people will have a draft open at all times, right? Wrong! It impacts new users worst of all – a criminal sin for software.

    Upgraders from 2.x won’t see this particular problem on their first run, as settings move forward…

    As a temporary workaround, you can use the ALT key to get around the menu – which is really unacceptable – and I *will* have a fix some time later tonight, in 3.1 – I had made a couple of changes in private builds for people so those are going to get rolled up into this.

Comments are closed.