-
Notifications
You must be signed in to change notification settings - Fork 253
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
NuGet packaging hangs if content folder contains too many files #348
Comments
Can you please provide specific repro steps, specifically the command you ran and the types/sizes of the files you are using to generate the package |
If you've uploaded the package to NuGet, please send us the link |
I have this repository, https://github.com/neurospeech/atoms.js which contains "nuget/Atoms.js" folder. And you can see nuget specs. https://github.com/neurospeech/atoms.js/blob/master/nuget/Atoms.js/Package.nuspec Inside "style" folder of my repository root, I have style sheets that are included in nuget package. But it looks like, if I add more LESS files, NuGet packager halts completely if there are more than current number of files. https://github.com/neurospeech/atoms.js/tree/master/style I had added 5 more LESS files, and I noticed the problem. Eventually, we combined all LESS files into one Unsorted.less file, that reduced total number of files, and we were able to build package. |
Has there been any progress on this? Today I ran into the same problem. If the number of files is greater than a certain number (49 in my case – the file sizes don't seem to matter), |
We haven't made much progress on this unfortunately. We plan to refactor pack to stop using OPC, and hopefully that should also resolve this issue. |
@toddm would you check if this repros in 3.5.0? |
I cloned the repo, added 10 more css files, and did a pack with 3.5.0 and it worked without any problem. |
Checked and verified, till 55 content files NuGet had no problem, but when we reached 65 content files, NuGet hangs and does not create new package.
The text was updated successfully, but these errors were encountered: