Azure Stream Analytics CI/CD部署及NuGet包同步问题咨询

Hey there! Let's work through your two questions step by step to get you unblocked with Azure Stream Analytics and CI/CD in Visual Studio 2017.

1. How to fix missing Microsoft.Azure.StreamAnalytics.CICD NuGet package after pushing to DevOps? #

First, let's clarify: Git (and DevOps Repos by default) doesn't track the physical NuGet package files in the packages folder—this is intentional to keep your repo clean. The key is ensuring your project references the package correctly so DevOps can restore it automatically during builds. Here's what to do:

• Verify package references in your project file: Open your Stream Analytics project file (.asaproj) and check that there's a reference to Microsoft.Azure.StreamAnalytics.CICD. If you installed the package via NuGet Package Manager, this should be added automatically. If not, you can manually add it (or re-run the install command in Package Manager Console):

  Install-Package Microsoft.Azure.StreamAnalytics.CICD
  

  If you hit errors during installation, check if your VS 2017 has access to the official NuGet feed, and try specifying a version compatible with VS 2017 (e.g., older versions like 1.0.0—check the package's version history for compatible releases).

• Commit your project file to DevOps: In Visual Studio's "Changes" tab, make sure you're committing the .asaproj file (not just the code files). The package reference lives here, so without committing this file, DevOps has no way to know it needs to restore the package.

• Don't modify the .gitignore file: By default, .gitignore excludes the packages folder, which is the right approach. DevOps will automatically download the package from NuGet during the build process as long as the project reference is present.

2. If using Visual Studio for CI/CD, do I need to sync VS project changes after modifying the stream job in Azure Portal? #

Yes—here's why: Your CI/CD pipeline is set up to deploy configurations from your VS project (stored in DevOps) to Azure. If you make changes directly in the Azure Portal, those changes won't sync back to your VS project automatically. Worse, the next time you run your CI/CD deployment, the portal's changes will be overwritten by the configuration in your VS project.

To keep everything consistent:

• Make all configuration changes in VS first: Edit your Stream Analytics project locally, test it, commit the changes to DevOps, then let the CI/CD pipeline deploy to Azure. This ensures your source of truth is always your code repo.
• If you already made portal changes: Use the "Import from Azure" feature in the Visual Studio Stream Analytics tools to pull the portal's configuration into your local project. Then commit those changes to DevOps so future deployments use the updated settings.

内容的提问来源于stack exchange，提问作者user185981