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

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…