-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Can't setup a new instance of OrchardCMS without PathTooLongException #5669
Comments
I updated the method to abort that directory if the path contains node_modules and it worked for me.
Can anyone see any knock on effects that this might cause? |
You need to delete the node_modules folder completely, remove packages.json and gulpfile.js. Also, please note that you will also get the same PathTooLongException for a couple of other modules (Layouts and Azure.Media, I believe). The same process resolves the issue there as well. |
See commit: 6da6c5c |
So you say this is not an issue any more? |
This was fixed by @DanielStolt in that commit. It's still a very real issue in the current 1.9.1 release |
Thanks, I did do a search in issues for I think it's safe to close this issue. FYI @DanielStolt goes into great detail into the reasoning behind this in #5450 |
I just got around to publishing the site in question today and hit a bunch of errors with the Publish / Deploy feature of Visual Studio. I'm just posting this here in case anyone else hits the same errors. You need to use 7-zip to delete the files. Open up 7-zip on its own then navigate to the offending After deleting the files mentioned by dcinzona the package created without an issue:
Delete any of these that you find in this location:
|
I've cloned the repo using GitExt as suggested in the setting up a source enlistment documentation.
When I open the solution in Visual Studio Community 2015, run it with F5 and attempt to go though the initial setup screen an exception is thrown from
ViewsBackgroundCompilation.cs
inGetViewDirectories()
.It tries to dig deep into the
node_modules
folders and eventually gets stuck on this folder:I don't think that the code should be going through the
node_modules
folders at all looking for views so I think the code needs to be changed somewhere to skip these folders.It looks like the offending code that triggers this cascade is in
ViewsBackgroundCompilation.cs
CompileViews()
. On lines 89/90 it does this:Which sends it off into a spiral of doom.
The text was updated successfully, but these errors were encountered: