Just wanted to drop a quick note in here letting people know that I've written a new ASP.NET server control for the Co-op Ad Network. I played around with the existing .NET port (coopad.dll) and found it to be buggy, out of date, and generally not as complete as the current PHP version. This new server control is ridiculously easy to use. No code-behind is required, unless you want to set some advanced settings. Here is a sample of an aspx page using the control: <%@ Register TagPrefix="can" Namespace="Oxford.CoopAdNetwork" Assembly="Oxford.CoopAdNetwork" %> <can:AdSpace Runat="Server" AdFilePath="~/ad_network.xml" /> Code (markup): More info can be found here: http://blog.blogspot.com/2005/05/new-co-op-ad-network-aspnet-server.html Cheers, Bobby D
If you absolutely cannot use PHP, and must use an ASP variant, this is the one you probably should use. I annoyed the crap out of Bobby while he was doing it to make sure everything works well.
Updated download url: http://www.web-controls.net/blog/new_co_op_ad_network_asp_net_server_control.aspx
Yeah, that's cool. I'll post the source on my site in a few days. I'm pretty slammed with a project right now, but I'll try to get it up by midweek. Cheers
ja, right, I hope it will be working. As I can see, the demo on your site is even not working. It is not working on my project neither.... Trying to find a working version.
File got locked. Deleted the files and all is good now. The source code has been posted and is available here: http://www.web-controls.net/blog/new_co_op_ad_network_asp_net_server_control.aspx Cheers
Did anyone else using this control suddenly start getting the message "Error retrieving ad" over the weekend?
I've deleted the XML file, but still no go. What's odd is that this behavior started occurring this weekend on all my websites using the coop on 2 different, separate servers. I had this set up and working like a champ for months now without a hitch. Such an easy setup on this one too (kudos to the developer). Just to rule out some sort of IP address related problem, I also tested out the code on a completely different IP block, but still no dice.
Ahhh, upon tracert from both servers, it seems as though there's a network problem halfway between the node that contains our servers and DP on the 18th hop. Typical end-user here, blaming the software before the hardware Edit: Well now, that doesn't seem to be it either. Even though it times out in tracert I can still bring up ads.digitalpoint.com via browser on the same machine. Is it possible that I've been banned for some reason? Are banned people usually contacted?
Hmmm, that's weird. Wonder why the tracert would timeout. Thanks for the compliments on the control - simplicity is bliss. Stupid question, but what does it tell you when you log in to view your stats for the ad network? Do your ads appear to be live?
What's your site(s)? I can check to see if the system blocked the IP due to excessive requests for new ads.
http://www.mysite.com @ 127.0.0.1 Many thanks for your time! Edit = edited to avoid bringing undue attention to our site(s)