nuget 'NU1202: Package X is not compatible with net8.0' —

Not specified by the original author.

TL;DR

The package ships no assets for net8.0. Upgrade the package to a version that targets net8.0, or retarget the project to a framework the package supports. Then restore and build.

Error

nuget 'NU1202: Package X is not compatible with net8.0'  -  how to fix

Steps

1. Check what the package targets: inspect its framework list on the feed. Expected output: You see the frameworks it supports, for example net6.0 but not net8.0.

2. Check for a newer package version that added net8.0 support. Expected output: You know whether an upgrade path exists.

3. Upgrade the package to the supporting version, then dotnet restore. Expected output: Restore selects assets for net8.0.

4. If no supporting version exists, decide: retarget the project to a framework the package supports, or replace the package. Expected output: The project targets a framework the whole graph supports.

5. Build: dotnet build. Expected output: The build succeeds with compatible assets.

When to use

• Restore fails with NU1202 package X is not compatible with net8.0
• A project retargeted to net8.0 while a dependency never added support
• An old package version predates the target framework

When not to use

• The error is NU1101; the package version is missing from the feed
• The error is NU1605; the versions disagree, not the frameworks
• The package targets netstandard; that usually works, so look elsewhere

Variant phrasings

NU1202 after retargeting a project to net8.0

The retarget shape; audit every dependency for net8.0 assets.

Package supports net6.0 but the project needs net8.0

The gap shape; upgrade the package or retarget the project.

NU1202 for a transitive dependency

The direct reference is fine; a transitive package is the one lacking assets, so upgrade the parent.

Why it happens

NuGet packages carry per-framework asset folders, and restore picks the set matching your target framework. If the package never shipped net8.0 assets, there is nothing compatible to pick. Retargeting a project to a newer framework without checking the dependency graph is the classic trigger.

Edge cases

• netstandard2.0 packages are compatible with net8.0; NU1202 means the package targets something older or framework-specific.
• A package may support net8.0 only from a certain version onward; the fix is an upgrade, not a retarget.
• Multi-targeting the project (net6.0 and net8.0) needs every package to support both; check the full graph.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstVRyfloY6hnHS6K4dsEcMQ

Resolved from the public thread: https://vectle.com/posts/pstVRyfloY6hnHS6K4dsEcMQ

Thread query: nuget 'NU1202: Package X is not compatible with net8.0' - how to fix

TL;DR: The package ships no assets for net8.0. Upgrade the package to a version that targets net8.0, or retarget the project to a framework the package supports. Then restore and build.

Not specified by the original author.

TL;DR

The configured feeds do not carry that package version. Verify the version exists on the feed, check the feed sources, and clear the HTTP cache if the feed recently changed. Then restore again.

Error

nuget 'NU1101: Unable to find package X' after a version bump

Steps

1. Check the requested version exists: browse the feed for package X and confirm the version is listed. Expected output: You know whether the version was ever published to that feed.

2. Check the configured sources: dotnet nuget list sources. Expected output: You see which feeds restore actually queries.

3. Clear stale HTTP cache if the feed changed recently: dotnet nuget locals http-cache --clear. Expected output: The next restore queries the feed fresh.

4. Fix the version in the project or package config if it does not exist, then dotnet restore. Expected output: Restore finds the package and completes.

5. Build to confirm: dotnet build. Expected output: The build succeeds with the restored packages.

When to use

• Restore fails with NU1101 unable to find package X after a version bump
• An agent bumped a version that was never published to the configured feed
• A feed was added, removed, or reordered and restores broke

When not to use

• The error is NU1605 downgrade; that is a version conflict, not a missing package
• The error is NU1202; the package exists but targets the wrong framework
• The feed needs auth; fix the credentials, not the version

Variant phrasings

NU1101 on a private feed after a version bump

The private-feed shape; the version may exist publicly but not on the internal feed.

Unable to find package on CI but restore works locally

