Skip to content

Conversation

Copy link

Copilot AI commented Jun 2, 2025

Updated Task 1 (part 3) in 02-ImageProcessingAndStorageEvents.md to replace outdated hardcoded package versions with comprehensive NuGet Package Manager instructions.

Problem

The walkthrough documentation contained a hardcoded XML snippet with specific package versions that could become outdated over time:

<ItemGroup>
    <PackageReference Include="Azure.Messaging.ServiceBus" Version="7.15.0" />
    <PackageReference Include="CsvHelper" Version="30.0.1" />
    <!-- ... more packages with hardcoded versions ... -->
</ItemGroup>

This approach led to potential issues:

  • Packages may have received version updates or name changes
  • Copy-pasting outdated dependencies could cause errors
  • Problems during GitHub Actions pipeline setup in Task 4

Solution

Replaced the hardcoded XML with step-by-step NuGet Package Manager instructions for all 10 required packages:

  • Azure.Messaging.ServiceBus
  • CsvHelper
  • Microsoft.Azure.CognitiveServices.Vision.ComputerVision
  • Microsoft.Azure.Cosmos
  • Microsoft.Azure.Functions.Extensions
  • Microsoft.Azure.WebJobs.Extensions.EventGrid (with specific search guidance)
  • Microsoft.Azure.WebJobs.Extensions.Storage
  • Microsoft.Extensions.DependencyInjection
  • Microsoft.NET.Sdk.Functions
  • Polly

Each package now includes clear instructions:

  1. Open NuGet Package Manager
  2. Search for the package name
  3. Install the latest stable version

Benefits

  • Always uses latest package versions
  • Prevents version compatibility issues
  • Reduces errors during GitHub Actions pipeline setup
  • Follows recommended Azure development practices
  • Maintains workshop compatibility with .NET 6 LTS

Fixes #13.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Walkthrough 2 Issue Replace hardcoded NuGet package versions with NuGet Package Manager guidance in Walkthrough 2 Jun 2, 2025
Copilot AI requested a review from blgorman June 2, 2025 14:42
<PackageReference Include="Polly" Version="7.2.4" />
</ItemGroup>
```
>**Note:** To ensure you have the latest and correct packages for your Azure Functions project (.NET 6 LTS), it is recommended to use the NuGet Package Manager to install the required dependencies rather than hardcoding specific versions. This approach prevents errors that may occur over time as versions and dependencies evolve, and will help prevent issues during Task 4 when setting up a pipeline in GitHub Actions.
Copy link
Member

Choose a reason for hiding this comment

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

@copilot can we update this to .NET 8 instead of .NET 6?

Copy link
Author

Choose a reason for hiding this comment

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

Updated all .NET 6 references to .NET 8 in the ImageProcessing walkthrough, including the NuGet package guidance, SDK download link, and Azure Function App deployment instructions. Commit 81432cc

Copy link
Member

@blgorman blgorman left a comment

Choose a reason for hiding this comment

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

@copilot Can you take a look and see if we can update these instructions to reflect .NET 8 and isolated workers in the function app (might need to change the packages to map to the isolated versions?)

- Install the latest stable version

Feel free to perform any reasonable upgrades to minor versions should any exist in your NuGet Package Manager.
>**Important:** This approach is NOT for the isolated version of Azure Functions. Isolated functions are not yet tested for this workshop.
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

Can we remove this and utilize .NET 8 with isolated workers for the function app?

Copy link
Author

Choose a reason for hiding this comment

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

Removed the note about isolated functions not being tested and updated the entire walkthrough to use .NET 8 isolated worker functions with proper packages and configuration. Commit 23bb75a

… proper packages and code examples

Co-authored-by: blgorman <[email protected]>
Copy link
Author

Copilot AI commented Jun 2, 2025

@copilot Can you take a look and see if we can update these instructions to reflect .NET 8 and isolated workers in the function app (might need to change the packages to map to the isolated versions?)

Updated the instructions to use .NET 8 isolated worker Azure Functions with proper package references and code examples. Replaced all WebJobs packages with their isolated worker equivalents and added Program.cs setup guidance. Commit 23bb75a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Walkthrough 2 Issue

2 participants