Set up solution scaffolding: Infrastructure & Tests projects, shared build settings

Open

#5 opened on Sep 11, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 68/100

Issue type: Feature
Clarity: Clearly specified
Activity status: Active
Tech stack: csharp
Domain: build-system, testing

Research direction

Start with AzStorage.slnx and the existing Domain and Application project files to understand the current layout and target settings. Add the named Infrastructure and xUnit test projects, root Directory.Build.props, and .editorconfig, then verify the acceptance criteria with dotnet build and dotnet test.

Written by the indexing model from the issue text.

Description

Goal

Establish the base Clean Architecture skeleton so that Domain, Application, Infrastructure and test projects build consistently.

Why

Currently the solution only has empty Domain and Application projects targeting net10.0. Before implementing any storage functionality we need a consistent project layout, shared build settings and code style so future PRs stay consistent.

Tasks

Add src/AzStorage.Infrastructure/AzStorage.Infrastructure.csproj (referencing Domain & Application) for concrete implementations (Azure SDK, file system, etc.).
Add tests/AzStorage.UnitTests and tests/AzStorage.IntegrationTests projects (xUnit) referencing the corresponding src projects.
Add all new projects to AzStorage.slnx.
Add a Directory.Build.props at repo root to centralize shared properties (TargetFramework, ImplicitUsings, Nullable, LangVersion, analyzers) instead of duplicating them per csproj.
Add an .editorconfig with basic C# formatting/naming rules.

Acceptance Criteria

dotnet build succeeds for the whole solution.
dotnet test runs (even with zero tests) without errors.
No project duplicates TargetFramework/Nullable/ImplicitUsings settings that are already defined in Directory.Build.props.

Dominant language: C#
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

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.

Similar issues

UnscopedRefAttribute article displaying xml tags Open

untriaged

Difficulty 1/5 Under an hour Newbie friendliness 88/100

dotnet/dotnet-api-docs#13095 · Opened Sep 25, 2026
Azure Sandboxes: Small and ExtraSmall tiers always fail to deploy (disk request exceeds tier maximum) Open

area-deployment area-integrations triage:bot-seen

Difficulty 2/5 Half a day Newbie friendliness 86/100

microsoft/aspire#20459 · 1 comment · Opened Sep 24, 2026
[quality-improver] AssertSourceCompatibilityTests.SpanAndMemoryCalls tests only half of the Span/Memory × comparer overload combinations Open

type/automation type/tech-debt

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

microsoft/testfx#11504 · Opened Sep 24, 2026
OpenTelemetry bridge duplicates MongoDB datastore segments for MongoDB.Driver 3.7.0+ because MongoDB.Driver is not excluded by default Open

bug

Difficulty 1/5 Under an hour Newbie friendliness 90/100

newrelic/newrelic-dotnet-agent#3850 · 1 comment · Opened Sep 24, 2026
Strip all whitespace from the license key Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

LuckyPennySoftware/AutoMapper#4660 · Opened Sep 24, 2026

More C# issues

Set up solution scaffolding: Infrastructure &amp; Tests projects, shared build settings