Hey Colin.

I had a few minutes before a meeting so wanted to try recreate on IRIS instead of Cache and happened to have not yet restarted VSCode so didn't have the new extension versions installed.

I was able to run the example you tried in the old extension versions and observed no errors moto x3m in the output for the language server, ran my updates, and then lost the ability to select the Language Server from the Output selection dropdown:

I would have liked to been able to completely recreate this in the new version, or at least give some indication of where the fault may be. But not being able to see the Output window for the language server like in your screenshot stops me in my tracks 😅

Hi Tim

Thanks, we don't currently use IPM.

So essentially if we want to use this we would need to change our current namespace setup and create a development namespace for each developer, plus one basketball stars for the master repository. Then for testing if we wanted multiple testers wanting to test multiple branches at the same time, presumably they'd also need a separate namespaces?

The settings I have in my outgoing namespace are:

and the settings I have in my incoming namespace (where I was trying to pull the project to) are:

I did originally have the settings for the receiving namespace very similar to the outgoing, but when I saw that the exported files had all been put underneath the csp directory I changed them to the above, but they still didn't import. 

The error I am getting is "Unable to import file *** as this is not a supported type"

thanks

From my experience, git-source-control works best with separate dev namespaces per developer. Shared namespaces cause conflicts. For static files (.js, .css, .png), import isn’t natively supported yet—you’ll need custom handling or a workaround script.