Quality of life issues while using Ambient

[Pombal]

Hi,

I've been trying to use https://github.com/AmbientRun/Ambient on latest VS22 and I've noticed a few issues:

When I select 'Start Debugging' for ambient.exe (app/Cargo.toml as startup item) then the code is rebuilt from scratch instead of using the existing binary.

When I select 'Start Debugging' for client_fog.exe (guest/rust/examples/basics/fog/Cargo.toml as startup item) then I get an error with the Manifest parsing logic where it's unable to find the .exe. I've deleted the .vs folder as the error message says but it continues.

It's possible these are due to user error but it would be great if you could have a look at making rust-analyzer.vs work well with Ambient.

Thanks!

[parthopdas]

looking into it.

[parthopdas]

apologies for the delay.

for issue 1: a build does happen but it is an incremental build. unfortunately without significant architectural changes this is unavoidable (e.g. the extension could bypass the build if the bins were update - which it does for running unit tests but extension api does not support it for debug case)

for issue 2: it appears the example is being built but the binary is not generated. same is the result from command line - see pic below. please can you see what the issue is. i'd wager if the commandline build works, IDE will as well, if not i'll take a look.

[Pombal]

Thanks for looking into it.

I believe that for issue 2 what is being generated by default is a wasm file instead of a binary.
I will look into seeing if there's something that be changed within Ambient.