Skip to main content

Tool-uri pentru Windows Azure

By
Total Cost Calculator
http://www.microsoft.com/windowsazure/economics/
O aplicatie oferita de catre Microsoft pentru a ne ajuta sa estimam preturiile unei aplicatii in loud. Estimariile nu sunt foarte exacte, dar ne pot oferii o idee asupra preturiilor in prima faza. As fi vrut sa fie mai exacta si sa ne permita sa introduce in calculul final mai multe variabile, dar in versiunea actuala trebuie sa ne multumim doar cu atat.
Nota 8.

Azure Storage Explorer
http://azurestorageexplorer.codeplex.com/
O alta aplicatie foarte utila poate sa fie Azure Storage Explorer. Prin intermediul ei putem sa interogam si sa executam operatii CRUD pe table, blob si queues aflate in cloud sau de pe masina de test. Poate sa ne fie de foarte ajutor, mai ales in faza de debug sau de testare.
Nota 10.

Windows Azure Service Management CmdLets
http://archive.msdn.microsoft.com/azurecmdlets
Ne permite sa facem deploy si sa controlam o aplicatie din cloud din linia de comanda. Putem sa scriem scripturi pe care apoi sa le rulam automat. Tot procesul de deploy poate sa fie automatizat si din cate am observat putem sa automatizam si modul in care scalam aplicatie. CmdLets ne permite sa cream( sau distruge) instante in cloud. Daca stim Power Shell putem sa generam scripturi care sa faca minuni.
Nota 10.
Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
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.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more