Skip to content

Conversation

haruna99
Copy link

No description provided.

@Copilot Copilot AI review requested due to automatic review settings March 24, 2025 22:33
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR establishes continuous integration for an ASP.NET project by adding an Azure Pipelines YAML configuration.

  • Introduces a new pipeline file for building, restoring NuGet packages, and running tests
  • Defines pipeline variables, tasks, and build arguments for an ASP.NET application
Comments suppressed due to low confidence (2)

azure-pipelines.yml:13

  • The use of the wildcard '**/*.sln' may inadvertently select more than one solution file if multiple are present. Consider specifying a single solution explicitly if only one is intended.
solution: '**/*.sln'

azure-pipelines.yml:27

  • System variables in Azure Pipelines are typically case-sensitive; verify that '$(build.artifactStagingDirectory)' is correctly cased. It might need to be updated to '$(Build.ArtifactStagingDirectory)' to ensure proper resolution.
msbuildArgs: '/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactStagingDirectory)\WebApp.zip" /p:DeployIisAppPath="Default Web Site"'

Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

@ViktorHofer
Copy link
Member

I'm not sure what the intent of this PR is but we already have azure devops pipelines in this repository. Closing.

@jkotas jkotas deleted the azure-pipelines branch April 12, 2025 13:56
@github-actions github-actions bot locked and limited conversation to collaborators May 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants