Archives

Archives / 2004 / February
  • Code theft: Codease uses my LLBLGen 1.x sourcecode as if it is theirs!

    This morning I found out that CodeAse, sells a tool, CodeAse 2.0, which is just LLBLGen 1.x but with different screencolors. LLBLGen 1.x is BSD licensed, but that doesn't mean you can simply rebadge it and sell it as if you wrote it! The BSD license clearly states you have to mention the original author of the work you use in your software in the About box and documentation. This didn't happen.

  • Subversion: unbeatable sourcecontrol.

    I'm now almost done reading the docs of Subversion, and I can only say: this is open source done right, and when open source is done right, it's unbeatable by any software vendor. The system breaths quality, well thought out design and passion for software engineering. The documentation is very good, it reads like a novel. The win32 explorer plug-in (TortoiseSVN) is also very good, and offers a rich quality of services. Subversion has two more things to offer: it's free and it runs on a wide range of platforms (Win32, *BSD, Unix, Linux, MacOS X).

  • Private classes and full type name

    This morning I was checking how my Xml serialization code was doing and I stumbled upon a phenomenon I hadn't seen before: the FullName property of Type will return a '+' instead of a '.' when the class is a private class. For testing I had defined some private classes and I set a property to an instance of one of those classes. My Xml serialization code will then add an Xml node with attributes for Assembly name and Type name. When examining the produced Xml, I saw:Type="DALTester.AdapterTester+OrderEntityValidator".

  • VB.NET stupidity

    Consider the following enum definition (which is defined in a C# assembly)

    public enum EntityState:int
    {
       New,
       Fetched,
       OutOfSync,
       Deleted
    }

  • Microsoft Support, Round 3, the flaw of the Hotfix

    Julien writes:

    PSS is the first line of contact for issues and if you contact them and tell them about your issue we will look into it. If we have a hotfix available for it, even if the SP is not yet released, we will provide you it. If we don't have a hotfix and your issue doesn't have a good workaround, we will make a hotfix for you (that's how they get done usually).

  • Microsoft Support, Round 2!

    Jeff writes as a reply to my previous blog about Microsoft Support:

    I found an actual bug in the framework (one of the RewritePath() overloads) and had a nice exchange started via the online support ticket system, finished by a member of the .NET team. It's one of three times I've had to contact MS directly, and every time my problem was resolved or at the very least explained. At the company level, I think they do a fine job.

  • Jimmy Nilsson on AOP

    Jimmy Nilsson blogs about AOP, or Aspect Oriented Programming.His article combines some different insights on the matter, good links to articles about AOP and is a good starting point for the people who have ignored AOP for a long time and find this the right moment to get started with AOP and what the fuss is all about.