Where is the Deploy Location setting stored?

[richardm90]

I can't for the life of my find where the Deploy Location is stored?

It can differ from the Working Directory, which is stored in the settings as homeDirectory and scoped to the connection.

The Deploy Location is remembered when I reopen VS Code but doesn't appear to be scoped to workspace or connection.

Does anyone know?

[worksofliam]

It's not stored in user space. Maybe we need to store it as part of the connection settings.

@sebjulliand i might take a look into doing this.

[arco400]

@worksofliam I was under impression that the deploy location currently is stored within the VScode project.
I do use multiple VScode projects that use the same connection, but each with their own different deploy location.
To me personal, I would not be a fan of storing the deploy location in the connection settings.

[worksofliam]

@arco400 yoy are right, it's tied to the connection+workspace folder actually.

[richardm90]

@worksofliam So is it in a settings file somewhere? I had a good look but couldn't find it.

[sebjulliand]

The deploy location is saved in the extension's global state.

It seems to be the C:\Users\<user>\AppData\Roaming\Code\User\globalStorage\state\state.vscdb file (the location must be similar under Unix OSes) - but it's binary and not meant to be modified outside of VS Code.

[richardm90]

Thanks for the info guys.

So basically it's not a setting in a JSON setting file, which is good to know.

However, it doesn't appear to be tied to the connection+workspace folder as I tried experimenting by creating a new connection and the previous Deploy Location setting was remembered. If I create a new workspace and add my local folder to that workspace it still remembers the previous Deploy Location setting. It appears to be based purely on the local folder name. If I rename the local folder I am prompted for the Deploy Location setting again.

[worksofliam]

@richardm90 to me, it should be based on the connection and workspace folder.

I will put an enhancement in next week.

[richardm90]

Looks like this enhancement has already been completed #2724!

[sebjulliand]

Indeed 😅
It turns out the deploy location was intended to be saved in the global storage per connection since the beginning. But we found out a bug that made our storage implementation ignore the connection...saving everything globally every time. Thankfully that's been fixed yesterday!