Ufdjrw

What would be the benefits of having both a state and local currencies?

What are the ramifications of creating a homebrew world without an Astral Plane?

How can I replace every global instance of "x[2]" with "x_2"

Was the picture area of a CRT a parallelogram (instead of a true rectangle)?

Why are on-board computers allowed to change controls without notifying the pilots?

I'm in charge of equipment buying but no one's ever happy with what I choose. How to fix this?

when is out of tune ok?

Your magic is very sketchy

How can I get through very long and very dry, but also very useful technical documents when learning a new tool?

What is difference between behavior and behaviour

How do I define a right arrow with bar in LaTeX?

Should my PhD thesis be submitted under my legal name?

Generic lambda vs generic function give different behaviour

Greatest common substring

Minimal reference content

Is there a good way to store credentials outside of a password manager?

Can somebody explain Brexit in a few child-proof sentences?

What defines a dissertation?

Is it okay / does it make sense for another player to join a running game of Munchkin?

How does residential electricity work?

How do I rename a LINUX host without needing to reboot for the rename to take effect?

How was Earth single-handedly capable of creating 3 of the 4 gods of chaos?

Is a roofing delivery truck likely to crack my driveway slab?

What to do with wrong results in talks?

Visual Studio Git pull, merge sync specified path, file name or both are too long

What are some examples of commonly used practices for naming git branches?Using Git with Visual StudioHow do I force “git pull” to overwrite local files?Merge, update, and pull Git branches without using checkoutsGit - fatal: Unable to create '/path/my_project/.git/index.lock': File existsResolve Git merge conflicts in favor of their changes during a pullTemp path too long when publishing a web site projectPath too long exception in MTMNuget package manager long file name errorWhen I want publish Project : “the specified path, file name, or both are too long”

-1

I have a branch where by every time I perform a pull, sync or merge i get this error in Visual Studio 2017. "The specified path, file name or both are too long. The full qualified filename must be less than 260 characters, and the directory name must be less than 248 characters."

This error message seems a bit too vague as it doesn't pin point where the problem is. Is it the path name that is too long, file name or the directory name.

To get around this I have to perform the actions through gitbash.

How can i resolve this issue?

Attache dis the screenshot of the error.

git visual-studio visual-studio-2017 git-merge git-pull

share|improve this question

asked Mar 7 at 11:45

ChiefChief

4619

add a comment | 

-1

I have a branch where by every time I perform a pull, sync or merge i get this error in Visual Studio 2017. "The specified path, file name or both are too long. The full qualified filename must be less than 260 characters, and the directory name must be less than 248 characters."

This error message seems a bit too vague as it doesn't pin point where the problem is. Is it the path name that is too long, file name or the directory name.

To get around this I have to perform the actions through gitbash.

How can i resolve this issue?

Attache dis the screenshot of the error.

git visual-studio visual-studio-2017 git-merge git-pull

share|improve this question

asked Mar 7 at 11:45

ChiefChief

4619

add a comment | 

I have a branch where by every time I perform a pull, sync or merge i get this error in Visual Studio 2017. "The specified path, file name or both are too long. The full qualified filename must be less than 260 characters, and the directory name must be less than 248 characters."

This error message seems a bit too vague as it doesn't pin point where the problem is. Is it the path name that is too long, file name or the directory name.

To get around this I have to perform the actions through gitbash.

How can i resolve this issue?

Attache dis the screenshot of the error.

git visual-studio visual-studio-2017 git-merge git-pull

share|improve this question

asked Mar 7 at 11:45

ChiefChief

4619

share|improve this question

asked Mar 7 at 11:45

ChiefChief

4619

share|improve this question

asked Mar 7 at 11:45

ChiefChief

4619

asked Mar 7 at 11:45

ChiefChief

4619

asked Mar 7 at 11:45

ChiefChief

4619

1 Answer
1

active

oldest

votes

1

