Open dammitjanet opened 7 years ago
I am also experiencing the same issue when the bundled files already exist in the project.
This is happening for me too. Every time I save a change in any input file, VS2015 becomes "Not Responding" and I have to force the task closed. Really painful!
I am also experiencing this issue. VS only crashes if I have the extension enabled.
I am experiencing this issue as well. I LOVED this extension until it started hanging VS a month or two ago. Now it is quite consistently annoying. Disable the extension and no issues, but no bundling either :( (Did try uninstalling the extension and reinstalling, no joy. Extension version 2.3.330, VS version 14.0.25431.01 Update 3 )
Same problem here, is astonishing how lack of attention this fundamental extension has received :(
This issue still exists on the latest version of the extension. I am using it with a .NET Framework project.
Same issue for me. VS2017 Community 15.9.2 Bundler & Minifier 2.8.396.
This is happening for me by simply adding a new C# file to a project. Pretty frustrating.
Installed product versions
Description
VisualStudio becomes unresponsive when the following conditions are met
Steps to recreate
Current behavior
The minification process works as expected, however it would appear that the 'BundleService.AfterWritingFile' event fails when includeInProject=true causing VS to become unresponsive. More specifically, the issue occurs because the ProjectHelpers.AddNestedFile fails at this point because the filename being passed already exists and is already in the project
Expected behavior
Don't cause VS to die.
Workaround - add "includeInProject": false