Skip to content

[Bug]: New FSLogix version doesn't provide enough detail to determine version number #13

@aaronparker

Description

@aaronparker

What happened?

The new FSLogix agent v3 URL does not provide enough detail to capture the full version string, e.g. 3.25.202.4223. See announcement post here: https://techcommunity.microsoft.com/blog/fslogix-blog/fslogix-v3-release-25-02-is-now-generally-available/4377003

Version

2412.1770

What PowerShell edition/s are you running Evergreen on?

PowerShell Core

Which operating system/s are you running Evergreen on?

macOS

Have you reviewed the documentation?

Verbose output

VERBOSE: Function path: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-MicrosoftFSLogixApps.ps1
VERBOSE: Function exists: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-MicrosoftFSLogixApps.ps1.
VERBOSE: Dot sourcing: /Users/aaron/projects/evergreen/Evergreen/Apps/Get-MicrosoftFSLogixApps.ps1.
VERBOSE: Get-FunctionResource: read application resource strings from [/Users/aaron/projects/evergreen/Evergreen/Manifests/MicrosoftFSLogixApps.json]
VERBOSE: Calling: Get-MicrosoftFSLogixApps.
VERBOSE: Resolve-SystemNetWebRequest: Attempting to resolve: https://aka.ms/fslogix/download.
VERBOSE: Resolve-SystemNetWebRequest: Resolved to: [https://download.microsoft.com/download/0d30db30-2d48-4640-a56c-3a1502fcb29a/FSLogix_25.02.zip].
VERBOSE: ConvertTo-DateTime: Converting: [02/12/2025 03:12:13].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-AU.
VERBOSE: ConvertTo-DateTime: Returning date: [12/2/2025].

Metadata

Metadata

Assignees

No one assigned

    Labels

    informationAlready fixed or not something requiring an update, or something that explains a known behaviour

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions