Comments on: 6 Steps to Automate Publishing a VSIX Extension with DevOps https://intellitect.com/blog/demystified-azure-pipeline-vsix-extension/ Complex Software Development - Simplified Thu, 21 Apr 2022 22:02:12 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Austen Frostad https://intellitect.com/blog/demystified-azure-pipeline-vsix-extension/#comment-385718 Tue, 29 Jun 2021 21:13:03 +0000 https://intellitect.com/?p=38092#comment-385718 In reply to Hector Flores.

Glad it was helpful!
I briefly looked into whether or not there were other options other than the PAT for creating the Visual Studio Marketplace Service Connection in the Devops project, but it still looks like the way its done. So yeah it requires maintenance based on the lifetime of the PAT :( So I guess set it to the max lifetime and mention its status in the project’s README.

]]> By: Hector Flores https://intellitect.com/blog/demystified-azure-pipeline-vsix-extension/#comment-385581 Mon, 14 Jun 2021 15:47:35 +0000 https://intellitect.com/?p=38092#comment-385581 This article is great! But I was wondering if there is a way to not rely on PAT token. Can a service principal or the pipelines underneath the principal using Oath Authentication be used instead? I know it has to be associated with an actual account, so it might be difficult, but I wondered if there is anything that can get closer to not using a PAT token for authentication. The reason is, if PAT token is used, manual maintenance is needed to keep the token up-to-date along with the need to rely on 1 user. This is not ideal for large organizations.

]]>