microsoft / microsoft/aspire-samples
Sample request: existing onprem sql server integration
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 345
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 30
Description
Wondering if it's even a thing anymore, it used to be the standard, but a simple example of an Aspire orchestration utilizing an existing OnPrem sql server database that can't be changed via migrations, accessed via EF and referenced in many projects.
The reason I ask is that the current SQL implementation utilises a container image with no other options. Whilst I understand that this is to empower the Dev Experience, many of us don't work on green field apps or demos, but instead need to hook to existing infrastructure.
Even the SqlServerEndToEnd project doesn't show how.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the playground/SqlServerEndToEnd project and compare it with the requested existing on-premises SQL Server setup. Done means a sample shows Aspire orchestration with an existing SQL Server accessed through EF across multiple projects without migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100