Geek Answers Handbook

Sometimes - it is impossible to create a Windows Azure Cloud Service - the link to the object is not installed in the instance of the object?

I have a solution where I have a working role, some kind of project library and a cloud service. Sometimes I can’t build a solution (without changing the source code or anything else).

Output windows show:

1> Error: the reference to the object is not installed in the instance of the object. ========== Build: 0 succeeded, 1 failed, 2 updated, 0 skipped ===========

When I try to change the properties of a user role in a Cloud Service project, I have a pop-up window "Object link not installed in object instance".

When I try to remove an employee from the Cloud Service project, I have a popup

"Windows Azure Tools for Microsoft Visual Studio.

The service definition or service configuration is invalid. Correct errors in the service definition files (.csdef) or the service configuration file (.cscfg) to complete this action. "

I am not sure if this is due to the build problem, but when the build works, these problems also do not exist, so I can assume that it is somehow connected.

This is strange because I can’t understand why sometimes it works and sometimes not.

Is anyone

+8
visual-studio-2013 azure
source share
3 answers

I was able to solve this problem by unloading the Azure project and reloading it.

  • Right-click the Azure project.
  • Click Upload Project.
  • Right-click the Azure project.
  • Click "Update Project."

Update

This happened to me again, and these steps were not enough, I had to close Visual Studio and open it again.

+13
source share

In my case, I get the same error after I transferred the solution from VS 2005 to vs 2013. The error only occurs when creating a website.

The only way to resolve the error when starting VS 2013 as an administrator.

0
source share

I fought the same thing last weekend after upgrading from SDK 2.1 to 2.5. I found that something (maybe the Azure Caching package?) Sometimes added <Import moduleName="Diagnostics" /> to the .csdef file. This is not true, because in SDK 2.5, diagnostics are performed differently. Removing this line will usually cause the assembly to work again, but then it will randomly break again.

The only thing I managed to fix was to create a new Cloud project from scratch, re-add all my roles and copy the settings.

0
source share

More articles:


All Articles