> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/developers/resources/dotnet-versions.md).

# .NET

A few important details about the Microsoft .NET platform

## Versions

We use each of these versions of .NET for specific purposes:

* [.NET Framework 4.8](https://versionsof.net/framework/4.8.1/)
* [.NET Standard 2.0](https://learn.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0)
* [.NET Core 9.0](https://versionsof.net/core/9.0/)

### Dependencies <a href="#dependencies" id="dependencies"></a>

.NET Framework and .NET Core dependencies can be summarized this way:

* You <mark style="color:$success;">**can**</mark> reference a .NET Standard assembly from .NET Framework and from .NET Core.
* You can <mark style="color:$danger;">**not**</mark> reference a .NET Core assembly from .NET Framework.
* You <mark style="color:$success;">**can**</mark> reference a .NET Framework assembly from .NET Core.

> .NET Framework does **not** support .NET Standard **2.1** and our .NET Framework assemblies need to reference .NET Standard assemblies. Therefore, we target .NET Standard **2.0** in a library that needs to be used by both .NET Framework and .NET Core.

## Development Tools <a href="#development-tools" id="development-tools"></a>

* Visual Studio 2022 is the recommended IDE for all .NET Framework development work.
* VS Code is the recommended IDE for all React development work.
* Either (or both) tools can be used for .NET Standard and .NET Core development work.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.shiftiq.com/developers/resources/dotnet-versions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.