Where is setting option that allows to change the app's location? - visual-studio-code

Basically VS Code can't update because it is located in the different location to the default one. It tries to update itself in the default location, but fails. How can I change this without uninstalling it?
Here is a picture of the error:
Here is what the log says:

Related

How can I change the update path for VS Code?

Essentially the same query as How to Change VS Code Code.exe Path for Update? , as shown by 'Similar questions'.
Is there any registry value (I am not familiar with such, so it may be a trivial doubt) that I can change so that 'Restart to Update' doesn't reference C:\Users\name\AppData\Local\Programs\Microsoft VS Code\Code.exe, and instead to my custom location?
Could I set the install location manually, instead of the default User Setup, if I am forced to reinstall the application?

Cannot create a flutter app using flutter create

When i run flutter create I get
Im not sure why that png is a sticking point everything above it are in the same parent folders. Has anyone run into this issue?The Programming Flutter folder seems like it is being set as read only:
But when i uncheck the Read only box and click apply when i open it again its set to Read Only again. But thats the very parent folder and other files seem to copy across fine before the error above.
Anyone have any idea why its failing?
Have you recently updated your Flutter version, or are you running on an older version? As per this thread, it seems to have been fixed somewhere in 2020.
It is your operating system not allowing Flutter to write files.
You can either delete that folder and create that again or change permissions. Uncheck that 'read-only' checkbox shown in picture.
You can learn more about handling permissions here.

How to temporarily disable "preventing dirty writes" feature in Visual Studio Code

In my project, I've used some build/linting tools so they can automate force change my code based on some convention code styles but when I was running those scripts, vs code showed an error message:
Failed to save "<file-name>": The content on disk is newer. Please compare your version with the one on disk.and continue to open the "Resolve to save conflict" tab.
It seems to be annoying and not convenient for me.
So can you tell me how to disable this feature of VScode for a temporarily time?
v1.42 is modifying this functionality including adding a setting so that the dirty file/save conflict notification can be disabled. See https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_42.md#ignore-save-conflicts
Ignore save conflicts
VS Code has a built-in mechanism to show an error when you try to save
a dirty file that has been changed outside of VS Code or by another
program (for example Git):
The motivation is to inform you that saving will overwrite the
contents on disk even though the file was changed after the file
became dirty. Clicking the Compare button lets you review your change
along with the version on disk and either overwrite or revert the
file.
In cases where you know that the changes on disk can be overwritten,
there is now an Overwrite button directly on the notification. You can
also configure files.saveConflictResolution globally or per workspace or
file type to disable the notification altogether. The options are askUser (default) or overwriteFileOnDisk.

Eclipse RCP Binding Service Sometimes Doesn't find key binding conflicts

My RCP app has key binding conflicts among some of the features I've included, which are shown on the console at launch. Because many of my users are new to Eclipse, I want to handle this for them, so I detect the conflicts and remove them by assigning one command in each conflicting pair to an unused custom context.
This works as desired, except that sometimes the binding service fails to find the conflicts, even though they're reported on the console. This is how I search for the conflicts:
IBindingService bs =
PlatformUI.getWorkbench().getService(IBindingService.class);
KeySequence keySequence = ...//key sequence known to have binding conflicts
Collection<Binding> bindings =
bs.getConflictsFor(KeySequence.getInstance(keySequence));
After changing the context for some of the conflicting bindings, I save them all (with type set to USER) via bs.savePreferences(bs.getActiveScheme(), bindings.toArray(new Binding[0]));
When I do the above on a fresh workspace, the conflicts are resolved as expected for subsequent launches. Then to test the ability to restore them (in case some users want to specify a different resolution) I click "Restore Defaults" on the General-> Keys preference page. Sometimes when I do this, I see the conflicts logged on the console. In this case, I know that when I restart the app, it will once again find the conflicts.
But sometimes I don't see the console message when I restore the default bindings. In that case, for every subsequent launch of the app, the conflicts will be reported on the console, but the binding service will not find them. If I click "Restore Defaults" one more time, or launch in a fresh workspace, then the binding service will find the conflicts.
When the app is in the state where conflicts are reported on the console but not by the binding service, the file org.eclipse.ui.workbench.prefs in the settings area has the following entry: org.eclipse.ui.commands=<?xml version\="1.0" encoding\="UTF-8"?>\n<org.eclipse.ui.commands/>
I can't find any predictor of when the problem will occur or not. It seems to just randomly occur, close to 50% of the time after restoring the default bindings. Since starting in a fresh workspace fixes the problem, it seems that relevant state is being stored somewhere in addition to the org.eclipse.core.runtime settings file, but I have no idea where.
EDIT: I found the scenario in which it breaks. If I launch the app and it saves the customized bindings through the binding service, and then I click "Restore Defaults" (as opposed to relaunching the app and then restoring) I get into the failed state mentioned above.
At that point, the customized bindings are not in the org.eclipse.ui.workbench.prefs settings file, and the app model (workbench.xmi in org.eclipse.e4.workbench) has <bindings> elements with the same key sequence in the same parent <bindingtables> element, but the binding service is not reporting any conflicts (though the console log does). This seems like a bug. I'll report it as such unless someone thinks otherwise.
EDIT2: I failed to notice at first, but the problem is that in the failed state, there is (in the application model xmi file) a child <tags> element for the binding with value deleted. If I manually remove that tag, then the binding service recognizes the conflict. So here now is the actual problem, I think:
When I reset defaults for the key bindings in the same application
session in which I saved customized bindings, the default bindings
that were restored are tagged as deleted in the application model.
I resolved the problem by adding a line which reads the binding information from the registry and preferences, and overwrites the information in the binding service. I added this line after the code which saves the customized binding preferences.
IBindingService bs = ...
bs.savePreferences(bs.getActiveScheme(), bindings.toArray(new Binding[0]));
bs.readRegistryAndPreferences(null); //Added this line

Get all latest action - gives warning `Cannot locate file`

After get all latest action in Enterpreise architect i get`warning
saying:
Cannot locate file 0x800c0006
After pressing ok the process continues.
How can i make that warning will not pop out?
This problem probably occurs because a file has been removed from the version control system without first "uncontrolling" the corresponding package in EA.
Now EA tries to get the latest version of the file, but the file does't exist anymore.
I guess the only thing you can do is check each and every controlled package to make you you can still do a getlatest. That will allow you to identify the missing file.
You can't. Except you simply avoid that case by checking that the file is present (in whatever API operation you invoked here).
You should also look into this wiki which suggests to run a file system check.