Skip to content

.Net: Reorganize MEVD projects #12332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

.Net: Reorganize MEVD projects #12332

wants to merge 3 commits into from

Conversation

roji
Copy link
Member

@roji roji commented May 31, 2025

Based on top of #12325 - review last commit only

This is a reorganization-only change, no code changes whatsoever.

  • Move MEVD test projects into a test directory (outside src) to align with standard .NET project layout, and to allow common settings for test projects (e.g. via Directory.Build.props).
  • Move MEVD projects and tests into their own VectorData directories, separating MEVD providers from other SK connectors.
  • Align solution layout with the filesystem layout.
  • Remove Memory from project paths.
  • Remove obsolete Connectors.UnitTests.

roji and others added 2 commits May 30, 2025 09:48
I'm planning some project/filesystem organization for the MEVD projects
to make everything easier to manage (and more standard). Before doing
that, I thought I might as well submit a modernization from the old SLN
format to the new, simplified SLNX format:
https://devblogs.microsoft.com/visualstudio/new-simpler-solution-file-format.
This should be a completely transparent change (all tooling/VS/VS Code
support this), but please give it a try and let me know if you see any
trouble.

Note that we had an odd "Publish" configuration (in addition to the
traditional Debug/Release), some projects were configured for it in the
SLN, others weren't; this is probably just a bit of mess that
accumulated over time. As part of this PR I cleaned that up to leave a
tight, minimal and standard SLNX. This should make changes easier to
track and conflicts much easier to manage.

Let me know what you think!

---------

Co-authored-by: Dmytro Struk <13853051+dmytrostruk@users.noreply.github.com>
Co-authored-by: Roger Barreto <19890735+RogerBarreto@users.noreply.github.com>
@roji roji requested a review from a team as a code owner May 31, 2025 17:27
@roji roji changed the title Reorganize Reorganize MEVD projects May 31, 2025
@roji roji temporarily deployed to integration May 31, 2025 17:27 — with GitHub Actions Inactive
@markwallace-microsoft markwallace-microsoft added .NET Issue or Pull requests regarding .NET code kernel Issues or pull requests impacting the core kernel kernel.core documentation labels May 31, 2025
@github-actions github-actions bot changed the title Reorganize MEVD projects .Net: Reorganize MEVD projects May 31, 2025
@roji roji temporarily deployed to integration June 1, 2025 20:55 — with GitHub Actions Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation kernel.core kernel Issues or pull requests impacting the core kernel .NET Issue or Pull requests regarding .NET code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants