Home → Questions →

VS2026 Environment does not generate VB based artifacts

• Edit

rgelb

06 Feb, 2026 01:08 AM

I have a solution that's .NET 10 and it has a mix of C# and VB projects. I set the Environment to Visual Studio 2026. I set the Automatic Packaging to "Package ASP.NET Core Projects". And I am guessing that this means that projects with <Project Sdk="Microsoft.NET.Sdk.Web"> get built into artifacts.

So the build goes well, but it only generates C# based artifacts. There are 6 web based projects, but it only builds 3 of them into artifacts.

Here is an example of what it was building before the switch to the new environment (using Visual Studio 2022 environment):

MSBuild version 17.14.23+b0019275e for .NET Framework
Uploading artifacts...
[1/6] NeutralPortal.zip (112,113,631 bytes)...100%
[2/6] ADRISBlueSky.zip (120,980,896 bytes)...100%
[3/6] WebSubmit.zip (52,179,828 bytes)...100%
[4/6] MyJW.zip (71,598,537 bytes)...100%
[5/6] AMIListener.zip (58,551,711 bytes)...100%
[6/6] VAST.zip (50,068,221 bytes)...100%
Build success

And here is what it builds with VS2026 environment.

MSBuild version 18.0.5+e22287bf1 for .NET Framework
dotnet publish "C:\projects\adris-web\main\MyJW\MyJW.csproj" --output C:\Users\appveyor\AppData\Local\Temp\1\0mkgsm0stv --verbosity quiet
dotnet publish "C:\projects\adris-web\main\VAST\VAST.csproj" --output C:\Users\appveyor\AppData\Local\Temp\1\8o9fer7he3 --verbosity quiet
dotnet publish "C:\projects\adris-web\main\AMIListener\AMIListener.csproj" --output C:\Users\appveyor\AppData\Local\Temp\1\6r91xxy2ks --verbosity quiet
Uploading artifacts...
[1/3] MyJW.zip (72,026,625 bytes)...100%
[2/3] VAST.zip (70,559,148 bytes)...100%
[3/3] AMIListener.zip (70,944,916 bytes)...100%
Build success

NeutralPortal, ADRISBlueSky, WebSubmit are all VB based projects.
Please have a look.

1. Support Staff 1 Posted by Owen McDonnell on 06 Feb, 2026 08:15 AM

   

   As the build agent has not yet been updated to work with Visual Studio 2026 you could switch to a manual script to publish those packages.
   If you're using the web UI for config you could add it to Before packaging script in Build section of settings, for example.

   • Edit

2. 2 Posted by rgelb on 06 Feb, 2026 04:02 PM

   

   So I did as you suggested.

   1. Added three artifacts
      
   2. Added three dotnet publish foo.vbproj... commands to the before packaging script.
      

   My observation is that it's a lot slower than when your system does it automatically. Is this correct?

   • Edit

3. 3 Posted by rgelb on 06 Feb, 2026 04:08 PM

   

   And what is the ETA for VS2026 to be fully working?

   • Edit

4. Support Staff 4 Posted by Owen McDonnell on 09 Feb, 2026 06:48 PM

   

   We're currently looking into the discrepancy between images. Can you provide the configurations for each of the above outputs?
   You can go to Export YAML section is using web UI for config.

   • Edit

5. 5 Posted by rgelb on 10 Feb, 2026 05:31 AM

   

   YAML attached.

   • appveyor(1).yml 3.42 KB
   • Edit

6. 6 Posted by rgelb on 12 Feb, 2026 02:42 AM

   

   So what's the word?

   • Edit