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: docs/deployment/clickonce-and-authenticode.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ ms.workload:
27
27
## Authenticode and code signing
28
28
A *digital certificate* is a file that contains a cryptographic public/private key pair, along with metadata describing the publisher to whom the certificate was issued and the agency that issued the certificate.
29
29
30
-
There are various types of Authenticode certificates. Each one is configured for different types of signing. For [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications, you must have an Authenticode certificate that is valid for code signing. If you attempt to sign a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application with another type of certificate, such as a digital e-mail certificate, it will not work. For more information, see [Introduction to code signing](http://go.microsoft.com/fwlink/?LinkId=179452).
30
+
There are various types of Authenticode certificates. Each one is configured for different types of signing. For [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applications, you must have an Authenticode certificate that is valid for code signing. If you attempt to sign a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application with another type of certificate, such as a digital e-mail certificate, it will not work. For more information, see [Introduction to code signing](https://docs.microsoft.com/windows/desktop/seccrypto/cryptography-tools).
31
31
32
32
You can obtain a certificate for code signing in one of three ways:
33
33
@@ -66,4 +66,4 @@ ms.workload:
66
66
-[ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md)
> For the best version control experience on macOS, we recommend using Git instead of Team Foundation Version Control (TFVC).
16
16
Git is supported in Visual Studio for Mac and is the default option for repositories hosted in Team Foundation Server (TFS)/Azure DevOps. To learn more about using Git with TFS/Azure DevOps, see the [Setting up a Git Repository](/visualstudio/mac/set-up-git-repository) article.
17
+
>
18
+
> If you previously used the preview release of the TFVC extension for Visual Studio for Mac, it is no longer supported when upgrading to Visual Studio 2019 for Mac.
17
19
18
20
Azure Repos provides two models of version control: [Git](/azure/devops/repos/git/?view=azure-devops), a distributed version control system, and [Team Foundation Version Control](/azure/devops/repos/tfvc/index?view=azure-devops) (TFVC), a centralized version control system.
19
21
@@ -107,6 +109,8 @@ To learn more about the commands mentioned here, or others, you can use the foll
107
109
> [!NOTE]
108
110
> For the best version control experience on macOS, we recommend using Git instead of Team Foundation Version Control (TFVC).
109
111
Git is supported in Visual Studio for Mac and is the default option for repositories hosted in Team Foundation Server (TFS)/Azure DevOps. To learn more about using Git with TFS/Azure DevOps, see the [Setting up a Git Repository](/visualstudio/mac/set-up-git-repository) article.
112
+
>
113
+
> If you previously used the preview release of the TFVC extension for Visual Studio for Mac, it is no longer supported when upgrading to Visual Studio 2019 for Mac.
110
114
111
115
In the Visual Studio for Mac Extension gallery, there is a Team Foundation Version control extension that offers limited support to connect to TFVC. The extension is not supported and has several known issues, so your experience may vary when using it.
> For the best version control experience on macOS, we recommend using Git instead of Team Foundation Version Control (TFVC).
16
16
Git is supported in Visual Studio for Mac and is the default option for repositories hosted in Team Foundation Server (TFS)/Azure DevOps. To learn more about using Git with TFS/Azure DevOps, see the [Setting up a Git Repository](/visualstudio/mac/set-up-git-repository) article.
17
+
>
18
+
> If you previously used the preview release of the TFVC extension for Visual Studio for Mac, it is no longer supported in Visual Studio 2019 for Mac.
17
19
18
20
Azure Repos provides two models of version control: [Git](/azure/devops/repos/git/?view=azure-devops), a distributed version control system, and [Team Foundation Version Control](/azure/devops/repos/tfvc/index?view=azure-devops) (TFVC), a centralized version control system.
19
21
20
22
Visual Studio for Mac provides full support for Git repositories, but requires some workarounds to work with TFVC. If you're using TFVC for version control today, here are some solutions you can use to access your source code hosted in TFVC:
21
23
22
24
*[Use Visual Studio Code and the Azure Repos extension, for a graphical UI](#use-visual-studio-code-and-the-azure-repos-extension)
23
25
*[Connect to your repo using the Team Explorer Everywhere Command Line Client (TEE-CLC)](#connecting-using-the-team-explorer-everywhere-command-line-client)
24
-
*[Connect to TFVC using the (unsupported) Team Foundation Version Control extension for Visual Studio for Mac](#connect-to-tfvc-using-the-team-foundation-version-control-extension)
25
26
26
27
The rest of this article walks you through the options listed above.
27
28
@@ -102,170 +103,6 @@ To learn more about the commands mentioned here, or others, you can use the foll
102
103
103
104
`tf help`
104
105
105
-
## Connect to TFVC using the Team Foundation Version Control extension
106
-
107
-
> [!NOTE]
108
-
> For the best version control experience on macOS, we recommend using Git instead of Team Foundation Version Control (TFVC).
109
-
Git is supported in Visual Studio for Mac and is the default option for repositories hosted in Team Foundation Server (TFS)/Azure DevOps. To learn more about using Git with TFS/Azure DevOps, see the [Setting up a Git Repository](/visualstudio/mac/set-up-git-repository) article.
110
-
111
-
In the Visual Studio for Mac Extension gallery, there is a Team Foundation Version control extension that offers limited support to connect to TFVC. The extension is not supported and has several known issues, so your experience may vary when using it.
112
-
113
-
To install the extension, launch Visual Studio for Mac and choose the **Visual Studio > Extensions** menu. In the **Gallery** tab, select **Version Control > Team Foundation Version Control for TFS and Azure DevOps** and click **Install...**:
114
-
115
-
116
-
117
-
Follow the prompts to install the extension. Once it's installed, restart the IDE.
118
-
119
-
### Updating the extension
120
-
121
-
Updates to the TFVC extension are made periodically. To access updates, choose **Visual Studio > Extensions...** from the menu and select the **Updates** tab. Select the extension in the list and press the **Update** button:
122
-
123
-
Press **Install** on the next dialog to uninstall the old package and install the new one.
124
-
125
-
### Using the extension
126
-
127
-
Once the extension is installed, select the **Version Control > TFS/Azure DevOps > Open from Remote Repository...** menu item.
128
-
129
-
130
-
131
-
Choose either VSTS or Team Foundation Server to get started and press **Continue**:
132
-
133
-
134
-
135
-
#### Azure Repos Authentication
136
-
137
-
When you select a project that is hosted on Azure Repos, you're prompted to enter your Microsoft account details:
138
-
139
-
140
-
141
-
#### TFS Authentication
142
-
143
-
To connect to TFS, enter the server details and your account credentials. Enter a domain to use NTLM authentication, otherwise leave blank to use basic authentication. Select **Add Server**:
144
-
145
-
146
-
147
-
### Selecting a project
148
-
149
-
Once you've successfully authenticated, you can see a list of repositories that are associated with the account in the **Open from Source Control** dialog:
150
-
151
-
152
-
153
-
This dialog is organized with the following nodes:
154
-
155
-
- Azure DevOps organization or collection – This displays all organizations connected to the Microsoft account you logged in with.
156
-
- Projects - In each organization or collection, you can have a number of projects. A project is where source code, work items, and automated builds are hosted.
157
-
158
-
At this point, you can search and filter by the name of a project or organization.
159
-
160
-
#### Adding a new server
161
-
162
-
To add a new server to the list, press the **Add Host** button on the **Open from Source Control** dialog:
163
-
164
-
165
-
166
-
Select the provider from the list, and enter your credentials:
167
-
168
-
169
-
170
-
### Creating a new workspace
171
-
172
-
To start working with a project, you need to have a _workspace_. If you don't already have a workspace, you can create one from the **Workspace** combobox in the **Open from Source Control** dialog:
173
-
174
-
175
-
176
-
Set the name and local path for your new workspace and select **Create Workspace**:
177
-
178
-
179
-
180
-
### Using the Source Code Explorer
181
-
182
-
Once you've created a workspace and mapped your project, you can start working with the _Source Code Explorer_.
183
-
184
-
To open the Source Code Explorer, select the **Version Control > TFS/Azure DevOps > Source Control Explorer** menu item.
185
-
186
-
The Source Code Explorer enables you to navigate through all the mapped projects, their files, and folders. It also allows you to perform all the basic source control actions such as:
187
-
188
-
- Get the latest version
189
-
- Get a specific version
190
-
- Check files in and out
191
-
- Lock and unlock files
192
-
- Add, delete, and rename files
193
-
- View history
194
-
- Compare changes.
195
-
196
-
Many of these actions are available through context actions on the project:
197
-
198
-
199
-
200
-
### Managing workspaces
201
-
202
-
If you haven't already created a workspace, as described in the [Creating a workspace](#creating-a-new-workspace) section, you'll notice that the Source Code Explorer is empty:
To set up your remote project with a local workspace, use the following steps:
207
-
208
-
1. Select the **Server** from the combobox.
209
-
1. Note that there are "no workspaces" and that the Local Path is "Not Mapped". Select the **Not Mapped** link to display the **Create new Workspace** dialog.
210
-
1. Provide a name for the workspace and then click **Add Working Folder** to map the project to a local folder on your computer:
211
-
212
-
213
-
214
-
1. Select the "$" folder to map all projects on your server to the same workspace, or select an individual project, and click **OK**:
215
-
216
-
217
-
218
-
1. Select the location on your local machine that you wish to map the project(s) to and click **Select Folder**.
219
-
1. Confirm the details of the new workspace by pressing **OK**
220
-
221
-
222
-
223
-
Once your workspace is set up, it can be changed or removed by clicking the **Manage Workspaces** button in the Source Code Explorer.
224
-
225
-
226
-
227
-
## Troubleshooting and Known Issues
228
-
229
-
#### Problems using basic authentication
230
-
231
-
The following options can be used to authenticate with a server:
232
-
233
-
- Oauth
234
-
- Basic
235
-
- Ntlm
236
-
237
-
To use basic authentication it is necessary to enable **Alternative authentication credentials** in Azure DevOps Services, by following the steps below:
238
-
239
-
1. Sign in to your Azure DevOps organization as the owner (https:\//dev.azure.com/{organization}/{project}).
240
-
241
-
2. From your organization toolbar, select the gear icon and select **Policy**:
To set up Team Foundation Version Control (TFVC) on your dev machine, you **must** create a workspace, as described in the [Managing workspaces](#managing-workspaces) section.
252
-
253
-
In Source Control Explorer, press the **Manage Workspaces** Button. Follow the steps to map the project to a folder on your dev machine.
254
-
255
-
#### I do not see any / all of my projects
256
-
257
-
After authenticating you should see the list of projects. By default, only TFS projects are shown. To see other types of projects, check the "See all projects" box.
258
-
259
-
Keep in mind that projects that are on the server will not appear if you don't have the correct privileges.
260
-
261
-
##### I am getting the error "Cannot create the workspace. Please, try again"
262
-
263
-
When trying to [create a new workspace](#creating-a-new-workspace), you should make sure the following conditions are met:
264
-
265
-
- No use of invalid characters in the workspace name.
266
-
- The name must be less than 64 characters.
267
-
- The local path cannot be used by any other workspaces.
268
-
269
106
### See also
270
107
271
108
-[Develop and share your code in TFVC using Visual Studio (on Windows)](/azure/devops/repos/tfvc/share-your-code-in-tfvc-vs)
0 commit comments