Archives

Archives / 2004 / January
  • ASP Classic weblog systems?

    I'm helping a friend on a website and .NET isn't available on that server. We'd like to add a simple blog system using Access as the data store. I was sure I could find something cheap or free, but I've been surprised that I haven't found anything I'm completely happy with. I've looked at BlogworksXML (no longer supported, but the install files can still be found), but it writes files out rather than writing to a database. I'm messing with UBlog, but the model's a bit different than what I'm trying to do and it's tough to make it fit. dBlog is promising, but it's Italian and I'm not. Am I really gonna have to take that trip down memory lane and write an ASP / Access blog system? Anyone recommend one?

    I'm looking for multiple users posting to a common feed - similar to the weblogs.asp.net, but I don't need all the neat features.

    Read more...

  • More fun with XSLT in VS.NET

    Jesse linked to a page showing how to set up XSLT IntelliSense for VS.NET. Doug Doedens has written an excellent article on how to install this, and then extend it with a VS.NET Macro so you can test XML / XSL transforms like you can in XmlSpy. Doug's posted some other really cool macros at C-SharpCorner, too - check them out.

    These guys have a schema you can use to add XSLT intellisense to your copy of VS.NET:
    http://www.fesersoft.com/dotNet/
    posted @ 1/23/2004 9:38 PM by Jesse Ezell

     

    Read more...

  • Music Keyboard that runs XP

    OpenSynth NEKO 64™

    Open Labs showed a music keyboard running XP Pro on standard computer parts at NAMM - the NEKO.

    “NEKO 64™ is so versatile it can virtually run any plugin or application designed for the Windows XP operating system including products from Steinberg, Native Instruments, Synapse Audio, IK Multimedia and many others!“

    Hmmm... so it's a pro quality keyboard blended with a buffed out dual Opteron system, comes with the .NET Framework installed and supports DirectX... mind races...

    Top end model is $8445, but the low end ones are mid-2K range (looks like that's the “bring your own monitor, computer keyboard, etc.“ model).

    Prizes to the first picture of one of these running The Regulator, SharpReader, or Snippet Compiler.

    [via Slashdot]

    Read more...

  • Intellisense Oddity?

    Intellisense for overridden methods shows both the base and the overridden method in the derived object, even though you can't actually call the base method from the derived object. Bug or feebleminded developer? You be the judge:

    Simple class which inherits from Object and overrides the ToString method:

    using System;
    
    namespace Test
    {
    class MainTest
    {
    [STAThread]
    static void Main(string[] args)
    {
    OverriddenObject oo = new OverriddenObject();
    Console.Write(oo.ToString());
    Console.ReadLine();
    }
    }

    class OverriddenObject : Object
    {
    public override string ToString()
    {
    return "Overridden" ;
    }
    }
    }

    Now for the (minimal) fun:

    1. Mouse over oo.ToString() - or just trust me, the tooltip reads: “string OverriddenObject.ToString() (+1 overloads)”.
    2. Odder still, if you backspace over and retype the open perinthesis that follows the ToString() to bring up the Intellisense, you'll see two methods. The signature for the second reads “string Object.ToString”. Now, this is no big deal, but to be really picky, this is wrong for two reasons - (a) it's not valid in this context. From where the cursor sits at “oo.ToString(”, it's impossible for me to call the “Object.ToString()” method. (b) It's a little misleading - let's say I decide that I want the Object.ToString() method, pick it from the dropdown, close the method call, and go about my business assuming I'm going to call the method Intellisense presented to me as one of my options. I've been mislead! Object.ToString() will never be called from oo.ToString(), since it's been overridden.

    Now, this seems pretty nitpicky in this example context. It's a bigger deal when you think of the base and derived classes representing business objects like ExemptEmployee derived from Employee, InternationalOrder derived from Order, etc.

    Is this (1) true and important (2) true and unimportant, or (3) untrue (as in I'm not understanding why Intellisense is showing what it does)?

    Read more...

  • MSDN Classes and Libraries Links

    Useful classes and libraries posted by the C# team on MSDN. Cool.

    Funny quote on the page:

    This page lists some useful classes that we've come across. Some are from Microsoft people and other are from non-Microsoft people, so don't complain if you use a class and your cat's hair falls out.

    You mean like this?

    Read more...

  • Code sharing sites - which?

    Chris's post reminded me of somthing I've been pondering recently - what's the best place to share code?

    I think the top three I've seen for collaborative development (whole projects) are these:
    GotDotNet Workspaces - seems okay, but some folks are mentioning source control and other problems
    SourceForge - lots of good stuff, nice web browsable cvs interface. lots of it is GPL'd, which can be - well, let's just say “a complication“.
    VaultPub - NKOTB?

    Some folks have been moving from GDN to SourceForge, others to Vault Pub.

    And for posting sample code, a utility class, etc.:
    Code Project
    C# Corner
    Weblog Article - Okay for small snippets, but can't attach a sample project

    I'm interested in feature comparisons, user experiences, etc. Thoughts?

    Read more...

  • [OT] If you didn't really "get" Matrix Revolutions...

    If you didn't really "get" Matrix Revolutions, this review may help.

    I have to say I was pretty disappointed when I saw this in the theatre. I missed all the wire work and bullet time of the previous two movies, the war against the machines was boring, and I felt the final showdown was a dud.

    To top it off, it didn't really make much sense.

    The above review at least explained what the heck went on.

    Read more...