WWWinamp v4.1 Build 2809
10 September 2007Hello Everyone!
The latest build of WWWinamp is good to go. I’ve been trying to expand out the WCF Endpoint to include as much information to the client as possible. This should allow a remote application access to every resource that WWWinamp has available locally.
WWWinamp v4.1 Build 2809 includes the following fixes/changes:
- [WCF] Added WWWinampGetStatus() Method to retrieve information on WinAmp and the current file
- [HTTP] Fixed script parsing issue when a file contained multiple HTML comment tags
- [HTTP] Added optional Google AdWords to help support program
- Minor UI Fixes
One of the small changes to this version is a small Google AdWords banner on the playlist screen. This is an optional script tag which can be removed. Leaving in this small banner will help support WWWinamp.
I’m also going to release an updated WWWinamp WCF Client Example program which includes the additional functionality which is included in Build 2809.
Again, I ask users of WWWinamp to submit their Error Logs so we can make WWWinamp a better product!
Cheers!
WWWinamp v4.1 Build 2809 - Download (57k)
UPDATE: The new WCF Example Client can be found here. It includes examples on how to use the new method WWWinampGetStatus() as well as a few bug fixes. The C# source code for this example is provided. For development environment prerequisites and setup help, please read this post.
2 Responses to “WWWinamp v4.1 Build 2809”
October 1st, 2007 at 6:07 am
I’m trying to get this app running, and am just plain confused with what to do. I setup the xml file, but I continually get errors when trying to run it. I tried an older build and managed to get it running, but could not pull anything up on a web page. Is their some kind of faq for this?
October 1st, 2007 at 6:52 am
There isn’t a WWWinamp FAQ only because this is more of a pet project.
I do offer help to those who need it via e-Mail. Just send your ERROR.LOG to wwwinampATenusbaumDOTcom and I’ll be more than happy to help you out!
The ERROR.LOG will let me know if the problems you’re seeing are an easily fixed configuration issue or a more serious defect within the application.
Thanks!