移动线程:实体框架和空间类型 [英] Moved Thread: Entity Framework and Spatial Types

查看:63
本文介绍了移动线程:实体框架和空间类型的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Raymond Saltrelli最初在预发布论坛上提出这个问题;将其移到此处以获得可见性:

Raymond Saltrelli originally asked this question on the pre-release forums; moving it here for visibility:

"是否有计划将新的Entity Framework空间类型添加到WCF数据服务? 当他们在2011年6月的CTP中将它们添加到EF时非常好,所以现在我可以操作它们服务器端但我也希望能够向客户端发送一些
类型的表示。

"Is there any plan to add support for the new Entity Framework spatial types to WCF Data Services?  It was really nice when they added them to EF in the June 2011 CTP so now I can manipulate them server side but I would also like to be able send some kind of representation to the client.

同时有解决方法吗? 我尝试在Geometry属性上使用IgnoreProperties属性并添加GeometryAsBase64String属性,但显然IgnoreProperties不适用于EF。 如果我想在WCF数据服务中使用空间类型,那么EF有什么替代方案可以获得
?"

Is there a work around for this in the mean time?  I tried to use the IgnoreProperties attribute on my Geometry property and add a GeometryAsBase64String property but apparently IgnoreProperties doesn't work with EF.  What alternatives to EF do I have if I want to use spatial types with WCF Data Services?"

推荐答案

我想我们是在这个世界上单独尝试使其在EF 5和WCF数据服务5之间工作,我很高兴EF使用system.data.spatial.dbGeography而WCF只使用system.spatial.Geography ...为什么会如此复杂的是让它在两者之间工作
I guess we are alone in this world to try to make it work between EF 5 and WCF data service 5, im stucked with the fact that EF uses system.data.spatial.dbGeography and WCF only uses system.spatial.Geography... why is it so complicated to make it work between the two?


这篇关于移动线程:实体框架和空间类型的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