In short, no there isn’t. SqlGeography has an appropriate method: Microsoft.SqlServer.Types.SqlGeography.Point(latitude, longitude, srid); … but you would then have to convert to DbGeography anyway. If you are interested in this, see a previous answer of mine on converting: DbGeography to SqlGeography (and back) That said, I completely agree with Raphael Althaus in that you should … Read more
As you correctly observed in the answer to your own question, removing the “virtual” keyword from the collection properties works around the problem, by preventing the Entity Framework from creating a change tracking proxy. However, this is not a solution for many people, because change tracking proxies can be really convenient and can help prevent … Read more
I noticed in visual studio, going to SQL menu, Transact-SQL Editor, New Query… gave a dialog about the tools not working with the server installed. Installing SQL Server Data Tools – December 2012 update (Sql Server Data Tools) fixed the problem
Just create your new table as a model and add its entry in DbContext class something like public class TestingContext : DbContext, IDisposable { public DbSet<CallDataRecord> CallDataRecords { get; set; } public DbSet<Attempt> Attempts { get; set; } public DbSet<MyNewModel> MyNewModels { get; set; } Then add-migration and update-database
The fact that the Seed method ran only when the database changed was quite limiting for the database initializers that shipped in EF 4.1. It was limiting because sometimes you needed to update seed data without changing the database, but to make that happen you had to artificially make it seem like the database had … Read more
You can overcome this scenario by replacing: using System.Data.Objects; With: using System.Data.Entity.Core.Objects; You may need to update the using statements in your T4 templates, like your Context.tt file, so that auto-generated files continue to work when re-generating. Before After
I know that this is not related directly to EF, but only solution I can think of is to alter DB table column collation to be Case Insensitive e.g.: ALTER TABLE TABLENAME ALTER COLUMN COLUMNNAME nvarchar(100) COLLATE Latin1_General_CI_AS NULL CI – case insensitive / CS – case sensitive AS – accent sensitive / AI – … Read more
I believe you should be able to do this: HasRequired(t => t.Agent).WithMany().HasForeignKey(t => t.AgentId)
Generally speaking, it is best to use the collection that best expresses your intentions. If you do not specifically intend to use the HashSet’s unique characteristics, I would not use it. It is unordered and does not support lookups by index. Furthermore, it is not as well suited for sequential reads as other collections, and … Read more
Usually this means that your schema and mapping files are not in synch and there is a renamed or missing column someplace.