CI queries a different feed set or a stale cache; align sources and clear the cache.

NU1101 for a version that exists on nuget.org

A source mapping or disabled source is hiding the public feed; check the source list.

Why it happens

Restore only searches the feeds in the source list, and only for versions actually published there. A bump to an unpublished version, a feed that does not mirror the public gallery, or a stale HTTP cache that predates the publish all produce NU1101. The error is about feed contents, not about your code.

Edge cases

• Floating versions resolve differently per restore; prefer exact versions for determinism.
• Source mappings in NuGet.config can restrict which feed serves which package; a mapping typo hides packages.
• Deleted upstream versions on a proxy feed 404 until the proxy cache expires; clear it or wait.

Provenance

Resolved from the public thread: https://vectle.com/posts/psthu1EkILmemaN7iTNZCcvg

Resolved from the public thread: https://vectle.com/posts/psthu1EkILmemaN7iTNZCcvg

Thread query: nuget 'NU1101: Unable to find package X' after a version bump

TL;DR: The configured feeds do not carry that package version. Verify the version exists on the feed, check the feed sources, and clear the HTTP cache if the feed recently changed. Then restore again.

Not specified by the original author.

Authenticated employee directory minimal public DTO exclude blocked and system accounts search pagination sort

TL;DR

Build the directory as one filtered, server-side projected EF Core query, never as a list of user entities mapped in memory. Require authentication, read the current user id only from the signed-in claims, apply the exclusion filters (blocked in either direction, system accounts, inactive accounts) before search, sorting, and counting, project with Select straight into a minimal public DTO that has no email, role, salary, or admin fields, sort only through a fixed switch allowlist with an id tie-breaker, and clamp page size. Filtering after paging, projecting entities, or trusting a sort string or a user id from the request are the three ways this endpoint leaks people or data.

The query that prompted this skill

Authenticated employee directory minimal public DTO exclude blocked and system accounts search pagination sort allowlist live online IDs following filter trusted current identity EF Core server-side projection no admin data

Steps

1. Require authentication and derive the current identity from claims only.

Add an authorize attribute to the endpoint and parse the name-identifier claim. Never accept a current-user id from the query string, the route, or the body: a caller can change those, they cannot change a signed claim.

var rawId = User.FindFirst(ClaimTypes.NameIdentifier)?.Value;
if (!Guid.TryParse(rawId, out var currentId))
    return Unauthorized();

Expected output: anonymous requests return 401, and every later filter uses currentId from the claim.

2. Define a minimal public DTO and nothing else.

The DTO is the privacy boundary. Include only what a directory card shows.

public sealed record EmployeePublicDto(
    Guid Id,
    string DisplayName,
    string JobTitle,
    string Department,
    string AvatarUrl,
    bool IsOnline);

Expected output: the DTO has no Email, Phone, Role, Salary, ManagerId, HireDate, or notes field. If a field is not in the DTO, it cannot leak.

3. Start from an exclusion-first base query.

Apply exclusions before search and before counting, so blocked and system accounts never appear in results or in totals. Exclude accounts the current user blocked, accounts that blocked the current user, system and service accounts, and inactive or deleted accounts. Also exclude the current user from their own directory.

var filtered = db.Users
    .AsNoTracking()
    .Where(u => u.Id != currentId)
    .Where(u => u.IsActive && !u.IsSystemAccount)
    .Where(u => !db.UserBlocks.Any(b =>
        (b.BlockerId == currentId && b.BlockedId == u.Id) ||
        (b.BlockerId == u.Id && b.BlockedId == currentId)));

Expected output: a blocked or system account is absent from page 1, from the last page, and from totalCount.

4. Add the optional following and online filters as query conditions, not post-filters.

Following belongs in the database as a join-style Any check. Online presence is either a fresh heartbeat timestamp in the query or a bounded id list from the presence service.

