Skip to main content

VS2011 BETA: Error : DEP3000 : Attempts to stop the application failed. This may cause the deployment to fail

Scriam cateva teste pentru o aplicatie metro pe Windows8 cand m-am trezit cu urmatoarea eroare:
    Error : DEP3000 : Attempts to stop the application failed. This may cause the deployment to fail.
    AppX packages may only be shutdown as part of a Visual Studio build operation.
    Error : DEP1100 : Cannot delete file "Assets\Logo.png" from the layout.
    Access to the path 'C:\..\bin\x86\Debug\AppX\Assets\Logo.png' is denied.
    An internal error occurred while launching test executor for Windows Metro style app.
Tot ce trebuie sa faceti este sa stergeti directorul 'bin' din proiectul de teste si problema ar trebuie sa dispara.

Putin mai tarziu cand scriam testele m-am trezit cu urmatoarea eroare:

An internal error occured while launching test executor for Windows Metro style ap.
Din pacate aceasta eroare nu iti spune foarte multe si nu stii care poate sa fie cauza. Dupa ce m-am jucat putin cu proiectul am descoperit si problema. In proiectul de deste aveam referit un proiect de UI (Windows Metro style project).
Solutia a fost simpla, am eliminat proiectul referit. Dar as fi vrut sa adaug si teste pentru View Module. Acest lucru nu este posibil in acest moment, deoarece nu se pot face teste pentru proiectele de tipul Windows Metro style. In schimb puteti sa adaguti View Module-urile intr-un proiect separat de tip library.
Sistem de operare: Windows 8 Consumer Preview
VS: Visual Studio 2011 BETA

Spor.

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

[Post Event] Azure AI Connect, March 2025

On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.