I've been trying to install Cassette for bundling style and script bundles. Installing it from NuGet works fine and everything works as expected on the frontend. When opening the console, however, problems arise. All I get from ~/Composite/top.aspx is an empty document response. I have confirmed that when uninstalling the Cassette package the console runs as normal again.
Steps to reproduce are simple:
1. Install Composite C1
2. Run the console - everything is fine
3. Install Cassette.AspNet from NuGet
4. Run the console - empty response returned.
Comments: ** Comment from web user: madsgodvinjensen **
Steps to reproduce are simple:
1. Install Composite C1
2. Run the console - everything is fine
3. Install Cassette.AspNet from NuGet
4. Run the console - empty response returned.
Comments: ** Comment from web user: madsgodvinjensen **
I've been digging around for at solution to this problem and have gathered some more info:
When creating for example a ~/Composite/test.aspx that just Response.Writes a string everything is fine. But after adding the first two Composite-things in top.aspx the page response is empty:
<control:appinitializer runat="server"/>
<control:httpheaders runat="server"/>
As it turns out, adding only the appinitializer works fine, but adding the httpheaders control does not. So it would seem there is something in the httpheaders control that conflicts with Cassette somehow.