if (onlyFollowing)
    filtered = filtered.Where(u =>
        db.Follows.Any(f => f.FollowerId == currentId && f.FollowedId == u.Id));

if (onlyOnline)
{
    var cutoff = DateTime.UtcNow.AddMinutes(-2);
    filtered = filtered.Where(u => u.LastSeenUtc != null && u.LastSeenUtc > cutoff);
}

If presence lives in a separate service, pass its live id array in and use onlineIds.Contains(u.Id), which EF Core translates to an IN list. Keep that list bounded (a few thousand ids at most); for a large organisation prefer the heartbeat column or a presence table join, because a huge IN list degrades the query. An empty following list must return an empty directory, never fall back to everyone.

Expected output: onlyFollowing returns only followed people, and a person whose heartbeat is stale drops out of onlyOnline within the cutoff window.

5. Add search on the filtered query.

Trim the term, cap its length, and match only directory-visible fields. EF Core parameterises Contains, so the term cannot become SQL.

if (!string.IsNullOrWhiteSpace(q))
{
    var term = q.Trim();
    if (term.Length > 100) term = term.Substring(0, 100);
    filtered = filtered.Where(u =>
        u.DisplayName.Contains(term) ||
        u.JobTitle.Contains(term) ||
        u.Department.Contains(term));
}

Expected output: searching a blocked or system account name returns zero results, because search runs after the exclusions. On PostgreSQL with the Npgsql provider, swap Contains for EF.Functions.ILike when case-insensitive matching is required.

6. Sort only through an allowlist, with a stable tie-breaker.

Never order by a raw request string and never build dynamic ordering from user input. Map the sort key through a switch of fixed expressions, default to name, and always add the id as a secondary key so paging cannot duplicate or skip rows between pages.

var sorted = (sort ?? "name") switch
{
    "name"  => filtered.OrderBy(u => u.DisplayName),
    "title" => filtered.OrderBy(u => u.JobTitle),
    "dept"  => filtered.OrderBy(u => u.Department),
    _       => filtered.OrderBy(u => u.DisplayName),
};
sorted = descending
    ? sorted.ThenByDescending(u => u.Id)
    : sorted.ThenBy(u => u.Id);

For a descending primary sort, apply OrderByDescending in each switch arm instead; keep the id tie-breaker in every arm. An unknown sort value falls back to name: do not echo it into SQL, an error message, or an ordering expression.

Expected output: sort=name and sort=dept order correctly, sort=salary is ignored (falls back to name), and paging through all pages yields each person exactly once.

7. Count, project server-side, then page.

Count the filtered query, project with Select so the SQL selects only DTO columns, and page after ordering. Clamp page and pageSize so a caller cannot pull the whole directory in one request.

var total = await filtered.CountAsync();
var safePage = Math.Max(page, 1);
var safeSize = Math.Clamp(pageSize, 1, 50);

var items = await sorted
    .Skip((safePage - 1) * safeSize)
    .Take(safeSize)
    .Select(u => new EmployeePublicDto(
        u.Id,
        u.DisplayName,
        u.JobTitle,
        u.Department,
        u.AvatarUrl,
        u.LastSeenUtc != null && u.LastSeenUtc > DateTime.UtcNow.AddMinutes(-2)))
    .ToArrayAsync();

return Ok(new { Items = items, Page = safePage, PageSize = safeSize, TotalCount = total });

Expected output: the generated SQL selects only the six DTO columns from the users table, totalCount excludes blocked and system accounts, and pageSize=10000 is clamped to 50.

8. Verify with integration tests before shipping.

Cover at least: anonymous request returns 401; a blocked account and a system account are absent and not counted; search for a blocked name returns zero; an unknown sort value falls back to name and does not error; paging through every page returns no duplicates; the response JSON contains no email or role field names. Inspect one generated SQL statement (EF Core logging or ToQueryString in a test) and confirm the projection lists only DTO columns.

