Activity

1. AndrewPearson

   changed the title [-]Version number not availabale for packages added using GlobalPackageReference in Directory.Packages.props[/-] [+]Version number not available for packages added using GlobalPackageReference in Directory.Packages.props[/+] on Feb 2, 2023
2. phmonte

   added

   ⚠ BugSomething isn't working as expectedSomething isn't working as expected

   on Feb 18, 2024
3. phmonte commented on Apr 7, 2024

   

   phmonte

   on Apr 7, 2024

   Collaborator

   More actions

   @AndrewPearson, I tried to reproduce the problem and it worked, do you have an example of the project?
4. phmonte

   added

   Feedback NeededFurther information is requestedFurther information is requested

   on Apr 7, 2024
5. AndrewPearson commented on Apr 8, 2024

   

   AndrewPearson

   on Apr 8, 2024

   Last edited by AndrewPearson

   Author

   More actions

   Hi @phmonte,
   Thanks for looking into this (great project btw).

   I found this issue while using a dotnet tool called snitch, which makes use of buildalyzer. I did also report the issue on that project (spectresystems/snitch#39)

   To replicate the problem:

   • create a new dotnet solution with a template 'hello world' console project. I'm using .Net 8.
   • add a Directory.Packages.props file containing the following:

   <Project>
     <PropertyGroup>
       <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
       <EnablePackageVersionOverride>false</EnablePackageVersionOverride>
     </PropertyGroup>
     <ItemGroup>
       <GlobalPackageReference Include="StyleCop.Analyzers" Version="1.2.0-beta.556" />
     </ItemGroup>
   </Project>
   

   With this solution, try the following code which uses Buildalyzer:

               var mgr = new AnalyzerManager();
               var projAnalyzer = mgr.GetProject(@"{YourPath}\{YourConsoleProject}.csproj");
               var results = projAnalyzer.Build();
   
               var packages =results.Single().PackageReferences;
               var styleCop = packages["StyleCop.Analyzers"];
               var version = styleCop["Version"];
   
               Console.WriteLine($"stylecop version = '{version}'", version);
   
   

   When I run this locally, the version is blank.

   I hope this explanation is clear enough to explain the problem I see. Please do ask any questions you might have, and thanks again for taking a look.
6. phmonte commented on Apr 9, 2024

   

   phmonte

   on Apr 9, 2024

   Collaborator

   More actions

   Thank you very much, I believe it is now possible to simulate, I will update soon.
7. Corniel commented on Apr 11, 2024

   

   Corniel

   on Apr 11, 2024

   Collaborator

   More actions

   I added a reproducer. I'm not sure why you use <GlobalPackageReference> in this case (or at all, I could not find any documentation on it, if you can provide that, that would be appreciated), but the version is not provided by the BuildStatusEventArgs, I'm not sure why,

   If you use <PackageReference> instead, the version is available.
8. AndrewPearson commented on Apr 11, 2024

   

   AndrewPearson

   on Apr 11, 2024

   Last edited by AndrewPearson

   Author

   More actions

   A description of the use of <GlobalPackageReference> is available here

   👍React with 👍1Reacted by Corniel Nobel
9. Corniel commented on Apr 19, 2024

   

   Corniel

   on Apr 19, 2024

   Collaborator

   More actions

   @AndrewPearson See my reporducer. I'm affraid that this is bug/feature that is not due to a bug in Buildalyzer. If I may ask, why do you want to know this version?

   May be, a (to be created) rule of .NET project file analyers I might solve what you want to achieve?
10. AndrewPearson commented on Apr 20, 2024

    

    AndrewPearson

    on Apr 20, 2024

    Author

    More actions

    I use a tool called snitch, which makes use of buildalyzer. Snitch fails to run on a project I have, producing errors. I debugged into snitch's code, and found this issue with the version number being blank.