migrating-system-spatial Skill
Migrates the obsolete System.Spatial (OData v1–v3 spatial types) to Microsoft.Spatial for OData v4. Use ONLY when System.Spatial has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where System.Spatial is still supported. Published by microsoft in upgrade-agent-plugins.
What is migrating-system-spatial Skill?
Migrates the obsolete System.Spatial (OData v1–v3 spatial types) to Microsoft.Spatial for OData v4. Use ONLY when System.Spatial has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where System.Spatial is still supported. Published by microsoft in upgrade-agent-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using upgrade-agent-plugins
Technical details
- Install or run with Copy skill directory
When to use migrating-system-spatial Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/libraries/migrating-system-spatial/SKILL.md
What it does
Migrates the obsolete System.Spatial (OData v1–v3 spatial types) to Microsoft.Spatial for OData v4. Use ONLY when System.Spatial has been flagged as obsolete or deprecated and must be replaced — not for version-bump scenarios where System.Spatial is still supported.
Skill instructions
System.Spatial to Microsoft.Spatial Migration Overview Migrate from System.Spatial (OData v3) to Microsoft.Spatial (OData v4). This is primarily a namespace change — the spatial type APIs (GeographyPoint, GeometryPoint, GeographyLineString, etc.) remain largely compatible. The main work is updating using directives and adjusting any SpatialFormatter or extension method references. Package Reference Changes Old Reference (Remove) xml <PackageReference Include="System.Spatial" Version="{old-version}" / New Reference (Add) xml <PackageReference Include="Microsoft.Spatial" Version="{version}" / Workflow Migration Progress: - [ ] Step 1: Detect System.Spatial usage - [ ] Step 2: Update project file references - [ ] Step 3: Update namespace references - [ ] Step 4: Adjust API differences - [ ] Step 5: Build and verify Step 1: Detect System.Spatial Usage Scan the project for: - using System.Spatial; statements - Types: GeographyPoint, GeometryPoint, GeographyLineString, GeometryLineString, Ge
Explore related resources
Frequently asked questions
What is migrating-system-spatial?
migrating-system-spatial is a open-source AI agent skill with Copy skill directory. Migrates the obsolete System.Spatial (OData v1–v3 spatial types) to Microsoft.Spatial for OData v4.
Who is migrating-system-spatial best for?
migrating-system-spatial is best for reusing agent instructions, scripts, and references.
How do I install migrating-system-spatial?
Install or run migrating-system-spatial using Copy skill directory. Check migrating-system-spatial for the latest setup command.
Is migrating-system-spatial actively maintained?
migrating-system-spatial may need a closer maintenance check before production use.
Auto-fetched from GitHub.
