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
sudo sed -i -e 's/deb mirror/deb [arch=amd64] mirror/g' /etc/apt/sources.list
59
+
echo "deb [arch=arm64] http://ports.ubuntu.com/ubuntu-ports noble main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/arm64.list
60
+
echo "deb [arch=arm64] http://ports.ubuntu.com/ubuntu-ports noble-updates main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/arm64.list
61
+
echo "deb [arch=arm64] http://ports.ubuntu.com/ubuntu-ports noble-backports main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/arm64.list
62
+
echo "deb [arch=arm64] http://ports.ubuntu.com/ubuntu-ports noble-security main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/arm64.list
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Below is our guidance for how to report issues, propose new features, and submit
4
4
5
5
## Open Development Workflow
6
6
7
-
The Windows Package Manager Manifest Creator team is VERY active in this GitHub Repository. In fact, we live in it all day long and carry out all our development in the open!
7
+
The Windows Package Manager team is VERY active in this GitHub Repository. In fact, we live in it all day long and carry out all our development in the open!
8
8
9
9
When the team finds issues we file them in the repository. When we propose new ideas or think-up new features, we file new feature requests. When we work on fixes or features, we create branches and work on those improvements. And when PRs are reviewed, we review in public - including all the good, the bad, and the ugly parts.
Copy file name to clipboardExpand all lines: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,22 +72,22 @@ You can also check out this [episode of Open at Microsoft](https://learn.microso
72
72
73
73
### Using the standalone exe:
74
74
75
-
The latest version of the standalone exe can be found at https://aka.ms/wingetcreate/latest, and the latest preview version can be found at https://aka.ms/wingetcreate/preview, both of these require [.NET Runtime 6.0](https://dotnet.microsoft.com/en-us/download/dotnet/6.0) to be installed on the build machine. To install this on your build machine in your pipeline, you can include the following dotnet task:
75
+
The latest version of the standalone exe can be found at https://aka.ms/wingetcreate/latest, and the latest preview version can be found at https://aka.ms/wingetcreate/preview, both of these require [.NET Runtime 8.0](https://dotnet.microsoft.com/en-us/download/dotnet/8.0) to be installed on the build machine. To install this on your build machine in your pipeline, you can include the following dotnet task:
76
76
77
77
```yaml
78
78
- task: UseDotNet@2
79
79
displayName: 'Install .NET Runtime'
80
80
inputs:
81
81
packageType: sdk
82
-
version: '6.x'
82
+
version: '8.x'
83
83
installationPath: '$(ProgramFiles)\dotnet'
84
84
```
85
85
86
86
Or you can utilize a PowerShell task and run the following script.
@@ -158,11 +158,11 @@ You can install the prerequisites in one of two ways:
158
158
* The following workloads:
159
159
* .NET Desktop Development
160
160
* Universal Windows Platform Development
161
-
* Windows 11 SDK (10.0.22000.0) (Tools -> Get Tools and Features -> Individual Components)
161
+
* Windows 11 SDK (10.0.22621.0) (Tools -> Get Tools and Features -> Individual Components)
162
162
163
163
### Building
164
164
165
-
Open `winget-create\src\WingetCreateCLI.sln` in Visual Studio and build. We currently only build using the solution; commandline methods of building a VS solution should work as well.
165
+
Open `winget-create\src\WingetCreateCLI.sln` in Visual Studio and build. We currently only build using the solution; command-line methods of building a VS solution should work as well.
166
166
167
167
## Testing the client
168
168
@@ -181,7 +181,7 @@ Running unit and E2E tests are a great way to ensure that functionality is prese
181
181
* Direct link to GitHub [Personal Access Tokens page](https://github.com/settings/tokens).
182
182
* `GitHubAppPrivateKey`: Leave blank, this is only used by the build server.
183
183
184
-
* Set the solutionwide runsettings file for the tests
184
+
* Set the solution-wide runsettings file for the tests
185
185
* Go to `Test` menu > `Configure Run Settings` -> `Select Solution Wide runsettings File` -> Choose your configured runsettings file
0 commit comments