Well, as promised on this fantastic 4th of July weekend I’m delivering everyone a great new version of WWWinamp

Mostly a bug fixer with some improvements to make it easier for people creating their own scripts! There are several users active here on my blog who are creating AJAX enabled skins and it was confusing the rules as to which files were passed to the Scripting Engine and which files were just treated as is.

Well, the rule of thumb in previous versions was that if the file was consided to have a MIME type of “text/html”, it would be sent to the Scripting Engine. This pretty much meant only *.htm and *.html files. At users requests, I’ve added a new configuration key to the WWWinamp.config file (WWWinamp.HTTP.ScriptFiles) which allows users to list which files are actually passed to the Scripting Engine.

Also in this version, I fixed an issue in the WWWinamp.config file which would keep the WCF service from starting.

Because of these changes, I suggest everyone use the WWWinamp.config file packaged with this build and just set back up your default configurations.

If you don’t feel like updating your configuration file.. well.. your WCF service just won’t work and WWWinamp will default back to using “text/html” MIME typed files as scripts.

Here’s the full changelog:

• [HTTP] Better handling of malformed HTTP Requests
• Added more user friendly help to some of the most commonly reported errors
• Added ability to specify file extensions that are sent to the Scripting Engine
• Increased performance of the Scripting Engine
• Fixed issue with WCF endpoint being misconfigured in the WWWinamp.config file

Cheers!

WWWinamp v4.2 Build 3109 – Download (60k)

This version of WWWinamp requires that you have the Microsoft .NET Framework 3.5 installed. You can get this from Microsoft.com by clicking here.

I’m calling it beta because a -lot- has changed behind the scenes and I did my best to test every feature but I might have missed a few bugs here and there. If you’re not comfortable running unstable version of software, then I suggest you install the previous release of WWWinamp v4.1 Build 2809. You can get it from here.

What’s new in this version of WWWinamp?

• [HTTP] Recoded processing of inbound HTTP Requests
• [HTTP] Fixed Defect #46: Processing HTTP Auth header even if one isn’t present
• [WCF] Small Optimizations
• Requires Microsoft .NET Framework 3.5
• Autoupdate Checks for new release on startup of WWWinamp (can be disabled in config)
• Minor UI Fixes

This version of WWWinamp is mostly a code cleanup and conversion to the .NET Framework 3.5. The source code now weighs in at a 300+ lines of code lighter than the previous version, while still maintaining the same functionality. I’m currently working on a Silverlight skin for WWWinamp which interfaces with the WCF endpoint for greater control and seamless use. Expect that to be out in the next month or so… well, perhaps longer I’m not too good with graphics and UI stuff, so I’ll do the best I can.

I also took the time and added a lot of comments to the WWWinamp CONFIG file. This should help users figure out what each configuration option means and their different settings. Hopefully this should help lower the amount of e-Mail I get from people who are getting errors because WWWinamp isn’t configured properly

Again, this is a BETA version and might not work 100% properly… it could have some personality But I believe it’s stable enough for release.

Share and enjoy!

WWWinamp v4.2 Build 2948 – Download (56k)

The issue that I ran into was I wanted to log these messages not to the file system, but to the database. Microsoft provides for this in allowing people to create custom Trace Listeners. After some heavy Googling I was able to find this article on MSDN which describes a method in which you would be able to create a custom Trace Listener. Using the code from this article, I was able to boil it down to a simple code shell which anyone could take and use within their WCF application.

This is very helpful for people looking to capture and log the incoming and outgoing SOAP messages to their WCF application without having to create a custom dispatcher. On top of that, creating a Listener provides a drag-and-drop assembly you can use on any future project you might create.

The code for this project can be found here (ZIP, 5.4k). The solution was created using Visual Studio 2005.

Cheers!