Relying on cargo metadata rather than individual Manifest files

[jelmansouri]

First thanks a lot for putting up a Visual Studio extension that works with RustAnalyser ! I was wondering if there is any reason why you are not relying on cargo metadata output to list the targets, find the target directory and such.
I can do a change in that regard if you are willing to review and in case there is rationale for that.

[cchharris]

Thanks for the interest! I did investigate cargo metadata - if I recall correctly, it didn't give all the information I needed to fully setup certain VS Integrations, like Build or Build+Run.

I'll give this a second look when I get a chance, as not having to parse the TOML ourselves and getting cargo's own interpretation would be very nice, and prevent us from deviating.

[cchharris]

Apologies for the delay on getting to this - I recently switched jobs and have been onboarding and otherwise occupied.

I recently saw Rust update Cargo to support showing test binaries location via cmd line - here.

I'll look into shifting grabbing as much information as possible from the existing cargo commands now, rather than rolling our own Toml. I'll probably be able to start working on that come next week.

(Edit) Apparently that was even earlier this year before this issue was even made. Regardless, I just now became aware of it, so I'll see if I can't incorporate it 😄

[cchharris]

Just investigated this. I'm refreshing my memory of what information is necessary for the Visual Studio plugin, but it seems like this is a viable alternative to parsing the Toml ourselves. Will see if I can't get a proof of concept going.