When trying to install tools like python, AZ CLI, updating tool versions, or etc, despite RDP'ing into the server and installing via Powershell, the pipeline still declares them either not installed, or still reflects the old version, even when confirming install/version in shell in RDP. What am I missing?
Related
For some Dependencies reason with Terraform (using azure cli internally). I'm trying to use multiple versions of azure cli in my machine. e.g, 2.30.0 ,2.22.0
Depends on the need we are planning to change the version whenever required. But I couldn't find a way to change the azure cli version.
I can find a way to install older version but that has to be done by uninstalling the newer version and installing the older version. But I don't want to uninstall it, I want to keep the version(s) and use the different version whenever needed.
Is this possible in azure-cli ?
As far as I know and as per the Microsoft Documentation you can't use different versions of Azure CLI in same system at a time.
As you already know you need to uninstall the older and install the newer when needed.
As suggested by CSharpRocks you can use containers to use multiple versions at a time.
You can Raise a Feature request and support ticket for further usage.
I have added a Selenium Project into the Azure pipeline as a maven task. But while running the same pipeline I am getting an error messaged 'Chrome version and chromedriver version is mismatching'.
What should I do to overcome this ?? How to know the chrome version installed inside the windows instance (Each time it takes different windows instance)
How does Microsoft choose the software and versions to put on the image?
More information about the versions of software included on the images
can be found at Guidelines for what's installed.
In your scenario, since you need a specific chrome version. The best and recommend way is using self-host agent.
You can use a self-hosted agent that includes the exact versions of software that you need. For more information, see Self-hosted agents. In this way, you could even clone an environment on VM as same as your local development, this will help to narrow down build issue which caused by environment.
I just upgraded my app to use the latest Microsoft.SqlServer.Types package v14 from v13. This resulted in an well-documented runtime error. The reason here would be missing native libraries:
Spatial types and functions are not available for this provider because the assembly 'Microsoft.SqlServer.Types' version 10 or higher could not be found
The Nuget package also contains the native DLLs that were missing, so I could theoretically copy them to my bin folder and load them through my code, but:
I didn't have to do that with my v13 binaries
When I deployed the updated project to Azure, it ran just fine.
My current assumption would be that I got the v13 binaries with my local SQL install, and on Azure, those binaries (both v13 / v14) are preinstalled.
However, when googling a bit about the issue, most developers have the opposite problem of things not working on Azure due to the missing libs, so I wonder whether not going the manual route might be dangerous with regards to Azure deployments. If anybody had some insight here, that would be awesome!
As far as I know, the azure web service install the SQL server SDK version is 9.0 - 13.0. So you need install 14.0 by yourself.
You could find the dll in the kudu console in your web service.
D:\Program Files (x86)\Microsoft SQL Server\130\SDK\Assemblies>
To open the kudu you could refer to below steps:
1.Find the Advanced Tools in DEVELOPMENT TOOLS click go.
2.Click dubug console's cmd.
3.Find the path.
Notice: You need firstly type cd.. to locate the root path.
You could find the Microsoft.SqlServer file as below:
I am new to Windows powershell and Visual Studio. I followed the azure developer guide on github(https://github.com/Azure/azure-powershell/wiki/Microsoft-Azure-PowerShell-Developer-Guide) till the "Build Solution .Execute tools\Build.ps1" step. Build is failing with 802 errors. How to import the project into visual studio and run the samples? What project is it actually? C# or VB or it just contains cmdlets and sample tests?
There are two parts to the Azure Powershell repository.
Firstly there is the source code, unless you're a developer, or are interested in the inner workings of Azure Powershell, this probably isn't what you are looking for (my apologies if it is!)
As a general overview though, the Build.ps1 configures your machine to build the Azure Powershell cmdlets. The source code is c# and is located here Build.ps1 installs the following -
Install Windows Azure SDK
Install Python 2.7 x86
Install Django
Install Wix 3.8
Make sure that git.exe and wix bin folder are in you PATH environment variable.
Set environment variable EnableNuGetPackageRestore to value true
if you do those things manually, you can then load the project into Visual Studio and compile the cmdlets.
However, the second purpose of that repository is what I suspect you are actually looking for. If you look here you will find the releases of the installers that you can download to install Azure Powershell. Once these are installed on your machine you can browse and configure Azure services via Powershell.
For instance for version 1.0.1 you will find the download for the latest version of Azure Powershell (at the time of writing anyway!)
If you are just looking to learn Powershell and Azure then that is probably the place you want to start.
If you are looking to explore the source code, then that is there also.
We use TeamCity as our CI server (but I imagine this applies to any build server).
We have not installed the azure SDK on the build server and are able to build the projects which use the SDK using the workaround described here.
I now want the server to produce the packages for deployment to Azure, but when I run an MSBuild task to create the packages (as directed here) I get a strange error
error MSB4057: The target "WatGetTargetFrameworkDirectories" does not exist in the project.
which yields few useful google results.
Do I need to install the SDK? Or is this error related to something else?
WatGetTargetFrameworkDirectories is a target from AzureSDKs .targets file. Looks like your error related to Azure SDK.
Except it could be more subtle error related to not very good msbuild Azure Targets. For our own azure packaging we did need to call 2 targets "Clean;CorePublish", not just "Publish". Maybe this will also help you.
Side note: why you don't want to install AzureSDK on TeamCity BuildAgent? Build agents made exactly for that - to have frameworks you need for build. Also 1.6 and 1.7 AzureSDKs can be installed side-by-side.