Skip to main content

Service Bus Queues from Windows Azure - Scheduling

Today I will continue discussion about Service Bus Queue with X topics.
Let’s assume that we have messages that we need to deliver on the queue only on a specific type. How should we do this? First solution that can come in our mind is to create a service, something like a schedule that will add the message to the queue only on a given time. This is a possible solution, but we need to develop a service, we need to host this. All of this means money and resources.
Another simple solution is to use the scheduled functionality that is offered by the Service Bus from Windows Azure. Any message that is added to the Service Bus Queue can be scheduled. Each message that is created can have the property “ScheduledEnqueueTimeUtc” set to a given value. When this value is not set the message is automatically added and available to the queue. When we set this value, the message will enqueued to the queue only at the specific time.
From the code, the only thing that we need to do is to set this property. Is not need to specify something when we send this message or something similar.
QueueClient qc =
myFooConnectionString, "FooQueue");
BrokeredMessage message = new BrokeredMessage();
message.Properties["Name"] = "Radu Vunvulea";
// The message will be enqueue in 1 hour from the current time.
message.ScheduledEnqueueTimeUtc = DateTime.UtcNow.Add( new TimeSpan(0,1,0,0));
As you can see is quite simple to do something like this. We don’t have to reinvent the wheel. This functionality is already built in in Service Bus. Next we will talk how we can integrate WCF to Service Bus.


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…