Skip to main content

Azure SDK 2.4 to 2.5 upgrade. Error: "'Microsoft.WindowsAzure.ServiceRuntime.RoleEnvironment' exists in both 'Microsoft.WindowsAzure.ServiceRuntime.dll' and 'Microsoft.WindowsAzure.ServiceRuntime.dll"

If you're getting this error while calling the type 'RoleEnvironments' then there is probably something wrong with the Visual Studio migration of Azure 2.4 to 2.5.

To fix this issue simply remove then add references to the DLL Microsoft.WindowsAzure.ServiceRuntime.dll to the project that's calling 'RoleEnvironments'.

Comments

  1. You can also fix the problem here http://fix4dll.com/xinput1_3_dll. I think it's one of the best services for this kind of problems. Check it out.

    ReplyDelete

Post a Comment

Popular posts from this blog

from zero to production in eighty days

When I mean zero, I literally mean zero. A brand new project, a PO that's new to IT, no existing processes in place and a small team of four including myself and the PO.

The departmental organisation we were working for doesn't have any developers, scrum masters, product owners working for them. Everything they did was either done by another department or outsourced completely.

This is a story how we went from zero to production in eighty days.

My first time speaking at a conference

Since time immemorial we humans have valued the art of public speaking. Today, I want to share with you my experiences in speaking at conferences for the first time. Recently, I spoke at both DDD Melbourne and DDD Perth. Both of which were positive experiences that I learnt a lot in.


Have You Ever Produced Negative Value in a System!?

As developers we encourage our product owners to order the priority of their backlog in order of value. However, every time a new feature is implemented by a development team, there is a certain degree of risk associated with the introduction of that new code. Namely, risk of breaking another part of the product and maintenance cost. When a development team pulls in a new feature to implement there is a certain acceptance of this risk. In many cases, the risks that arise due to additional code complexity doesn't justify the value added by the new feature itself, so the development team can start implementing it.

Are there scenarios where the value added to a software product can be negative though?