d6c4972024 | ||
---|---|---|
.. | ||
.devcontainer | ||
.vscode | ||
test-project | ||
.npmignore | ||
README.md |
README.md
F# (.NET)
Summary
Develop F# and .NET based applications. Includes all needed SDKs, extensions, and dependencies.
Metadata | Value |
---|---|
Contributors | The VS Code Team, F# team |
Categories | Languages |
Definition type | Dockerfile |
Published image architecture(s) | x86-64, arm64/aarch64 for bullseye variants |
Works in Codespaces | Yes |
Container host OS support | Linux, macOS, Windows |
Container OS | Ubuntu |
Languages, platforms | .NET, .NET Core, F# |
Using this definition
Debug Configuration
Only the integrated terminal is supported by the Remote - Containers extension. You may need to modify your .vscode/launch.json
configurations to include the following:
"console": "integratedTerminal"
Note: Currently the Ionide-fsharp extension appears to force the use of an external console when clicking on the Debug icon in the F# Solution Explorer. You can configure a .NET application launch in launch.json
with the property above instead.
Enabling HTTPS in ASP.NET using your own dev certificate
To enable HTTPS in ASP.NET, you can mount an exported copy of your local dev certificate.
-
Export it using the following command:
Windows PowerShell
dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
macOS/Linux terminal
dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
-
Add the following in to
.devcontainer/devcontainer.json
:"remoteEnv": { "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere", "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx", }
-
Finally, make the certificate available in the container as follows:
If using GitHub Codespaces and/or Remote - Containers
- Start the container/codespace
- Drag
~/.aspnet/https/aspnetapp.pfx
from your local machine into the root of the File Explorer in VS Code. - Open a terminal in VS Code and run:
mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https
If using only Remote - Containers with a local container
Add the following to
.devcontainer/devcontainer.json
:"mounts": [ "source=${env:HOME}${env:USERPROFILE}/.aspnet/https,target=/home/vscode/.aspnet/https,type=bind" ]
If you've already opened your folder in a container, rebuild the container using the Remote-Containers: Rebuild Container command from the Command Palette (F1) so the settings take effect.
Installing Node.js or the Azure CLI
Given JavaScript front-end web client code written for use in conjunction with an ASP.NET back-end often requires the use of Node.js-based utilities to build, this container also includes nvm
so that you can easily install Node.js. You can change the version of Node.js installed or disable its installation by updating the args
property in .devcontainer/devcontainer.json
.
"args": {
"VARIANT": "3.1",
"NODE_VERSION": "14" // Set to "none" to skip Node.js installation
}
If you would like to install the Azure CLI, you can reference a dev container feature by adding the following to .devcontainer/devcontainer.json
:
{
"features": {
"azure-cli": "latest"
}
}
If you've already opened your folder in a container, rebuild the container using the Remote-Containers: Rebuild Container command from the Command Palette (F1) so the settings take effect.
Adding the definition to your folder
-
If this is your first time using a development container, please see getting started information on setting up Remote-Containers or creating a codespace using GitHub Codespaces.
-
Start VS Code and open your project folder or connect to a codespace.
-
Press F1 select and Add Development Container Configuration Files... command for Remote-Containers or Codespaces.
Note: If needed, you can drag-and-drop the
.devcontainer
folder from this sub-folder in a locally cloned copy of this repository into the VS Code file explorer instead of using the command. -
Select this definition. You may also need to select Show All Definitions... for it to appear.
-
Finally, press F1 and run Remote-Containers: Reopen Folder in Container or Codespaces: Rebuild Container to start using the definition.
Testing the definition
This definition includes some test code that will help you verify it is working as expected on your system. Follow these steps:
- If this is your first time using a development container, please follow the getting started steps to set up your machine.
- Clone this repository.
- Start VS Code, press F1, and select Remote-Containers: Open Folder in Container...
- Select the
containers/dotnetcore-fsharp
folder. - When prompted click "Restore" in the notification to restore packages.
- After the folder has opened in the container, press F5 to start the project.
- You should see "Hello Remote World from the F# Container!" in a terminal window after the program executes.
- From here, you can add breakpoints or edit the contents of the
test-project
folder to do further testing.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License. See LICENSE.