@emer-connelly_2117 very cool, thanks for sharing!!

Ahh that could be it, I will update to latest version and try it again :)

Hi @bryan-ellis_2367 , I'm not an Azure DevOps expert, but last I checked, it's not possible to add NuGet package sources other than it's own ADO Packages product or the public repositories. That may just refer to "upstream sources", but I'm not totally sure. However, if you want to use the ADO Pipeline's built-in NuGet commands to publish packages, I guess you can set up a service connection using this? https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml#nuget-service-connection Not totally sure -- but please let us know what you find :) Cheers, Alana

I think that guide is more for when you host a domain controller in azure as IaaS. Im after connecting to Azure AD in the form of SAML, or OpenIDConnect (Federation) I'll keep an eye on release notes to see when SSO gets released. Thanks

The situation with Azure is a bit confusing; I will put a note in to the docs team that it should support asset storage, but it can not support large/chunked uploads because of the limitations of the blob storage API that Alana mentioned.

That's the error from the SCM, but the .NET error is also logged. You may want to try running the service interactively in this case, then you can see the error message and identify what's wrong with the db connection.

Definitely! We're really not thrilled on how the current legacy Actions work (they were built by a third party, and also during a time that Azure underwent so many changes), so we'd like to update them to make more sense and be more useful... We'd love to understand your usecases, and how we can make the BuildMaster/Otter Azure integrations great. It'd be quite a bit easier to do this outside of Q&A though, so let's get in touch via email!

Yes, although this is currently extensible by extending the UserDirectory class.

I managed to perform the upgrade. I had to stop IIS before running the process and run the following command: ProGetSetup4.0.9.exe /Upgrade /S /BackupDatabase=false

Thanks Alana, I will have to run the install as a service account to make sure it has access to SQL. I didn't expect it connects to SQL server as it unpacks the resources. So, it didn't cross my mind that this would be an issue. I have not yet validated if the issue is resolved, but I am 99% sure it will be. I will reply to the post once I confirm it.

We made and tested several changes to the installer a while back, but it's not something we regularly test/verify. Please share what you find work! Thanks.

This question was resolved via other means, but the solution would be to upgrade to v4.5+ of the Azure extension.

I'm not sure the component we use to FTP supports negated wildcards, but you can simply add a Delete Files action before this that operates on *.config Alternatively (if you don't want to delete because you may re-use the files), you can use the Synchronize/Transfer Files action to a temporary directory (e.g. ~\Ftp) and use a !*.config mask on that to not transfer the configs, then use the FTP action from ~\Ftp as the source directory.

That action will package and deploy in much the same way as Visual Studio does when you click "Publish" for the solution, so it should only include the correct transformed configuration based on the publish profile selected.

Wow! Talk about agile, thank you for the quick turn around.

I figured out the problem was with the cloud service name. I was including the build number in the name and it just so happens that build number includes the {Major}.{Minor} numbers. The period was ultimately throwing it off. If you want to include the build number, then you have to use a url friendly number.

Thanks for the Answer Alex, I was able to get this to work. Maybe there should be a screenshot showing the Test environment's setup?