Is there an easy way to download the latest Universal package contents without running all the commands using the Azure CLI ?
In my project, we are storing the Installer generated from pipeline (of a .NET application) as a Universal Package in the Azure Artifacts. This is a ZIP file containing the Installer.
While it was easy to download the Zip file in TeamCity, it's a headache in Azure Devops. 30 people in my team has to download the Installer every week and we are looking for an easy way to download this (at least the latest universal package).
Is there an easy way to download the latest Universal package contents without running all the commands using the Azure CLI ?
To download the Universal package in Azure Devops, we could use the Universal packages taskļ¼
We could use wildcard in the Version option to get the highest version with major version.
BTW, there is an user voice about use the REST API to download the Universal package. If there is a REST API available, the ERST API will also be a good choice. You could vote that that up and leave your comment.
Related
I want to get some books to better work with Azure DevOps that is installed on-premise at work and I want to get the most recent book for the version/edition that is installed.
How can I know what is the version / edition we are using?
You can get the version number of the actually running instance by going to the following URL (adapt for your own environment):
http://<server:port>/<base Azure path without project name>/_home/about
For instance, if my project (name P1) url is
http://myserver:8080/azure/P1
The about page will be
http://myserver:8080/azure/_home/about
I've recently started using VSTS to build a Xamarin Forms App for iOS. I have it build using a hosted macos agent and then releasing it to a container in our Azure Blob Storage. The one thing I can solve at the moment, is how to include the Assembly Version in the name of the ipa file?
We're using an Enterprise license, so the ipa doesn't end up on any Store. At the moment I have the App_Name.ipa file and all previous versions App_Name.1.0.0.ipa in the container, however it's always App_Name.ipa that is downloaded.
I thought that it might be an option to parse the AssemblyInfor.cs file and extra the version and then set an environment variable - however I don't seem to be able to access the variable in the Release stage.
Ideally I'd like all this to stay is VSTS, however I don't mind trigger a WebJob to perform some extra tasks, however the version number doesn't appear to be accessible from the ipa file.
Can anyone suggest an approach?
You can use some related extension tasks to get Assembly Version from AssemblyInfor.cs files.
Such as you can use Assembly Info Reader task, and then you can get the Assembly Version by the variable $(AssemblyInfo.AssemblyVersion).
I'm using AppVeyor CI to build my UWP app and want to create an APPX package during every build. However my .gitignore is ignoring the Package.StoreAssociation.xml and MyAppName_StoreKey.pfx which I want to include in the APPX package as they are identifying my app in Windows Store.
Is there any way to get these files using PowerShell or MSBuild or something like that? In other words, is there any command line equivalent to the Project > Store > Associate App with the Store... wizard?
I know I can upload these files to the repo as Secure files but I'd prefer getting the latest files from the Dev Center with every build.
I would say probably not, as the Associate App with the Store Wizard, is an authenticated Wizard which requires a users Microsoft Account to be registered with Visual Studio, Load Credentials from storage or asking for OAuth, and then Visual Studio goes to Microsoft's server to Sign the Certificate and Sign the app with it.
AppVeyor documentation says the currently UWP is not officially supported for UWP, as a Microsoft License is required.
Edit: Does this help?
Is there any way to get these files using PowerShell or MSBuild or something like that? In other words, is there any command line equivalent to the Project > Store > Associate App with the Store... wizard?
No, as #William's explanation. The associating operation needs user's interaction in Visual Studio, this doesn't depend on a public command/API.
In my experience, we need to store(maintain) the latest store association information in somewhere, overwrite the related files and replace the reserved keywords in the app's manifest template file before packaging.
As of now the latest version of the Exchange Web Services Managed API is 2.0. The only package on nuget is http://nuget.org/packages/Microsoft.Exchange.WebServices/ which is 1.2.
What is the proper way to bring the latest managed api to nuget? Do we have to request a package from Microsoft? Is it legal to create a package and push it to nuget?
Since there are many Microsoft libs on nuget that have been packaged by 3rd parties, I decided to go ahead and put it up there: https://www.nuget.org/packages/EWS-Api-2.0/
We are currently using web deploy for creating packages for our .net web applications. It got some pros and cons. Now we are going to use nuget for dependency management but given the ease of packaging in nuget .. i am debating on should i still use web deploy + remote service or try to use nuget to bundle my web application and use powershell or something like octupus to deploy ??
For my web deploy becomes little complex when even try to do simple things like include , exlcude , gac or registry or iis config ( which again not very flexible ).
But on the other hand it comes with remote service and all i need to do is through the package to the service and i am done..
Please give your inputs on this comparison.
-raj
NuGet is a dependency manager, and as such is appropriate for use at development/build, not deployment time. From a deployment perspective, it doesn't offer you any more than what a zip file does... except all the overhead of trying to fit NuGet in the process.
Take a look at Inedo's BuildMaster. It can take care of the process from source control through production deployment. There's also a free version that will most certainly handle your requirements, and it also has a module to manage your configuration files so you don't need to worry about doing transforms.
(disclaimer: I work for Inedo)
I am setting up a system that uses NuGet and Webdeploy.
NuGet is used as the repository format, so the build system publishes NuGet packaged artifacts.
The Deployment systemn uses NuGet to get the RIGHT packaged artifact from the NuGet repository.
The build artififact happens to be WebDeploy for easy installation.
I am still working out if I am going to use puppet, chef or octupus to orchastrate the deployment.