The key here is to find your solution's .git folder, which will be in the root of your Visual Studio solution. Right-click your solution entry in Solution Explorer and choose Open Folder in File Explorer. You will see the .git folder there:

Take note of the path that leads to this .git folder. Chances are that it's not in the root of the drive but is instead a folder or several folders down from the root. Whoever created the repository had located their solution closer to the root and never exceeded the path limit you're exceeding.

The solution is to do a Git pull to a folder location that's as close to the root as possible. Try creating a folder such as "C:MyWork" (or something like that) and pull to that folder. You very likely will get past this error. Once you do, you can drill down and inspect the deepest and longest folder paths within your solution structure. If you can identify unnecessarily long or deeply nested folders, you can shorten them and check those changes back to the repo so that others can pull to their own root folders without worrying about path lengths.

share|improve this answer

answered Mar 7 at 12:20

JazimovJazimov

7,08252940

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55043016%2fvisual-studio-git-pull-merge-sync-specified-path-file-name-or-both-are-too-lon%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

1

The key here is to find your solution's .git folder, which will be in the root of your Visual Studio solution. Right-click your solution entry in Solution Explorer and choose Open Folder in File Explorer. You will see the .git folder there:

Take note of the path that leads to this .git folder. Chances are that it's not in the root of the drive but is instead a folder or several folders down from the root. Whoever created the repository had located their solution closer to the root and never exceeded the path limit you're exceeding.

The solution is to do a Git pull to a folder location that's as close to the root as possible. Try creating a folder such as "C:MyWork" (or something like that) and pull to that folder. You very likely will get past this error. Once you do, you can drill down and inspect the deepest and longest folder paths within your solution structure. If you can identify unnecessarily long or deeply nested folders, you can shorten them and check those changes back to the repo so that others can pull to their own root folders without worrying about path lengths.

share|improve this answer

answered Mar 7 at 12:20

JazimovJazimov

7,08252940

add a comment | 

1

The key here is to find your solution's .git folder, which will be in the root of your Visual Studio solution. Right-click your solution entry in Solution Explorer and choose Open Folder in File Explorer. You will see the .git folder there:

Take note of the path that leads to this .git folder. Chances are that it's not in the root of the drive but is instead a folder or several folders down from the root. Whoever created the repository had located their solution closer to the root and never exceeded the path limit you're exceeding.

The solution is to do a Git pull to a folder location that's as close to the root as possible. Try creating a folder such as "C:MyWork" (or something like that) and pull to that folder. You very likely will get past this error. Once you do, you can drill down and inspect the deepest and longest folder paths within your solution structure. If you can identify unnecessarily long or deeply nested folders, you can shorten them and check those changes back to the repo so that others can pull to their own root folders without worrying about path lengths.

share|improve this answer

answered Mar 7 at 12:20

JazimovJazimov

7,08252940

add a comment | 

The key here is to find your solution's .git folder, which will be in the root of your Visual Studio solution. Right-click your solution entry in Solution Explorer and choose Open Folder in File Explorer. You will see the .git folder there:

Take note of the path that leads to this .git folder. Chances are that it's not in the root of the drive but is instead a folder or several folders down from the root. Whoever created the repository had located their solution closer to the root and never exceeded the path limit you're exceeding.

The solution is to do a Git pull to a folder location that's as close to the root as possible. Try creating a folder such as "C:MyWork" (or something like that) and pull to that folder. You very likely will get past this error. Once you do, you can drill down and inspect the deepest and longest folder paths within your solution structure. If you can identify unnecessarily long or deeply nested folders, you can shorten them and check those changes back to the repo so that others can pull to their own root folders without worrying about path lengths.

share|improve this answer

answered Mar 7 at 12:20

JazimovJazimov

7,08252940

share|improve this answer

answered Mar 7 at 12:20

JazimovJazimov

7,08252940

answered Mar 7 at 12:20

JazimovJazimov

7,08252940

answered Mar 7 at 12:20

JazimovJazimov

7,08252940