Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

Issue with GeographyPoint: System.Data.Entities.Spatial not found for .Net Core 3.1 #159

Closed
ccjx opened this issue Mar 9, 2020 · 1 comment
Labels
bug Confirmed bug released Issue is resolved in a current release
Milestone

Comments

@ccjx
Copy link

ccjx commented Mar 9, 2020

Hi there,

I am trying to use GeographyPoint in one of my entities, however it seems that it is generating with System.Data.Entities.Spatial even when in .Net Core 3.1.x mode.

It should be using Point in NetTopologySuite.Geometries instead. (https://docs.microsoft.com/en-us/ef/core/modeling/spatial)

Is anyone else aware of this issue? Is this fixed in a release post 1.3.0.11?

@msawczyn msawczyn added the investigating Looking into this label Mar 9, 2020
@ccjx
Copy link
Author

ccjx commented Mar 13, 2020

@msawczyn do let me know if there's anything I can do to help. I really like your extension and it has helped me in my projects a lot.

For now I have worked around the issue by adding a partial class and adding the column in the partial class as a property (with type Point from the Geometries library).

@msawczyn msawczyn added this to the 2.0.0.0 milestone Mar 18, 2020
@msawczyn msawczyn added bug Confirmed bug and removed investigating Looking into this labels Mar 18, 2020
msawczyn added a commit that referenced this issue Mar 22, 2020
Fix: HasDefaultSchema doesn't work with MySql (#160)
Fix: Issue with GeographyPoint: System.Data.Entities.Spatial not found for .Net Core 3.1 (#159)
@msawczyn msawczyn added the pending release Issue is resolved in the current codebase, will be published with the next release label Mar 27, 2020
@msawczyn msawczyn modified the milestones: 2.0.0.0, 2.0.0 Mar 27, 2020
@msawczyn msawczyn added released Issue is resolved in a current release and removed pending release Issue is resolved in the current codebase, will be published with the next release labels Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Confirmed bug released Issue is resolved in a current release
Projects
None yet
Development

No branches or pull requests

2 participants