-
The build runs successfully, but deployment does not.
The reason seems to be a Demand on DotNetFramework that cannot be removed. I assume it's because we use PowerShell to run a deployment script.
!…
-
## **Agent version and platform**
Agent version vsts-agent-win7-x64-2.105.7
OS of the machine running the agent: Windows Server 2016 DataCenter
## **VSTS type and version**
On-Prem TFS TFS2…
-
Windows XP, Build 24.
Treied to create a service. I.e. executed:
asadmin create-instance --node localhost aa
asadmin create-service --node localhost aa.
Was seen such output:
=========================…
-
### Description
I have reference to package that has a reference to ms code analysis, paket is failing to resolve underlying dependencies for the package and it failing to add Analyzers section to cs…
-
Hi
I am unable to link the VSTS Agent to my account. I have access to the website so I dont think this is a Network issue
## **Agent version and platform**
Version of your agent? 2.107.0
Windows 20…
-
Have tried both on Azure Notebooks and running the latest docker image locally.
## Steps to reproduce
In a new cell:
`#N "Newtonsoft.Json"`
## Results
`NuGet error: Unable to find package…
-
.NET Core 版本应该为.NET Framework 版本
-
In dotnet cli AssemblyInfo is generated during each build from properties present in the project.json file. MSBuild currently relies on a template generated or user created AssemblyInfo to be present.…
-
Each of the tasks need to demand powershell. This is imporntant for agent pools that have a mix between MS build agents and cross platform build agents.
Example here:
https://github.com/Microsoft/vst…
-
I have copied the dotnet exe package to my local shared folder and gave the URL path but the package is copied to the node under chache folder and it shows file sizes exceed 10000000 bytes, diff outpu…