How to

Boolean search strings for .NET developers: C#, ASP.NET Core, Azure and the symbol problem

On this page
  1. Frameworks, versions and credentials that change what a .NET search finds
  2. Ten Boolean strings by kind of .NET work
  3. What LinkedIn, Dice, GitHub and Google actually support
  4. Narrowing by domain, hosting and seniority
  5. False positives worth excluding with NOT
  6. A worked example: three passes on a .NET Framework migration search
  7. What a search cannot verify
  8. Questions people ask

A .NET developer search works when it writes out every form candidates use for the platform (.NET, dotnet, ASP.NET, C#, csharp) and pairs it with a framework only .NET developers list, such as ASP.NET Core, Entity Framework or Blazor. The symbols are the trap: LinkedIn's Boolean help page does not say how search reads the dot in .NET or the pound sign in C#, so a string that leans on them alone can drift toward "net" and the letter "c." As of November 2026, Microsoft supports .NET 10 and .NET 11, and .NET 8 and .NET 9 reached end of support on November 10, 2026, which is why so many clients now ask for migration experience.

Below are ten strings by kind of .NET work, and what LinkedIn, Dice, GitHub and Google support as of November 2026. For other languages, see Boolean search strings for software engineers and for Java developers, the nearest enterprise neighbor; for the operators themselves, see Boolean search strings for recruiters.

Frameworks, versions and credentials that change what a .NET search finds

Kind of .NET workTerms candidates writeCommon titles
Web and API backendASP.NET Core, Web API, minimal APIs, Entity Framework Core, LINQ, SQL Server.NET developer, C# developer, backend engineer
Cloud on AzureAzure Functions, App Service, Service Bus, Azure DevOps, AKS.NET engineer, Azure developer, senior software engineer
Full stack in C#Blazor, Razor Pages, ASP.NET MVC, with Angular or ReactFull stack .NET developer
Desktop and mobileWPF, WinForms, XAML, MVVM, .NET MAUI, Xamarin.NET desktop developer, mobile developer
Legacy enterprise.NET Framework 4.x, WCF, Web Forms, IIS, VB.NET.NET developer, application developer
  • Write every form of the name. LinkedIn has no wildcards, so ".net," dotnet, "asp.net," "asp.net core," "c#," csharp and "c sharp" each need writing out. Dice's own Boolean guide uses ".net" as its example of a keyword to put in quotation marks because it contains punctuation.
  • Versions show what a developer has touched. Microsoft's .NET support policy lists, as of November 2026, .NET 10 as a long-term support release from November 11, 2025 and .NET 11 as a standard-term release from November 10, 2026, both supported to November 14, 2028; .NET 8 and .NET 9 went out of support on November 10, 2026. The same table names the older releases .NET Core 1.0 through 3.1 and the later ones .NET 5 onward, so profiles write ".NET Core" and ".NET 8" for the same modern platform. Put both in one OR block.
  • .NET Framework is a different product line. Microsoft's .NET Framework policy says 4.8.1 is the latest version and is supported as long as it runs on a supported version of Windows, as of November 2026. A profile with only .NET Framework, WCF and Web Forms is the maintenance pool, or the starting point of a migration hire.
  • Xamarin became .NET MAUI. Microsoft's Xamarin support page says support ended on May 1, 2024 for all Xamarin SDKs and that Xamarin.Forms evolved into .NET Multi-platform App UI (MAUI). Mobile .NET developers write both, so search both.
  • Microsoft certifications are optional evidence. Microsoft's Skills Hub post lists the Azure Developer Associate (exam AZ-204) as retired on July 31, 2026, replaced by the Azure AI Cloud Developer Associate (exam AI-200), and says earned credentials stay valid until they expire. The AI-200 page lists Python programming among the expected skills, so it shows Azure depth, not C# depth. Never require either.

Ten Boolean strings by kind of .NET work

Swap in the frameworks, industry and metro from your own intake; these are examples.

Backend, cloud and full stack

1. .NET backend developer — LinkedIn general search
(".net developer" OR "dotnet developer" OR "c# developer" OR ".net engineer") AND ("asp.net core" OR ".net core" OR "web api") AND ("entity framework" OR "ef core" OR "sql server") NOT (recruiter OR "talent acquisition")

2. Senior .NET engineer on Azure — LinkedIn Recruiter, Job titles + Keywords filters
("senior .net developer" OR "senior .net engineer" OR "lead .net developer" OR "senior c# developer") AND ("azure functions" OR "service bus" OR "app service" OR "azure kubernetes service" OR aks)

3. Full-stack .NET developer — LinkedIn general search
("full stack .net developer" OR ".net full stack developer" OR "full stack developer") AND ("asp.net core" OR "asp.net mvc" OR blazor) AND (angular OR react OR "razor pages") NOT (recruiter OR bootcamp OR instructor)

Desktop, mobile and migration

4. WPF desktop developer — Dice resume search
("c#" OR csharp) AND (wpf OR winforms OR "windows forms") AND (mvvm OR xaml)

5. .NET MAUI or Xamarin mobile developer — LinkedIn general search
(".net maui" OR "maui developer" OR xamarin OR "xamarin.forms") AND ("c#" OR csharp) AND (ios OR android) NOT (unity OR "game developer")

6. .NET Framework to modern .NET migration — LinkedIn general search
(".net developer" OR "c# developer" OR "senior software engineer") AND (".net framework" OR wcf OR "web forms" OR webforms) AND (".net core" OR ".net 8" OR ".net 10" OR "asp.net core") AND (migration OR migrated OR modernization OR upgrade)

Domain, credentials and the public web

7. C# developer in healthcare — Dice resume search
(".net" OR "c#") AND ("asp.net core" OR "web api") AND (hl7 OR fhir OR hipaa OR "electronic health record")

8. .NET developer with a Microsoft Azure certification — LinkedIn Recruiter, Keywords filter
(".net developer" OR "c# developer" OR "software engineer") AND ("azure developer associate" OR "az-204" OR "azure ai cloud developer associate" OR "ai-200") AND ("asp.net core" OR ".net core")

9. Public GitHub accounts by language and city — GitHub user search
language:csharp location:"dallas" repos:>5

10. Public LinkedIn profiles by framework and metro — Google X-ray
site:linkedin.com/in "c# developer" "asp.net core" "dallas" -jobs -recruiter

For public resumes, the same idea works as a filetype search: filetype:pdf "c# developer" resume "asp.net core" -template -sample. Every X-ray and GitHub result reaches only what someone has made public, and most enterprise .NET code lives in private company repositories.

What LinkedIn, Dice, GitHub and Google actually support

LinkedIn's Boolean help page says, as of November 2026, that AND, OR and NOT must be typed in capitals, that quotes mark exact phrases and parentheses are the only grouping symbols, and that wildcards are not supported. It evaluates quotes first, then parentheses, NOT, AND and finally OR. The page says nothing about the pound sign or a leading dot, so do not trust "c#" or ".net" alone: run the string once with "c#" and once with csharp and compare. If search ignores the symbols, .NET reads as "net" (net revenue, net promoter score) and C# as the letter "c." A quoted phrase such as "asp.net core" or "c# developer" is safer than either symbol on its own. LinkedIn Recruiter's Boolean page lists Job titles, Companies and Skills and Assessments among its Boolean filters and warns that too many facets in one query can cause a search result issue, so split long strings across fields.

Dice's guide says to quote keywords that contain spacing or punctuation, with ".net" as its example, and that its database fills in word endings automatically. It also warns that NOT removes every candidate with the term anywhere in the resume, which is why the exclusions above stay short. GitHub's user search documents language:, location: and repos: qualifiers, and says language: matches users with a majority of their repositories in that language; in our test on November 10, 2026, language:csharp and language:"c#" returned the same accounts. Google's search operators page documents quotes, site:, the minus sign, filetype: and the before: and after: date operators, but not OR and nothing about C#, so string 10 avoids both.

Narrowing by domain, hosting and seniority

After the framework, the client's domain narrows a .NET search best. Insurers, banks, healthcare systems and government contractors run large C# estates, and their developers write about claims, payments, HL7 interfaces or case management. Add the two or three words the client's engineers use about their own system as a separate AND block.

Hosting is the second filter. A team on Windows servers writes IIS, Windows services and SQL Server Agent; a cloud team writes Azure App Service, Functions, containers and Azure DevOps or GitHub Actions pipelines. Ask which one the client runs, and whether the role moves from the first to the second. For seniority, look for "designed," "led the migration," "owned the service," "code reviews" and "mentored." LinkedIn's premium search filters page lists Years of Experience and Seniority Level only for Recruiter and Sales Navigator, as of November 2026.

False positives worth excluding with NOT

  • Unity game developers. Unity's scripting manual covers creating C# scripts to control an application, so C# alone returns game and AR developers. Exclude "unity" and "game developer" unless the client builds simulations in Unity.
  • Maui, the island. "maui" on its own also matches people who live or work on Maui. Use ".net maui" or "maui developer."
  • Low-code and platform configurers. Power Platform, SharePoint and Dynamics 365 specialists list C# for small plugins. Fine for a Dynamics role; for an application developer role, require ASP.NET Core or Entity Framework.
  • Test automation engineers. Many SDETs write Selenium and NUnit tests in C#. Exclude "sdet" and "test automation" for development roles, and drop that exclusion when testing is the hire.
  • Recruiters, IT staffing sales and trainers. Their headlines say "hiring .NET developers" or "C# instructor." Exclude "recruiter," "talent acquisition" and "instructor."
  • Students and bootcamp graduates, for senior roles. Course projects list every framework in the table. Exclude "student," "intern" and "bootcamp" when the client needs production experience, and keep them when it is hiring juniors.

None of these strings targets or excludes anyone by age, sex, race, religion, national origin, disability or veteran status, and yours should not either; leave out proxies such as graduation years and names.

A worked example: three passes on a .NET Framework migration search

An invented search, shown as it actually gets narrowed.

Intake: A health insurer's claims portal runs on .NET Framework 4.8 with WCF services on IIS. It needs a senior C# developer to move it to ASP.NET Core on .NET 10 in Azure. Not looking for game developers, SDETs or developers who have only built new services.

Pass 1: "c#" AND ".net": a very large list mixing junior developers, Unity developers, SDETs and recruiters.

Pass 2: ("senior .net developer" OR "senior c# developer") AND "asp.net core" AND azure NOT (unity OR sdet OR recruiter): relevant, but much of the list has only worked on new cloud projects.

Pass 3: add AND (wcf OR ".net framework" OR "web forms") AND (migration OR migrated OR upgrade). Those terms come from developers who have carried an old application across. The list is short enough to call, and the screen asks what they moved first, how they replaced WCF and what broke in production.

For a migration role, the old platform is the filter. The new framework shows where a developer has arrived; WCF and Web Forms show whether they have made the trip the client is about to make, and with .NET 8 out of support since November 10, 2026, many clients are making it now.

What a search cannot verify

A string can find someone whose profile names the right framework and version. It cannot show whether they designed the services or patched someone else's, how they debug a production incident, or whether a listed certification is current. Microsoft's transcript page lets a certification holder select "Share link" to send an employer an online transcript, so ask for that link rather than a badge image. Then use the software engineer phone screen questions for the first call, the interview guide for software engineers for the technical rounds, and the software engineer job description template to write the posting the search is built from. When the client will consider strong backend developers new to C#, the Java strings find the closest neighbors.

Questions people ask

Does LinkedIn search understand C# and .NET?

LinkedIn's Boolean help page, as of November 2026, documents AND, OR, NOT, quotes and parentheses, but it does not say how search reads the pound sign in C# or the leading dot in .NET. Write both forms of each name, such as "c#" OR csharp and ".net" OR dotnet, pair them with a phrase like "asp.net core", and compare the results with and without the symbol.

Which .NET versions should a recruiter search for in November 2026?

Microsoft's support policy lists .NET 10, a long-term support release from November 11, 2025, and .NET 11, a standard-term release from November 10, 2026, as the supported versions. .NET 8 and .NET 9 reached end of support on November 10, 2026, so developers who have moved applications off them are in demand. .NET Framework 4.8.1 is a separate product that follows the Windows lifecycle.

Is the AZ-204 certification still worth searching for?

As an optional signal, yes. Microsoft retired the Azure Developer Associate certification (exam AZ-204) on July 31, 2026 and named the Azure AI Cloud Developer Associate (exam AI-200) as its replacement, but it says earned credentials stay valid until they expire. Search both names in one OR block, never require either, and ask the candidate for their Microsoft Learn transcript link to check one.

How do I keep Unity game developers out of a .NET search?

Unity's own manual describes creating C# scripts to control a game or application, so C# alone brings back game developers. Require a business framework such as ASP.NET Core, Entity Framework or Web API, and add NOT (unity OR "game developer") unless the client builds simulations or training software in Unity.