AFAICT the latest nuget fixed this. I've tested on 3 servers and it
works like a champeen. I still can't get it working locally (And my
looks like it's me at this point. Once I figure out whats up on my
On Oct 14, 10:39 pm, Joshua Arnold <
rncodep...@gmail.com> wrote:
> Last step is minor clean up and docs so that I can pawn that off on someone
> else to keep it going.
>
>
>
>
>
>
>
> On Fri, Oct 14, 2011 at 9:38 PM, Mike O'Brien <
m...@mikeobrien.net> wrote:
> > Ok, np, thanks for taking a look.
>
> > BTW, loving the diagnostics, thanks for all your work on that!
>
> > On Fri, Oct 14, 2011 at 10:36 PM, jmarnold <
rncodep...@gmail.com> wrote:
>
> >> Interesting. Let me take a peek but I'm not going to spend TOO much
> >> time on this. The asset stuff is about to get pushed in so I'll take a
> >> peek when that hits.
>
> >> On Oct 14, 9:34 pm, hcoverlambda <
m...@mikeobrien.net> wrote:
> >> > I've run into a weird issue with diagnostics (0.9.1.568 & 0.9.1.578)
> >> > and IIS 7.5. When I create a new stock web app + the latest nuget and
> >> > hit the diagnostics via cassini it works fine. But if I switch it over
> >> > to using IIS instead then nothing under ~/_content is available. So
> >> > the diagnostics page (~/_fubu) comes up but none of the stylesheets,
> >> > js, etc are being loaded. There are also no routes showing up in the
> >> > diagnostics but they are still accessible. I've tried this in a couple
> >> > of projects and on a couple of machines with the same result. Here is
> >> > what I'm talking about:
>