I’ve spent a lot of time learning about advertising on the radio. I understand ROI as well as MER (Media Efficiency Ratio). I understand the point of 30 minute long form ads versus :30 second spots and prime placement versus remnant space. These are all radio terms that help businesses get good at advertising on the radio.
But here’s something I don’t get. When I was a kid growing up in Anchorage, Alaska I first heard “That Song” by Genesis on KGOT. In Omaha during college I listened to Rush Limbaugh on KKAR and in Nashville I listen to music on JackFM.
There doesn’t appear to be anything strange about that, does there? EXCEPT while driving today I couldn’t remember where JackFM was on the radio dial.
That’s what’s strange. At least JackFM has branded itself with an attitude, but what about KGOT and KKAR and WTN? Who cares what the call letters are? I certainly don’t and I’ve never had a radio that was organized by call letters, it’s only numbers.
Now I’ve certainly listened to my share of stations that use their numbers with their name every 2 minutes like 101.3 KFAR. It gets ingrained in your head after a while – that part makes sense. But what marketing value do the call letters KFAR bring? Nothing. Absolutely Nothing. Advanced Internet Marketing Strategies
But there’s always an exception, isn’t there? There’s a station in Omaha that goes by Lite96. That’s their moniker, that’s their name, that’s their brand. Genius! They’re a light rock/pop station at position 96 on the dial – thus Lite96. That’s pure radio genius. They say their call letters every once in a while because some government body forces them to, but Lite96 is their name – no matter the call letters. Read more...
Windows Workflow Foundation is part of the Microsoft .NET Framework 3.5. Is this series of lessons we will understand how to develop a Page-flow solution using ASP.NET and Windows Workflow Foundation. In this lesson we are going to learn how to create a communication channel between the workflow library and the ASP.NET Application. In this lesson we are going to implement the contract that we created in the lesson 2 and with this implementation we are creating our PageflowService. This service is the responsible for managing the events pageflow events and methods called from the workflow library. In this lesson, we are also, creating a WorkflowRuntime Wrapper class. The WorkflowRuntime is the responsible for managing workflow instances and workflow services. We are going to understand how to manage the Workflow runtime in an ASP.NET application, it means, when and where to create it and where to store it. Technologies Used: Windows Workflow Foundation, .NET Framework 3.5, Visual Studio 2008.
Windows Workflow Foundation is part of the Microsoft .NET Framework 3.5. Is this series of lessons we will understand how to develop a Page-flow solution using ASP.NET and Windows Workflow Foundation.In this lesson we are going to learn how to create the host application to the Pageflow Solution. In the previous lesson we created a Pageflow Service in our ASP.NET Application, in this lesson we are going to consume the Pageflow Service in our webforms. We will also understand the best practices in a web application to create a Workflow Instance using the Workflow Runtime and also how to invoke events in the workflow. We will also understand how the Manual Scheduler Service works in an ASP.NET Scenario. Technologies Used: Windows Workflow Foundation, .NET Framework 3.5, Visual Studio 2008.
Windows Workflow Foundation is part of the Microsoft .NET Framework 3.5. Is this series of lessons we will understand how to develop a Page-flow solution using ASP.NET and Windows Workflow Foundation. In this lesson we are going to learn how to create a communication channel between the workflow library and the ASP.NET Application. In this lesson we are going to implement the contract that we created in the lesson 2 and with this implementation we are creating our PageflowService. This service is the responsible for managing the events pageflow events and methods called from the workflow library. In this lesson, we are also, creating a WorkflowRuntime Wrapper class. The WorkflowRuntime is the responsible for managing workflow instances and workflow services. We are going to understand how to manage the Workflow runtime in an ASP.NET application, it means, when and where to create it and where to store it. Technologies Used: Windows Workflow Foundation, .NET Framework 3.5, Visual Studio 2008.
