Tony Alves
Flex, .Net, and Fluorine

BlogEngine.NET comes to Life

Saturday, 29 September 2007 18:00 by talves

After months of looking at blog applications, I have decided on BlogEngine.NET.  This decision is based on many things, but mainly for 2 reasons.

1. Open Source .NET project.

2. The data can be stored in XML.  No database is required and there is the opportunity for it to switch over later if  your blog becomes too large for XML.

Other reasons were considered.  Other blog features are missing, but I do not use them and they will be added later anyway.  The developer has a reputation for having very clean code and is dedicated to keeping the code concise and clean.  The code also adheres to some best practices methods you would not normally see in .NET projects which is also promising.

Setup

BlogEngine.NET could not have been any easier to set up.  I literally had it running in less than 5 minutes.  Of course, I am a .NET junkie and have an advantage, so the layman could be up in less than 1 hour at worse case scenario.

BlogEngine.NET

You can find BlogEngine.NET on the official website. Here you'll find tutorials, documentation, tips and tricks and much more. The ongoing development of BlogEngine.NET can be followed at CodePlex where the daily builds will be published for anyone to download.

Currently rated 3.7 by 12 people

  • Currently 3.666666/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Tags:  
Categories:   BlogEngine.NET | .NET
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

ArgumentError: Error #2004

Wednesday, 19 September 2007 16:50 by talves
ArgumentError: Error #2004: One of the parameters is invalid.

I hope this will help you out there before you spend too many hours on this one.

Issue that caused the error:
Making a remote call using a RemoteObject that returns back a strongly typed object. The call is made and the Error is triggered before you can capture it in the debugger. I thought I was losing my mind. Everything is exactly the way I have done remote calls a hundred times.

remoteObject.SomeMethod();
SomeMethod() returns a strongly typed class object.

Solution and reason for the error:
Make sure you have an instance of the object referenced in your project. The object is not linked into your .swf upon compiling the project, because there is not a reference to the object anywhere in the project, so the RemoteObject call cannot find the class. What a simple solution, but what a non descriptive error. Now that I read the error it makes a little more sense.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Tags:   ,
Categories:   Flex | .NET
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed