VPC embarrassment (after the virtual machine of the VPC copies a few files, the program suddenly reports an error)

After the virtual machine in the VPC copies several files ProgramCrazy Error

VPC is often used, but it is still used well. It only modifies a local script, copies it to the virtual machine, and finds that the script reports an error. When debugging and tracking, the script file cannot be loaded at all.

Even if you copy a DLL file or folder, the program will not be able to log on and crash.

Is it because God is punishing me? How is it possible? I see flowers and flowers, cars and cars, and people. How can this happen!

Is there an error in the file to be copied? It is impossible. After I deploy the file in the local environment, I will run everything OK. What is the problem.

Suddenly, some time ago, I heard from the implementers that sometimes, when copying files to a virtual machine, the permission may be lost, resulting in the program being unable to run.

Right-click the file, right-click the file, and choose Properties to view the security permissions. As a result, there are only three permissions:

1. System
2. Administrator (Users \ Administrator)
3. Administrators (Users \ administrators)

Nnd: No wonder it cannot be run. It's really amazing.

Now the problem has been found. Add the required permissions to the file and everything is OK.

What permissions are required? You can refer to the permissions of other files in this directory.

But why are there only a few permissions left?

Think about the process of copying and deploying.

It turns out that after I compress it, I send it to the email and someone else decompress it to the local device. At this time, the file permission should have changed, with only three permissions left.

Therefore, when copying data to a VM, the permission is insufficient and cannot be viewed.

However, the permissions of our files are inherited from folders.

Why is it not inherited?

I don't know.