Skip to main content

TechEd 2013 -Day 3

The 3rd day of TechEd had finished. At the keynote I had the opportunity to see a demo of an application for Windows Store for which I write a part of the code a design it. Also I discover that over 66% of the companies has the bring your own device policy active. For them, Windows 8 and Windows Phone 8 came with special features that secure and protect their private data. Because of this, companies like SAP will have all their applications for sale force migrated to Windows 8 (until end of 2015).
From the developer perspective, we should try the new  Visual Studio 2013. It has great features especially for load test. Even if in the preview it is pretty stable. Also, if you are starting to develop a client-server application, that will communicate over http/s than… go with  Web.API. Why? Because Microsoft invest and will invest a lot of resources in that area. WCF is good for TCP/IP and other protocols, but for HTTP/S they recommend is Web.API.
The last presentation of the day was very intertying. It started at 5 PM, in the same time with another presentation from the Build, where they announce some new services of Windows Azure. Auto-scaling is not build-in and supported by Azure. From now on we can define the rules directly on Window Azure portal – this is so COOL :D. This feature combined with alerts and notification services will be very useful for the maintenance team. Great job!
That all for today!

Comments

Popular posts from this blog

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

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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.51 EF 6.0.2 VS2013 It see...