Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.locked file extension #479

Closed
gmenezesg opened this issue Nov 12, 2018 · 3 comments
Closed

.locked file extension #479

gmenezesg opened this issue Nov 12, 2018 · 3 comments
Assignees
Labels
azdo-sync Azure DevOps Sync not-on-roadmap Not currently planned
Projects

Comments

@gmenezesg
Copy link

gmenezesg commented Nov 12, 2018

Please change the .locked file extension for any other extension or allow us to choose the extension name, since the .locked is a well known extension used by ransomware. At a corporate environment, some antivirus solutions block this extension.

VS bug #732189

@newky2k
Copy link
Contributor

newky2k commented Nov 13, 2018

@gmenezesg Could you please be a bit more specific? What are you referring to exactly?

Regards

@newky2k newky2k added the needs-info More information is requested by engineering label Nov 14, 2018
@Redth Redth added this to Needs triage in Triage Nov 19, 2018
@Redth Redth added Proposed azdo-sync Azure DevOps Sync and removed needs-info More information is requested by engineering labels Nov 19, 2018
@Redth Redth self-assigned this Nov 19, 2018
@Redth
Copy link
Member

Redth commented Nov 19, 2018

Guessing this is Xamarin.Build.Download. The .locked is what we use. Sad that antivirus software is just checking filenames instead of heuristics :(. But we can consider changing this in future versions.

@Redth Redth moved this from Needs triage to Low priority in Triage Nov 19, 2018
@Redth Redth added the not-on-roadmap Not currently planned label Dec 3, 2018
@Redth
Copy link
Member

Redth commented Dec 3, 2018

After looking into this, it's a bit more complicated than just switching the filename. The problem is the .locked file is used to ensure there is no contention across projects or even separate instances of visual studio while working on a file that might be used by these instances (we try and obtain an exclusive write lock to this file).

If we change the filename on a newer version of Xamarin.Build.Download we risk other projects or instances of the IDE still using older versions of Xamarin.Build.Download, and the old filename, and so we risk contention.

Unfortunately this doesn't look like something we should change. The advice for now is to set an exception for .locked files in the particular path they are found %localappdata%\XamarinBuildDownloadCache.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azdo-sync Azure DevOps Sync not-on-roadmap Not currently planned
Projects
Triage
  
Closed
Development

No branches or pull requests

3 participants