Skip to content

AppDomain.FriendlyName doesn't include file extension in .NET (Core) #11028

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 3, 2025
Merged

AppDomain.FriendlyName doesn't include file extension in .NET (Core) #11028

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e47e527
Update AppDomain.xml
gewarren Feb 28, 2025
fb19f17
Update xml/System/AppDomain.xml
gewarren Mar 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions xml/System/AppDomain.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,6 @@
Application domains, which are represented by <xref:System.AppDomain> objects, help provide isolation, unloading, and security boundaries for executing managed code.

- Use application domains to isolate tasks that might bring down a process. If the state of the <xref:System.AppDomain> that's executing a task becomes unstable, the <xref:System.AppDomain> can be unloaded without affecting the process. This is important when a process must run for long periods without restarting. You can also use application domains to isolate tasks that should not share data.

- If an assembly is loaded into the default application domain, it cannot be unloaded from memory while the process is running. However, if you open a second application domain to load and execute the assembly, the assembly is unloaded when that application domain is unloaded. Use this technique to minimize the working set of long-running processes that occasionally use large DLLs.

> [!NOTE]
Expand Down Expand Up @@ -5804,9 +5803,8 @@ This method overload uses the <xref:System.AppDomainSetup> information from the
<format type="text/markdown"><![CDATA[

## Remarks
The friendly name of the default application domain is the file name of the process executable. For example, if the executable used to start the process is `"c:\MyAppDirectory\MyAssembly.exe"`, the friendly name of the default application domain is `"MyAssembly.exe"`.


The friendly name of the default application domain is the file name of the process executable. For example, if the executable used to start the process is `"c:\MyAppDirectory\MyAssembly.exe"`, the friendly name of the default application domain is `"MyAssembly.exe"`. (In .NET (Core) versions, the friendly name doesn't include the file extension.)

## Examples
The following code example uses the <xref:System.AppDomain.FriendlyName%2A> property to get the friendly name of the current application domain. For the default application domain, the friendly name is the name of the application's executable file. The code example also displays additional information about the application domain.
Expand Down