Skip to main content
ProductsDesktop toolsTASTECADDrawing reviewTASTEFILESFile managementTASTEFTPFile transferTASTESSHRemote workspaceTASTEZIPCompression and extractionDeveloper toolsTASTECODERust integrated development environmentTASTESTUDIOIntegrated development and test environmentTASTEETLData integration (ETL)ServersTASTEREMOTERemote desktop serverTASTEGEOGeospatial serverTASTEMAILMail workspaceGet startedDownloadsDocumentationBuyAll products
Marketplace
News
TechNewsToday's dev newsDeveloper docsProgramming languagesRustTypeScriptJavaScriptPythonGoC#JavaCC++KotlinDartWeb front-end frameworksNext.jsReactVue.js · NuxtSvelteKitAngularServer frameworksSpring BootDjangoFastAPIASP.NET CoreNestJS · ExpressApp & desktop frameworksTauriFlutterReact NativeElectronAlgorithmsAlgorithm basicsCore algorithmsAdvanced algorithmsPractical algorithms
CommunityProjectsDevelopment logsPromptsAI tool issuesShowcaseCommunity guide
Work with usTech transferWebsite buildDesktop app buildRelease and payment pipelineSales partnerContact
ServicesRemote desktopCustom installer packages
TASTEDEV
Products

Desktop tools

TASTECADComplex drawings, opened with easeTASTEFILESJust the files you need, as fast as possibleTASTEFTPThe tidiest path for your filesTASTESSHA stronger link between you and your serversTASTEZIPPack faster, unpack safer

Developer tools

TASTECODEEdit, build, debug and test Rust apps in one windowTASTESTUDIOFrom editing to remote tests and approved AI fixesTASTEETLMove data while you watch the values

Servers

TASTEREMOTEA remote desktop you run on your own serverTASTEGEORebuilding a GeoServer-compatible geospatial server in RustTASTEMAILTake back control of your email

Get started

DownloadsLatest builds of every productDocsHow to use each productBuySubscriptions and perpetual licencesAll productsEvery product at a glance
All products
MarketplaceNews
Tech

News

Today's dev newsOfficial announcements on languages, frameworks, GitHub and AIDeveloper docsGuides to languages, frameworks and algorithms

Programming languages

RustTypeScriptJavaScriptPythonGoC#JavaCC++KotlinDart

Frameworks

Web front-end frameworksNext.jsReactVue.js · NuxtSvelteKitAngular
Server frameworksSpring BootDjangoFastAPIASP.NET CoreNestJS · Express
App & desktop frameworksTauriFlutterReact NativeElectron

Algorithms

Algorithm basicsComplexity analysis · Sorting · Searching · Basic data structures · Trees and heapsCore algorithmsGraph traversal · Shortest paths & minimum spanning trees · Dynamic programming · Greedy algorithms · Divide and conquer · BacktrackingAdvanced algorithmsString algorithms · Math and number theory · Bit manipulation · Segment trees · Union-findPractical algorithmsCoding interview strategy · LRU cache · Rate limiting · Consistent hashing
All development docs
Community
ProjectsDiscover builders and their workDevelopment logsDecisions and lessons learnedPromptsReusable instructionsAI tool issuesProblems and workarounds for Claude, Codex, GeminiShowcaseFinished resultsCommunity guideHow we build in the open
Work with us
Tech transferNative apps in Rust and eguiWebsite build10 languages, accounts, docs and downloadsDesktop app buildRust and egui, no WebViewRelease and payment pipelineSigning, MSI, deb, rpm, AppImage, hashesSales partnerRecommend us and earn 30%ContactBuilds, partnerships and investment
Services
Remote desktopReach your computer from a browserCustom installer packagesOnly the features you need, settings preloaded
Buy
EN
한국어EnglishDeutschEspañolFrançaisItalianoPortuguês (Brasil)日本語简体中文繁體中文
Log in
Log in
TASTEDEV

From small tools to better development.

support@tastedev.netSupport TASTEDEV
ProductsProduct lineupBuyDocsDownloadsMarketplaceSupport
CommunityProjectsDevelopment logsPromptsAI tool issuesShowcase
PoliciesPrivacy policyTerms of serviceSubscription termsRefund policyCommunity guidelines
AccountLog inSign up
Visitors
Today
012345678901234567890123456789012345678901234567890123456789
Yesterday
012345678901234567890123456789012345678901234567890123456789
Total views
0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
Company
GXSOFT
Representative
CHOI YOUNG GU
Business registration number
853-44-00368
Address
9F V24, 351 Gyeongin-ro, Michuhol-gu, Incheon, Republic of Korea
Phone
+82-10-4404-1523
Email
whitecalvin@tastedev.net
Privacy officer
CHOI YOUNG GU

