Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. It provides cloud messaging between application components. In designing applications for scale, application components are often decoupled, so that they can scale independently. Queue storage delivers asynchronous messaging for communication between application components, whether they are running in the cloud, on the desktop, on an on-premises server, or on a mobile device. Queue storage also supports managing asynchronous tasks and building workflows.
There are two ways to manage resources in Azure: Classic and Resource Manager. Resource Manager is the recommended way now, you can read more about resource manager at Azure Resource Manager overview. Microsoft will enable Resource Manager for every service that is important for future solutions, but until the support is consistent, you need to know the current status for each service. For example it is possible to use Azure Storage cmdlets in a resource manager context, you can mix them easily.
Azure PowerShell is a set of modules that provide command line interface to Azure. You can accomplish almost everything using Azure PowerShell. It's obvious now that Microsoft investing lots of effort into command line tools for its products and it's great! There are two command line interfaces implementation - PowerShell and Azure CLI. Personally I don't use Azure CLI very often because I primary work on windows systems, but people who work with *nix systems are first-class citizens now in Microsoft world, so they have their own tool. The funny thing is that Microsoft released PowerShell for Linux. So developers can use both Azure PowerShell and Azure CLI regardless operation system they use.
Recently I have been reading Q&A for the 70-483 Microsoft certification exam. Most of the questions are very simple, but some of them were actually hard to answer correctly. Anyway, one of the questions forced me to make a small research regarding how C# compiler concatenates strings. At first, I thought that the question is very easy and there is nothing special about that, but then I realized that I am not 100% confident with my answers, I will show you why.
There are lots of info regarding this topic on the Internet. Also, each and every C# book has a few pages dedicated to this subject. I am going to start from basics and continue with more advanced topics related to IoC containers and handling exceptions in SOA and distributed systems. I am going to highlight some common mistakes related to implementing exception handling as well.
Every time I google for covariance I end up reading Eric Lippert's blog. It has an awesome seria of articles about covariance and contravariance. It is very old, it was written in 2007, but still useful when you don't know how to explain the variance to somebody who doesn't know how it works for delegates or generic types.
- Covariance and Contravariance in C#, Part One
- Covariance and Contravariance in C#, Part Two: Array Covariance
- Covariance and Contravariance in C#, Part Three: Method Group Conversion Variance
- Covariance and Contravariance in C#, Part Four: Real Delegate Variance
Anyways, his blog is awesome, any developer can find something useful there.
On one of the job interviews I have been asked about ThreadPool, after my answer (which was 100% correct) interviewer decided to give me a small test.
Recently I've come across the
checked keyword. To be honest, I don't use this keyword very often. I used it only few times in algorithmic challenges and that's all. I belive most people use
unchecked frequently, but don't know much about