Home → Problems →

VS2026 Environment stil does not automatically compile VB projects or generate artifacts.

• Edit

rgelb

13 Apr, 2026 09:05 PM

A while ago I submitted this issue. https://help.appveyor.com/discussions/questions/383260-vs2026-envir...

For whatever reason, I thought this was fixed. However, in a mixed solution of VB and C# projects, the VB projects are not automatically compiled, and consequently, no artifact is generated.

This used to work with a VS2022 image.

1. Support Staff 1 Posted by Owen McDonnell on 14 Apr, 2026 09:30 PM

   

   Are all the projects you are building SDK style? Can you share configuration and a build log of the same commit built on vs2022 and vs2026 image?

   • Edit

2. 2 Posted by rgelb on 15 Apr, 2026 04:50 PM

   

   All projects are .NET 10.

   When I say it all used to work... it was .NET 4.8 and NOT SDK style. And we used the VS2022 image.

   We then converted the the code to .NET 10 (and obviously it's SDK style now). And as a result of that, we had to switch to the VS2026 style.

   The new config is vanilla. There is nothing custom about the appveyor.yaml. It's just me clicking various checkboxes and added extra commands to pre and post build commands (and adding manual artifacts), to compensate for this bug.

   Attached is the current log (log-vs2026.txt) and the old log (vs-2022.txt) and appveyor.yaml.

   • appveyor.yml 1.47 KB
   • log-VS2022.txt 128 KB
   • log-VS2026.txt 271 KB
   • Edit

3. Support Staff 3 Posted by Owen McDonnell on 17 Apr, 2026 12:39 AM

   

   Thanks for that, we're working on a build agent update to address the different behaviours between images.

   • Edit

4. 4 Posted by rgelb on 18 Apr, 2026 06:25 PM

   

   @Owen, please post here if and when this issue is fixed.

   • Edit

5. Support Staff 5 Posted by Owen McDonnell on 20 Apr, 2026 04:40 PM

   

   We've deployed a new build agent to address the issue.
   Here is the test we ran to verify that VB based dotnet core web apps are detected along with C# based ones.

   • Edit

6. 6 Posted by rgelb on 20 Apr, 2026 08:52 PM

   

   @Owen,

   The VB projects are now building. But there is still a bug. I have a VB library (ACommon.vbproj). It shouldn't be built as an artifact, since it's a library. But it is being built and artifact generated.

   Here are partial contents of vbproj:

   <Project Sdk="Microsoft.NET.Sdk">
   
     <PropertyGroup>
       <TargetFramework>net10.0-windows</TargetFramework>
   
       <!-- Warning Configuration -->
       <NoWarn>WFO1000,CA1416,41999,42016,42017,42018,42019,42032,42036</NoWarn>
       <WarningsAsErrors>42020,42021,42022</WarningsAsErrors>
     </PropertyGroup>
   

   • Edit

7. Support Staff 7 Posted by Owen McDonnell on 21 Apr, 2026 05:35 AM

   

   We've rolled back the build agent as we investigate a possibly related issue. Although, before doing so I added a VB class library to the test project and was not able to reproduce your error, i.e. it did not get automatically packaged.
   Build here

   • Edit

8. Support Staff 8 Posted by Owen McDonnell on 22 Apr, 2026 09:26 PM

   

   Please let us know how your project differs from the example i linked so that we might adjust the build agent accordingly going forward.

   • Edit

9. 9 Posted by rgelb on 22 Apr, 2026 10:49 PM

   

   @owen. I am not sure. The only thing that I see is that my projects have a of net10.0-windows. And yours have the generic net10.0.

   But otherwise they are the same. Here is my project (called ACommon) that was mistakenly building when you had the new copy of the image deployed:

   <Project Sdk="Microsoft.NET.Sdk">
   
     <PropertyGroup>
       <TargetFramework>net10.0-windows</TargetFramework>
   
       <!-- Warning Configuration -->
       <NoWarn>WFO1000,CA1416,41999,42016,42017,42018,42019,42032,42036</NoWarn>
       <WarningsAsErrors>42020,42021,42022</WarningsAsErrors>
     </PropertyGroup>
    ....
   

   And here was the the output from the build. Mistaken build is ACommon.zip (3/9)

   Uploading artifacts...
   [1/9] NeutralPortal.zip (117,673,259 bytes)...100%
   [2/9] ADRISBlueSky.zip (123,182,101 bytes)...100%
   [3/9] ACommon.zip (71,382,808 bytes)...100%
   [4/9] WebSubmit.zip (68,151,055 bytes)...100%
   [5/9] MyJW.zip (75,405,291 bytes)...100%
   [6/9] VAST.zip (69,232,423 bytes)...100%
   [7/9] AMIListener.zip (68,478,875 bytes)...100%
   [8/9] ABLE.Core.zip (69,508,974 bytes)...100%
   [9/9] CAIN.zip (68,918,086 bytes)...100%
   Build success
   

   • Edit

10. Support Staff 10 Posted by Owen McDonnell on 23 Apr, 2026 08:55 PM

    

    It looks like our logic was counting projects with any package referencing the Microsoft.AspNetCore namespace as ASP.net core apps. We're currently working on a new build agent deployment to correct that.
    I'll update here when it's been deployed.

    • Edit

11. Support Staff 11 Posted by Owen McDonnell on 24 Apr, 2026 05:38 PM

    

    The new agent has been deployed. It seems to work on the test project modified to be as close to yours as I can guess.

    • Edit

12. 12 Posted by rgelb on 25 Apr, 2026 01:09 AM

    

    @Owen. It appears to work. Thank you. I'll let you know if anything crops up.

    • Edit