Microsoft.DotNet.ProjectTools

Prevents the virtual project's from being garbage collected when MSBuild's demotes it to a weak reference (which can happen when many SDK import files fill the cache during NuGet restore). Without this, nested <MSBuild> tasks that re-evaluate the project with different properties would fail to find the in the cache and try to load it from disk, resulting in MSB4025 because the virtual project file does not exist on disk.

Kept in sync with the default dotnet new console project file (enforced by DotnetProjectConvertTests.SameAsTemplate).

Parses a source file to extract property value from directives.

Array of frameworks if TargetFrameworks is specified, or empty otherwise

Obtains a temporary subdirectory for file-based app artifacts, e.g., /tmp/dotnet/runfile/.

Obtains a specific temporary path in a subdirectory for file-based app artifacts, e.g., /tmp/dotnet/runfile/{name}.

Evaluates against a and the file system.

All directives that need some other evaluation (described below) are expanded as MSBuild expressions (i.e., $() and @() are substituted with property and item values, etc.). #:project directives are resolved to full project file paths (e.g., if the evaluated value is a directory, finds a project in that directory). #:include/#:exclude have their determined and relative paths resolved relative to their containing file.

Warning: Settings from '{0}' are not used because '{1}' has precedence.

Cannot use launch profile '{0}' because the launch settings file could not be located. Locations tried: {1}

A profile with the specified name isn't a valid JSON object.

The 'profiles' property of the launch settings document is not a JSON object.

There are several launch profiles with case-sensitive names, which isn't permitted: {0} Make the profile names distinct.

A launch profile with the name '{0}' doesn't exist.

A usable launch profile could not be located.

The launch profile type '{0}' is not supported.

An error was encountered when reading '{0}': {1}

Path '{0}' specified in '{1}' is invalid.

(Default)

Unable to determine a temporary directory path. Consider configuring the TEMP environment variable on Windows or local app data folder on Unix.

File included via #:include directive (or Compile item) not found: {0}

This is an experimental feature, set MSBuild property '{0}' to 'true' to enable it.

The hashed mac address needs to be the same hashed value as produced by the other distinct sources given the same input. (e.g. VsCode)

When targeting netstandard2.0, the user of the source package must "implement" certain methods by declaring members in this type.

If , the whole is parsed to find diagnostics about every app directive. Otherwise, only directives up to the first C# token is checked. The former is useful for dotnet project convert where we want to report all errors because it would be difficult to fix them up after the conversion. The latter is useful for dotnet run file.cs where if there are app directives after the first token, compiler reports anyway, so we speed up success scenarios by not parsing the whole file up front in the SDK CLI.

Finds file-level directives in the leading trivia list of a compilation unit and reports diagnostics on them.

The builder to store the parsed directives in, or null if the parsed directives are not needed.

Size of whitespace that consists of only blank lines (i.e., lines that contain only whitespace).

Size of the remaining whitespace on a not-entirely-blank line.

Represents a C# directive starting with #: (a.k.a., "file-level directive"). Those are ignored by the language but recognized by us.

Represents a C# directive starting with #: (a.k.a., "file-level directive"). Those are ignored by the language but recognized by us.

Span of the full line including the trailing line break.

Additional leading whitespace not included in .

Additional trailing whitespace not included in .

#! directive.

#! directive.

#:sdk directive.

#:sdk directive.

#:property directive.

#:property directive.

#:package directive.

#:package directive.

#:project directive.

Preserved across calls, i.e., this is the original directive text as entered by the user.

This is the with MSBuild $(..) vars expanded. E.g. The expansion might be implemented via ProjectInstance.ExpandString.

This is the resolved via (i.e., this is a file path if the original text pointed to a directory).

Change and .

Change and .

Change only .

If the directive points to a directory, returns a new directive pointing to the corresponding project file.

#:ref directive. References another file-based app as a library.

Preserved across calls, i.e., this is the original directive text as entered by the user.

This is the with MSBuild $(..) vars expanded.

The resolved full path to the referenced .cs file.

Change and .

Change and .

Change only .

Resolves the path relative to the source file's directory.

#:include or #:exclude directive.

#:include or #:exclude directive.

Preserved across calls, i.e., this is the original directive text as entered by the user.

See .

Parses a in the format .protobuf=Protobuf;.cshtml=Content. Should come from MSBuild property with name .

Used for deduplication - compares directives by their type and name (ignoring case).

An adapter of that ensures we JSON-serialize only the necessary fields.

note: this type is only serialized for run-api scenarios. If/when run-api is removed, we would also want to remove the usage of System.Text.Json attributes.

Internal utilities copied from microsoft/MSBuild repo.

Converts a string to a bool. We consider "true/false", "on/off", and "yes/no" to be valid boolean representations in the XML. Modified from its original version to not throw, but return a default value.

The string to convert. Boolean true or false, corresponding to the string.

Returns true if the string represents a valid MSBuild boolean true value, such as "on", "!false", "yes"

Returns true if the string represents a valid MSBuild boolean false value, such as "!on" "off" "no" "!true"

Could not find any project in `{0}`.

Could not find project or directory `{0}`.

Found more than one project in `{0}`. Specify which one to use.

Invalid property name: {0}

The property directive needs to have two parts separated by '=' like '#:property PropertyName=PropertyValue'.

Unrecognized file extension in the '{0}' directive. Only these extensions are currently recognized: {1}

Static graph restore is not supported for file-based apps. Remove the '#:property'.

error

The directive should contain a name without special characters and an optional value separated by '{1}' like '#:{0} Name{1}Value'.

Some directives cannot be converted. Run the file to see all compilation errors. Specify '--force' to convert anyway.

Duplicate directives are not supported: {0}

Directives currently cannot contain double quotes (").

The '#:project' directive is invalid: {0}

The '#:ref' directive is invalid: {0}

Could not find file '{0}'.

Missing name of '{0}'.

Unrecognized directive '{0}'.

Each entry in 'FileBasedProgramsItemMapping' MSBuild property must have two parts separated by '='. The entry '{0}' is invalid.

Each entry in 'FileBasedProgramsItemMapping' MSBuild property must map from a non-empty file extension starting with '.'. The extension '{0}' in entry '{1}' is invalid.

Each entry in 'FileBasedProgramsItemMapping' MSBuild property must map to a non-empty item type. The item type '{0}' in entry '{1}' is invalid.