© 2026 TASTEDEVProduct information is based on verified development sources.Released · improving

C# docs
C#
Getting Started with CSyntax BasicsTypes and DataProjects and PackagesErrors and TestingKey Concepts: LINQ, Delegates, and Async
Discussions

C# guide · 1/6

Getting Started with C

C# is a statically typed, object-oriented language from Microsoft that runs on .NET, an open-source, cross-platform runtime. The same language and toolchain cover command-line tools, web APIs, desktop apps, Unity games, and cloud services. In this chapter you will install the .NET SDK, create and run a first project, look inside the project file, and set up an editor.

Installing the .NET SDK

To build C# code you need the .NET SDK. It bundles the compiler, the dotnet command-line tool, the base class libraries, and the runtime. Machines that only run apps can get by with the runtime alone, but your development machine needs the full SDK.

  • Download installers for Windows, macOS, and Linux from the .NET download page. Unless you have a reason not to, pick the current long-term support (LTS) release.
  • Package managers work too: winget on Windows, Homebrew on macOS, and your distribution's package manager or Microsoft's package feed on Linux.
  • Installing Visual Studio with the .NET development workload also installs the SDK.

Open a fresh terminal afterwards and check the installation:

dotnet --version
dotnet --list-sdks
dotnet --info

dotnet --version prints the SDK currently in use, and dotnet --list-sdks shows every installed SDK. Multiple SDKs can live side by side; each project declares which framework version it targets.

Your First Project

dotnet new scaffolds projects from templates. The console app template is called console:

dotnet new console -o HelloApp
cd HelloApp
dotnet run

The -o HelloApp option creates a HelloApp folder and puts the project inside it. You get two files, HelloApp.csproj and Program.cs, and dotnet run prints Hello, World!. The whole program is a single line:

// Program.cs
Console.WriteLine("Hello, World!");

There is no class and no Main method because of top-level statements: the compiler generates the entry point around the statements in this file for you. Command-line arguments arrive in a predefined args variable:

if (args.Length == 0)
{
    Console.WriteLine("Usage: dotnet run -- <name>");
    return;
}

var name = args[0];
Console.WriteLine($"Hello, {name}! Today is {DateTime.Now:yyyy-MM-dd}.");

Run it with dotnet run -- Alice. Everything after -- is passed to your program; options before it belong to dotnet run itself.

The Project File (.csproj)

The .csproj file is an MSBuild XML document describing what to build and how. The template generates something like this:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net10.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

</Project>
SettingWhat it does
Sdk="Microsoft.NET.Sdk"Uses the standard build rules for .NET projects. Web projects use Microsoft.NET.Sdk.Web.
OutputTypeExe produces an executable; leave it out to build a class library (.dll).
TargetFrameworkThe .NET version you target. The template fills in a value that matches your SDK.
ImplicitUsingsAutomatically imports common namespaces such as System, System.IO, and System.Linq.
NullableTurns on nullable reference type analysis (covered in chapter 3).

SDK-style projects include every .cs file under the project folder automatically, so adding a new source file never requires editing the project file.

Building and Running

These are the commands you will use most often:

dotnet build                 # build the Debug configuration
dotnet build -c Release      # build the Release configuration
dotnet run                   # build, then run
dotnet watch                 # rebuild and rerun whenever files change
dotnet clean                 # remove build outputs

Compiled output lands in bin/Debug/<target framework>/, and intermediate files go to obj/. Both folders can be regenerated at any time, so keep them out of source control. Running dotnet new gitignore drops a .NET-flavored .gitignore into the current folder.

Setting Up an Editor

C# has excellent tooling. Any of the following gives you completion, refactoring, and debugging out of the box:

  • Visual Studio: a full IDE for Windows with the richest debugger and profiler.
  • Visual Studio Code: a lightweight editor; add the C# Dev Kit extension for a solution explorer, test explorer, and debugger.
  • JetBrains Rider: a cross-platform IDE that behaves the same on Windows, macOS, and Linux.

Whatever you choose, dotnet format keeps code style consistent. Commit an .editorconfig at the repository root so indentation, naming rules, and warning levels are shared by the whole team.

Summary

  • C# development requires the .NET SDK; verify it with dotnet --version.
  • Create a project with dotnet new console and run it with dotnet run.
  • Top-level statements in Program.cs form the entry point, and arguments come in through args.
  • The .csproj file is an MSBuild document that sets the target framework, output type, and compiler options.
  • Pick Visual Studio, VS Code with C# Dev Kit, or Rider, and use dotnet format to keep style consistent.
Questions about this chapter?
Next chapterSyntax Basics

0 comments

Top commentsNewest first

Sign in · Sign in to leave a comment.