Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The program '[17020] Phoesion.Glow.Reactor.Debugger.exe' has exited with code 4294967295 (0xffffffff). #3

Closed
ad-yodiwo opened this issue May 13, 2022 · 2 comments

Comments

@ad-yodiwo
Copy link

I tried the "Hello World" service - https://glow-docs.phoesion.com/tutorials/Create_Hello_World.html. When pressing F5 at Visual Studio I get:

The program '[17020] Phoesion.Glow.Reactor.Debugger.exe' has exited with code 4294967295 (0xffffffff).

I am expecting to see a window of the service running.

I am using latest release - 0.0.299.

@gepa21
Copy link
Contributor

gepa21 commented May 13, 2022

Hello,

I was able to reproduce and identified the issue in a problematic escaping of path between Visual Studio and Windows.

the command line that is trying to launch the application is something like :
Phoesion.Glow.Reactor.Debugger.exe -QuantumSpace:Default "bin\Debug\net6.0\win-x64\Foompany.Services.HelloWorld.dll"

that (for some reason) the \n string in the path for Debug*\n*et6.0 gets escaped (it shouldn't) and ends up as a new line in the arguments! (The debugger then fails to find the file and cannot load it)

I will release a new version in couple of days that will take this into account and de-escape new lines into the "\n" string, which should fix the problem.

In the meantime, a workaround for your project is to add the
<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
property in your .csproj file, so the output does not contain a directory start with the letter n (in this case net6.0)

so your project file should be something like :

<PropertyGroup Condition="'$(Configuration)'=='Debug'">
   <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath>
</PropertyGroup>

Thank you for reporting this issue!

@gepa21 gepa21 closed this as completed May 13, 2022
@gepa21
Copy link
Contributor

gepa21 commented Jun 28, 2022

fixed in version v0.0.300

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants