New Fubu+StructureMap Weirdness

42 views
Skip to first unread message

hcoverlambda

unread,
Aug 15, 2014, 12:45:31 PM8/15/14
to fubumv...@googlegroups.com
We updated a few weeks ago to the latest Fubu (1.3.0.1710) and SM (3.0.5.130) and were seeing a lot of sporadic errors in our production logs along these lines:

System.InvalidCastException: Unable to cast object of type 'FubuMVC.Core.Http.AspNet.AspNetRequestData' to type 'FubuMVC.Core.Http.ICurrentChain'. 
at StructureMap.BuildSession.GetInstance[T]() in c:\BuildAgent\work\996e173a8ceccdca\src\StructureMap\BuildSession.cs:line 55 

System.InvalidCastException: Unable to cast object of type 'FubuMVC.Core.Http.AspNet.AspNetStreamingData' to type 'FubuMVC.Core.Http.ICurrentChain'. 
at StructureMap.BuildSession.GetInstance[T]() in c:\BuildAgent\work\996e173a8ceccdca\src\StructureMap\BuildSession.cs:line 55 

System.InvalidCastException: Unable to cast object of type 'FubuMVC.Core.Http.AspNet.AspNetHttpWriter' to type 'FubuMVC.Core.Http.ICurrentChain'.

System.InvalidCastException: Unable to cast object of type 'StructureMap.Container' to type 'FubuMVC.Core.Http.ICurrentChain'. 

Can't seem to repro in dev or test server. It's happening on both our api and website. Just wanted to throw this out there in case someone else has seen this.

hcoverlambda

unread,
Aug 18, 2014, 10:07:58 AM8/18/14
to fubumv...@googlegroups.com
Dropped us down to StructureMap 2.6.3 and FubuMVC.StructureMap 1.3.0.1710 and the errors go away.

Gary Brunton

unread,
Aug 21, 2014, 7:20:39 PM8/21/14
to fubumv...@googlegroups.com
At this point, what do you see as the incentive for upgrading to the latest fubu and/or structuremap? I'm not trying to be facetious here with my question.  I'm really serious.  With the lack of leadership of this framework aren't you only asking for trouble trying to upgrade.  Wouldn't it make more sense to stay on a stable release or are there features that you really want?

We've stopped the effort of upgrading.  We have a rather large (large for us) application that is still growing in features that we just don't know what to do with.  We have a small team so we feel a little stuck at this point.  I'm kind of waiting for asp .net vnext but I'm not even sure that's realistic at this point.

Anyways, just curious as to your thoughts (or others) regarding the decision to try and upgrade things.

Thanks,
Gary Brunton
Reply all
Reply to author
Forward
0 new messages