Hi! I hope this is the right spot to ask these sorts of questions!
I've been playing with the latest release and was wondering if I'm misunderstanding the function of the "Show in VS Code" button under Assets: When I use that button on e.g. MainPage.xaml, it opens a temporary file with some sort of a side-by-side diff view, from a path like C:\Users\username\AppData\Roaming\NoesisStudio\Backups\A8DAE144\E2EBDD21.xaml: My expectation was to see the \MainPage.xaml from the project path, like so: I wonder if this is a bug or whether that diff view is the intended function.

Hey Artyom,

This 'side-by-side' occurs when you have an unsaved file open in Studio whilst not having yet saved over, or discarded the 'Backup' (auto-save) copy we automatically surface on re-launch of the application. The reason you're seeing a diff, is that it's comparing this 'Backup' file to the modified, 'unsaved' version you currently have open.

If you 'Save' the file in Studio, and then 'Show in VSCode' for the same file, you'll get the result you're looking for.

Alternately, you can also achieve similar results by closing the open tab of the file in question, confirming you want to discard the current doc in the pop-up, and then selecting 'Show in VSCode'. It is however important to note that this method will revert your file to the state it was in when you last manually saved.

- Dorian

Ah, that makes sense, thank you for clarifying!

If I could share an idea, I wonder if it would be possible to try shifting this functionality into its own unique button. Here's a very basic mockup:
I definitely see the merit in displaying the diff for unsaved changes it but I also think it could be more intuitive if this was available through a new button. Something along the lines of the image above (* next to the filename and adding a "show changes" button) could nicely communicate saved/unsaved status of different files and make it clear you're about to open a different place. Just placing a button with a * icon next to the main VS Code icon could also work (doubled * on the mockup looks a bit too busy).

This is an interesting one! One of the challenges of adding this type of functionality, is that in theory, the 'diff' is an incredibly transient state/edge case. It only occurs if you either crashed, or didn't save your file before closing Studio, and only in the period of time until you either 1) save, or 2) decide you don't want to use the auto-save as your starting point after rebooting.
So, in the vast majority of cases, the 'diff' it is a function that will only exist in the first ~10-15 seconds it takes to make this decision after re-launching the application, and will not be available otherwise.

In any case, will bring this up for discussion once everyone is back from GDC!

Thanks Artyom!