Skip to main content

Cum sa faci deploy din Visual Studio direct in cloud

Visual Studio 2010 ne ofera posibilitatea de a face deploy( publish) la un proiect direct in cloud. Mecanismul prin care se face deploy este asemanator cu cel pentru o solutie web.
Primul pas este sa dam click dreapta pe proiectul care contine rolurile pentru Azure si sa selecta "Publish".
Al doilea pas este selectam "Deploy your Windows Azure project to Windows Azure". O sa avem nevoie sa adaugam credentialele daca acestea nu sunt setate deja. Pentru a putea adauga credentialele avem nevoie sa selectam un certificat( putem sa folosim unul deja existent sau sa generam unul local), iar apoi ID-ul subscripției noastre. Insa aici apare o problema cand vrem sa dam OK. Nu o sa putem sa adaugam credentialele pentru subcriptia noastra pana cand nu inregistram certificatul pe platforma de Windows Azure.
Pentru a inregistra certificatul este nevoie sa il exportam de pe masina noastra folosind tool-ul mmc.exe. Iar apoi este nevoie sa ne logam pe si sa mergem la sectiunea "Managment Certificates" de sub "Hosted Services, Storage Account & CDN". In aceasta locatie este nevoie sa adaugam certificatul pe care l-am exportat cu mmc.exe.
Dupa ce am selectat si credentialele, este nevoie doar sa selectam unde vrem sa facem deployment-ul si ce storage vrem sa folosim.
Atentie, nu uitati sa adaugati acest certificatul pe platforma de Windows Azure.


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 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)

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

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…