I am unable to build any of my Asp.net projects

Elements Oxygene
,
1

Microsoft Visual Studio Community 2022
Version 17.14.13 (August 2025)
VisualStudio.17.Release/17.14.13+36414.22.-august.2025-
Microsoft .NET Framework
Version 4.8.09037

RemObjects Elements 12.0.0.3013

I am unable to build any of my Asp.net projects. It gives two incomprehensible errors (for my):

Error (MSB4217) Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt. WebApplicationTest C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\RemObjects Software\Elements\RemObjects.Elements.Echoes.Legacy.targets 465
Error (MSB4028) The “OxygeneCompilerOutOfProcess” task’s outputs could not be retrieved from the “PositionsFileName” parameter. Object does not match target type. WebApplicationTest C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\RemObjects Software\Elements\RemObjects.Elements.Echoes.Legacy.targets 536

I have tried a completely new app using ASP.NET Classic Web Application (.Net Framework 4.8) template. Without touching anything it builds, but if I add a simple field in the Global_asax class I get the errors. No matter how many tests I have done, I can’t get it to work.

Attached is the test project and build output.

Build output.zip (28.1 KB)

WebApplicationTest.zip (34.4 KB)

2

Curious. i think we had a similar report a few weeks back, i need to check what the status or resolution there was.

In the mean time, your project builds fine for me using plain EBuild without the MSBuild wrapper that Visual Studio unfortunaterly needs. So as a temporary workaround, could you use Water (or EBuild on the commandline) to build your project, rather than VS?

3

The truth is that I don’t have much time. The thing is, I use Visual Studio because I have several of my own extensions and some from others that are essential in my day-to-day work.

4

I understand. I was merely suggesting thisas a workaround until we can solve this issue, which probably will not happen today.

Oddly, when i open your solution in VS, i get

The project file ‘\Mac\Home\Downloads\WebApplicationTest\WebApplicationTest.elements’ cannot be opened.

There is a missing project subtype.
Subtype: ‘{349c5851-65df-11da-9384-00065b846f21}’ is unsupported by this installation.

I haven’t investigated further (or tried removing the subtype) yet; this might be an issue with my VS setup, as in don’t use VS regularly myself. Unfortunately the team member most likely to know whats going on here is on vacation this week and part of next.

Do you see this issue too? or is this maybe related tom one of the (non-RemObjects) extensioms you use in VS that you mentioned?

Update: i also seem to be missing “$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v17.0\WebApplications\Microsoft.WebApplication.targets”, which your project uses. I could imagine that this target is causing some conflict with ours that causes your error. Investigating what components i’m missing to get this, now…

5

https://github.com/VISTALL/visual-studio-project-type-guids

{349C5851-65DF-11DA-9384-00065B846F21} is for ASP.NET MVC 5.I think it’s from your “classic ASP.NET web application” template. It’s in all my Web Forms projects.

6

It’s also in all my Web Forms projects.

7

I’ve found it Build Errors MSB4217 and MSB4028 with empty classic webserver project, but there does not seem to be any solution.

It hasn’t even been Logged as bug.

8

After installing ASP.NET development support (a whopping extra 800mb, wow), your project opens and builds fie for me… Latest VS2022, 17.4

9

Use Rebuild, please.

In more complex projects, it is impossible to achieve anything using “build” or “rebuild,” but in simple projects, sometimes “build” works.

10

Logged as bugs://E27359.

11

My colleague reproduced the issue. We’ll investigate thanx!

12

You’re welcome.

1 Like
13

I think what is happening is that it doesn’t compile any code that has a real syntax error because the two MS Build errors replace the code error report. My rather large project when it didn’t have an error in it compiled, threw the errors, and then when I ran it, it ran just fine because it was already compiled. When I futzed with it enough that I introduced an error, now it doesn’t compile and also does not give me the error. I will try EBuild.

14

Note that EBuild is giving me an unsupported language error on this line:
<%@ Page Language=“Oxygene” AutoEventWireup=“true” CodeBehind=“Default.aspx.pas” Inherits=“etc._Default” EnableEventValidation=“false” %>

15

Interesting. I don’t think EBuild will work to compile .aspx files themelves, yo’ll bneed to use thew MSBuild toolchain for that. Unless i ever get arund to fully finishing this thing: ESP: Keeping Classic ASP.NET Alive. Which mighyt actuallty be what you’re hitting. Can i see the/a project that gives you the unsupported language error?

16

I can give you a onedrive link privately. How are we coming on the bug? The biggest issue with it is that it suppresses the reporting of syntax errors which makes anything more than a few lines impossible.

17

Please!

I’ll follow up with my colleague who was investigating this. My apolofies for the delay.

18

Mark:

Will we have a version with this problem solved today? I’m eagerly awaiting it.

19

We’re going as fast as we can. My apologies that this hasn;t been possinle to solve more quickly.

20

bugs://E27359 was closed as fixed.