Skip to main content

WTF - Package Load Failure - Microsoft.VisualStudio.TeamFoundation.VersionControl.HatPackage, Microsoft.VisualStudio.TeamFoundation.VersionControl

In cursul zilei de azi am avut parte de o experienta destul de neplacuta. De doua ori mi s-a restartat PC-ul fortat in timp ce Visual Studio se incarca. O sa spuneti si ce daca, asa am zis si eu, dar am avut o surpriza neplacuta sa ma trezesc cu niste erori destul de urate.
Dupa ce pornit din nou sistemul de operare si Visual Studio am vrut sa accesez din Team Explorer Source Control-ul dar m-am trezit ca acest lucru nu mai este posibil. Puteam sa vad lista de build-uri, documentele de pe SharePoint si orice altceva, mai putin sa accesez Source Controler-ul. Am primit o eroare destul de urata, asemanatorare cu urmatoarea:
... Package Load Failure - Microsoft.VisualStudio.TeamFoundation.VersionControl.HatPackage, Microsoft.VisualStudio.TeamFoundation.VersionControl ...
WTF, de unde pana unde, nici nu stiam de unde sa o iau. Am incercat restore la OS la o versiune precedenta dar la fel. Am incercat sa reinstalez Team Explorer-ul dar fara nici un rezulvat. Pana la urma am ajuns in cache-ul de la Team Foundation, unde a fost nevoie sa sterg fisierul "VersionControl".
c:\Users\[someUser]\AppData\Local\Microsoft\Team Foundation\3.0\Cache\ VersionControl.config
Odata ce l-am sters lucrurile pareau sa revina la normal si am putut din nou sa accesez source controler-ul.
Din nou am avut o surpriza neplacuta cand am incercat sa deschid solutia pe care lucram. Nici unul din proiectele din solutie nu le putema deschide. Nu avea importanta ca era un proiect standard de .NET 4.0, sau de SL 4.0. Nici unul nu se putea incarca, iar urmatoarea eroare se afisa pentru fiecare proiect din solutie care se incarca:
A project with that name is already opened in the solution.
Din nou WTF, acest lucru se intampla si cand doream pe o solutie goala sa adaug un proiect. A fost nevoie sa fac repair la VS 2010 SP1, iar apoi sa reinstalez SL 4.0 Tools, iar apoi din nou repair la VS 2010 SP1.
I did it, solutia din nou se incarca fara probleme si totul a revenit la normal.
Sper sa nu aveti si voi aceleasi probleme.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…