F7 everytime rebuilds

Question

0.00/5 (No votes)

See more:

, +

When my project and sources are located on a network drive, F7 always rebuilds. I'm talking about Visual Studio 2010, C#, form applications. The network drive is provided by a samba share. smb.conf is as follows:

Quote:
[global]
protocol = SMB2

[root]
comment = the whole file system
read only = false
locking = no
path = /
hosts allow = all
writeable = yes
browsable = yes
create mode = 0644
directory mode = 0755
guest ok = yes
public = yes

This is while when on a local drive (C:), there's not such problem. It seems that there's an issue with modification times of files. The machine in which Windows is installed is a virtual machine provided by VirtualBox, although I don't see it as a cause. Any idea?

What I have tried:

I've no clue what the cause may be.

Posted 18-May-18 21:33pm

ilostmyid2

Updated 19-May-18 1:10am

Add a Solution

2 solutions

Solution 1

I have seen this in the past where such shares do not sync the dates and times correctly, so Visual Studio always thinks that some sources are out of date.

Posted 18-May-18 22:04pm

Richard MacCutchan

Updated 18-May-18 22:05pm

v2

Comments

ilostmyid2 21-May-18 5:31am

the question is exactly this, what causes the date-time not to be synced?

Richard MacCutchan 21-May-18 5:41am

It's an issue with Samba.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Accepted Answer · 2018-05-19T01:11:00

You can try to set the

dos filetime resolution = yes
fake directory create times = yes

options. This was necessary with older VS versions but I don't know if recent VS versions still behave as described at smb.conf[^]:

dos filetime resolution (S)
Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second resolution is made to smbd(8).

This option is mainly used as a compatibility option for Visual C++ when used against Samba shares. If oplocks are enabled on a share, Visual C++ uses two different time reading calls to check if a file has changed since it was last read. One of these calls uses a one-second granularity, the other uses a two second granularity. As the two second call rounds any odd second down, then if the file has a timestamp of an odd number of seconds then the two timestamps will not match and Visual C++ will keep reporting the file has changed. Setting this option causes the two timestamps to match, and Visual C++ is happy.