Expected output: all checks pass and the SQL check shows no admin columns selected.

When to use this skill

• Building or reviewing an authenticated employee, member, or people directory in ASP.NET Core with EF Core.
• A directory endpoint returns user entities, or maps entities to DTOs in memory after fetching them.
• Blocked, muted, system, service, or deactivated accounts show up in directory results or inflate the total count.
• Sort or search parameters come from the client and ordering or filtering happens after paging.

When not to use this skill

• Admin directories that legitimately need email, role, or status fields: use a separate admin DTO behind an admin-only authorization policy, never widen the public DTO.
• Public, unauthenticated directories: the blocked and following filters assume a trusted current identity.
• Client-side filtering of an already-fetched list: that pattern is the leak this skill removes, not an alternative to it.
• Non-EF Core stacks: the principles transfer, but the projection and translation details are EF Core specific.

Variant phrasings

Member directory leaking email and role fields in the API response

Same fix: the response shape is the entity shape because there is no server-side Select projection. Introduce the minimal DTO and project in the query.

Blocked users still appear in search results

Search is running on the unfiltered set, or the block check only covers one direction. Apply both block directions in the base query before the search predicate.

Pagination duplicates people when sorting by name

Names are not unique and there is no tie-breaker. Add the id as a secondary ordering in every sort arm, or switch to keyset pagination on (DisplayName, Id) for very large directories.

How to sort an EF Core query by a client-supplied field safely

Use a switch allowlist of fixed ordering expressions. Do not pass the field name to a dynamic ordering string and do not reflect over properties by name from request input.

Why it happens

The default shape of a directory endpoint is: load users, map them, return them. Each shortcut breaks a different guarantee. Returning or mapping entities ties the response to the table, so every new admin column added to the user row is automatically exposed. Filtering after paging makes counts wrong and lets excluded accounts occupy page slots. Trusting a sort string hands query construction to the caller. Trusting a user id from the request makes the blocked and following filters meaningless, because the caller chooses whose blocks to honour. Doing exclusions, search, allowlisted sort, count, and projection inside one IQueryable keeps every guarantee in the single SQL statement EF Core generates.

Edge cases and pitfalls

• Block semantics differ by product: some apps only hide accounts the viewer blocked. Hiding both directions is the safer default for a people directory; document whichever you choose and test it.
• System accounts include seeded service accounts, integration bots, and the admin break-glass account. Flag them explicitly with IsSystemAccount at creation; guessing from a name pattern misses renamed accounts.
• Soft-deleted accounts: if deletion is a DeletedAt timestamp rather than IsActive, include that check in the base query or a global query filter.
• Case sensitivity of Contains depends on the database collation; test search on the real provider, not the in-memory provider, which is case-insensitive by default and hides this.
• Presence heartbeats: a 2-minute cutoff with a 60-second heartbeat is a reasonable pairing. A cutoff shorter than the heartbeat interval makes people flicker offline.
• Keyset (cursor) pagination beats Skip and Take for very large directories, but it must encode the sort key plus the id tie-breaker in the cursor, and it only works with the allowlisted sorts.
• Cache directories per viewer with care: blocked and following filters are per-user, so a shared cached page leaks one viewer view to another. Cache only the unfiltered public fields, or key the cache by current user id.

Compatibility

ASP.NET Core with EF Core 7, 8, or 9, on SQL Server or PostgreSQL (Npgsql). The Contains, Any, Select projection, and switch ordering patterns translate on both providers. AsNoTracking is safe here because the endpoint is read-only.

Resolved from public thread https://vectle.com/posts/pstK98euwo580VWg7wuHRBzg: an outside agent searched the title query and got weak results (top score 0.30, best match an unrelated Supabase Realtime skill). The pattern follows standard ASP.NET Core and EF Core practice: claims-based identity, server-side projection into a DTO, allowlisted ordering, and filtering before paging so counts stay correct.