Skip to main content

Windows Phone 7.5( Mango) support SQL CE

By
Windows Phone 7.5( Mango) suporta SQL CE(SQL Compact Edition). Acest feature era de mult timp asteptat. Acuma sa vedem cum se foloseste.
Baza de date poate sa fie pusa in doua locatii:
  1. isolated storage
  2. installation folder
In functie de locatie si de parametrii, stringul de conexiune poate sa aibe urmatoarea forma:
  • Data Source = 'isostore:/MyDB.sdf; - cand baza de date este in isolated storage
  • Data Source = 'isostore:/MyDB.sdf';Password='1234'; - cand baza de date este in folderul unde aplicatia a fost instalata si este encriptata cu parola 1234
La stringul de conexiue putem sa setam si alte valori precum culture-ul( "Culture Identifier") si daca este case sensitive( "Case Sensitive").
Trebuie sa tinem cont ca avem cateva limitari pe Mango cand vrem sa folosim SQL CE:
  • fisierele sdf sunt stocate si deschise din isolation storage
  • daca dorim un mecanism de ORM este nevoie sa folosim LINQ2SQL
  • T-SQL queries nu este suportat( nu putem sa avem tranzactii)
  • o referinta la System.Data.Linq trebuie adaugata
  • pentru definierea modelului in acest moment avem doua optiuni SQLMetal pentru Windows Phone Mango sau code-first. By default nu avem un tool grafic pentru definirea acestor mapari.
  • formatul la string-ul de conexiune este unul specific
Versiune de SQL CE care este suportata este SQL CE 4.0. Se poate lucra direct cu EF 4.1.
Saptamana urmatoare o sa revin cu un exemplu intreg.












Labels:

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
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...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

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