You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/dev-box/how-to-configure-team-customizations.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,21 +52,21 @@ To complete the steps in this article, you must:
52
52
## Choose a source for customization tasks
53
53
Dev Box tasks can be sourced from tasks built-in to the platform, or custom tasks stored in a catalog. Choose the source that best aligns with your customization needs and project requirements.
54
54
55
-
### Use WinGet and PowerShell tasks
56
-
Dev Box dev centers support PowerShell and WinGet tasks out of the box. If your customizations require only PowerShell and WinGet, proceed with creating your customizations file: [Create an image definition file](#create-an-image-definition-file).
55
+
-**Use WinGet and PowerShell tasks**
56
+
Dev Box dev centers support PowerShell and WinGet tasks out of the box. If your customizations require only PowerShell and WinGet, proceed with creating your customizations file: [Create an image definition file](#create-an-image-definition-file).
57
57
58
-
### Use a catalog to define custom tasks
59
-
You can create your own custom tasks. To make custom tasks available to your entire organization, attach a catalog that contains custom task definitions to your dev center. Dev Box supports Azure Repos and GitHub catalogs.
58
+
-**Use a catalog to define custom tasks**
59
+
You can create your own custom tasks. To make custom tasks available to your entire organization, attach a catalog that contains custom task definitions to your dev center. Dev Box supports Azure Repos and GitHub catalogs.
60
60
To learn more about defining custom tasks, see: [Create tasks for Dev Box team customizations](how-to-create-customization-tasks-catalog.md).
61
61
62
62
## Create image definitions at project level
63
63
Using a project can help manage Dev Box resources efficiently. By assigning each developer team their own project, you can organize resources effectively. You can attach a catalog that stores image definitions to a project to target developer teams.
64
64
65
-
### Assign permissions for project admins.
65
+
### 1. Assign permissions for project admins.
66
66
To attach a catalog to a project, you must have Project Admin or Contributor permission for the project.
67
67
To learn how to assign Project Admin permission, see [Grant administrative access to Microsoft Dev Box projects](how-to-project-admin.md).
68
68
69
-
### Enable project-level catalogs
69
+
### 2. Enable project-level catalogs
70
70
You must enable project-level catalogs at the dev center level before you can add a catalog to a project.
71
71
To enable the use of project-level catalogs at the dev center level:
72
72
1. In the [Azure portal](https://portal.azure.com/), navigate to your dev center.
@@ -84,17 +84,19 @@ You can create and manage image definition files by using VS Code. You can use t
84
84
1. Download an example YAML image definition file from the samples repository and open it in VS Code.
85
85
1. Discover tasks available in the catalog by using the command palette. Select **View** > **Command Palette** > **Dev Box: List Available Tasks For This Dev Box**.
86
86
87
-
:::image type="content" source="media/how-to-configure-team-customizations/dev-box-command-list-tasks.png" alt-text="Screenshot showing the Visual Studio Code command palette with the 'Dev Box: List Available Tasks For This Dev Box' option selected.":::
87
+
:::image type="content" source="media/how-to-configure-team-customizations/dev-box-command-list-tasks.png" alt-text="Screenshot showing the Visual Studio Code command palette with the 'Dev Box: List Available Tasks For This Dev Box' option selected.":::
88
88
89
89
1. Test customization in VS Code by using the command palette. Select **View** > **Command Palette** > **Dev Box: Apply Customizations Tasks**.
90
90
91
-
:::image type="content" source="media/how-to-configure-team-customizations/dev-box-command-apply-tasks.png" alt-text="Screenshot showing the Visual Studio Code command palette with the 'Dev Box: Apply Customizations Tasks' option selected.":::
91
+
:::image type="content" source="media/how-to-configure-team-customizations/dev-box-command-apply-tasks.png" alt-text="Screenshot showing the Visual Studio Code command palette with the 'Dev Box: Apply Customizations Tasks' option selected.":::
92
92
93
93
1. The image definition file runs and applies the specified tasks to your test dev box. Inspect the changes and check the VS Code terminal for any errors or warnings generated during the task execution.
94
94
1. When the image definition file runs successfully, upload it to your catalog.
95
95
96
96
## Optional: Customize your dev box by using existing WinGet Configuration files
97
-
WinGet configuration uses a config-as-code approach to define the software and settings needed to prepare your Windows environment for coding. You can also use these configuration files to set up a dev box, by using a WinGet task included in the Microsoft-provided quickstart catalog.
97
+
WinGet configuration uses a config-as-code approach to define the software and settings needed to prepare your Windows environment for coding.
98
+
99
+
You can also use these configuration files to set up a dev box, by using a WinGet task included in the Microsoft-provided quickstart catalog.
98
100
The following example shows a dev box image definition file that calls an existing WinGet Desired State Configuration (DSC) file:
99
101
100
102
```yaml
@@ -104,7 +106,7 @@ tasks:
104
106
configure: "projectConfiguration.dsc.yaml"
105
107
```
106
108
107
-
To learn more, see WinGet configuration.
109
+
To learn more, see [WinGet configuration](https://aka.ms/winget-configuration).
0 commit comments