I am testing out BundleTransformer, because I'd love to use it. I wanted to make sure that things could fail gracefully if something goes wrong.
I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).
Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!
__EDIT:__
I found the application error in my Event Viewer:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Hello, Jake! This error occurs only in 64-bit mode. This error was contained somewhere in source code of libSass version 3.3.6, and it seems, that it occurs only in assemblies compiled by the Visual C++. Therefore, to solve this problem, I built a LibSass Host for .Net based on the latest version of the libSass (version of July 4, 2016). I recommend you upgrade the LibSass Host for .Net to version [0.5.2](https://github.com/Taritsyn/LibSassHost/releases/tag/v0.5.2).
I attempted to do an `@import` to a bogus path, to see what would happen. I assumed the bundle would just fail to compile, and would spit out an empty file, or something. Instead, the IIS process crashed over and over and eventually didn't restart, causing a 503 error (service unavailable).
Have I configured something incorrectly? I would definitely want to avoid a situation like this in production. Thanks!
__EDIT:__
I found the application error in my Event Viewer:
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: LibSassHost.Native-64.dll, version: 0.0.0.0, time stamp: 0x571ca76c
Exception code: 0xc0000409
Fault offset: 0x00000000000d7124
Faulting process id: 0x7dd0
Faulting application start time: 0x01d1d8b287f38d23
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: D:\{path-to-my-project}\LibSassHost.Native\LibSassHost.Native-64.dll
Report Id: eb28eb63-44a5-11e6-84c7-3085a99b439e
Comments: Hello, Jake! This error occurs only in 64-bit mode. This error was contained somewhere in source code of libSass version 3.3.6, and it seems, that it occurs only in assemblies compiled by the Visual C++. Therefore, to solve this problem, I built a LibSass Host for .Net based on the latest version of the libSass (version of July 4, 2016). I recommend you upgrade the LibSass Host for .Net to version [0.5.2](https://github.com/Taritsyn/LibSassHost/releases/tag/v0.5.2).