@Josh I've been trying out VS Code with your extension tonight to see if I could move over from FlashDevelop. On the whole, I like it and I think I could cope!
Like you said, there's a lot more typing and a lot less clicking for configuration. I think it's much better for understanding what's going on behind the scenes, but I'm slightly worried about missing settings that I didn't know were important. The documentation is really great though, so I'll just have to read it all carefully!
It would be nice if there was a way to install and launch apps on a device as a build task/similar. Presumably I could write a script/task of my own to do this and hook it onto one of the extensions tasks? (I'm not that familiar with VS Code so any pointers would be great!)
And, lastly, one potential sticking point is with my current project. It's got this (simplified) structure:
N.B. the .as3proj files are FlashDevelop's version of the asconfig.json file
So the products run off the same source code, it's just the assets in the bin folder (not shown, but db, icons, images, etc.) that are different per product. I switch between the .as3proj files in FlashDevelop (just double-click them) when working on different products.
I thought I could just repliacte the multiple .as3proj files with asconfig.json files, but then I didn't know how to/if I could switch between them when working on different products. So...
- Is there a way to replicate that structure with your extension?
- Or is there a structure that would work better with your extension?
(Sorry for the long post!)