Hello,
i’ve just tried to check the Latest build of Elements 12…2975 and the installer stucks repeatedly at the “Registering RemObjects Elements CodeDom” phase.
CPU does nothing, the installer windows is not responding. Looks like there is some kind of modal promp hanging and waiting for input but not visible.
Tried to
restart everything
run in elevated mode
uncheck option "Register CodeDom with .NET and Mono
do it on another computer
Non of this helped.
Do you have any advice how to solve this ?
Thanks in advance
Ive found, the installer attempts to do something with Visual Studio, starts the devenv.exe with /SETUP argument and hangs there (maybe there is a hidden dialog within the VS process ?). If I kill the devenv.exe, the installer continues. This happens as many times as many VS editions ive installed.
In my case, 4 times killing devenv helped to finish the installer and it looks like event VS extensions are OK. Dont know what is happening there.
I am afraid that this confirmed as a bug in Visual Studio 17.13.1., unrelated to Elements. Visual Studio hangs with devenv /setup even in clean environment without our products installed. As I understand Microsoft has already fixed this for the next version.
As workaround, simply kill devenv.exe with Task Manager.
thanks,
are you avare of any other problems with VS 17.13.x ? The original reason, why im testing new elements build is that with the VS 17.13.x sometimes the Elements build inside MSBUILD doesnt produce all assemblies at the bin outdir.
Can you describe the issue in more detail? what kind of dlls ar missing? The actual output of you project, or secondary/Copy-Local dlls? What happens if you build in Water, or with ebuild on the command line?
Looks like that VS 17.13.2 and greater are OK with both cases - Elements installation and build.
But this week we discovered a problem with the preview channel 17.14.0. Preview 2
Elements projects fails with error below, do you have any details about this ?
Thanks
Error (MSB4217) Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt. TescoSW.DigitalSignature.FPC.Pades C:\Program Files\Microsoft Visual Studio\2022\Enterprise\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. TescoSW.DigitalSignature.FPC.Pades C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\RemObjects Software\Elements\RemObjects.Elements.Echoes.Legacy.targets 536
V MSBuild_*.failure.txt. je:
UNHANDLED EXCEPTIONS FROM PROCESS 16032:
=====================
13.03.2025 8:23:54
Microsoft.Build.Framework.InternalErrorException: MSB0001: Internal MSBuild Error: _eventType should not be a custom event
v Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(String message, Exception innerException, Object[] args)
v Microsoft.Build.Shared.LogMessagePacketBase.WriteToStream(ITranslator translator)
v Microsoft.Build.BackEnd.NodeEndpointOutOfProcBase.RunReadLoop(BufferedReadStream localReadPipe, NamedPipeServerStream localWritePipe, ConcurrentQueue`1 localPacketQueue, AutoResetEvent localPacketAvailable, AutoResetEvent localTerminatePacketPu
