If it helps, we're not doing anything particularly fancy with Windsor. We
populate the container using about a half dozen basic registration calls
and then hand it off to NServiceBus. This exception occurred within the
context of an NSB handler, but I've seen it in an MVC context as well.
We
I have a really strange issue that I only see when deploying my app to
Azure. A full stack trace is at the bottom. I'm deploying it with full
trust using the latest OS.
System.Data.ProviderIncompatibleException: The provider did not return a
ProviderManifest instance. ---
Thanks! I am glad to know it wasn't something crazy about my app. Any idea
when 3.2.1 might go out?
Is this new to 3.2 or was it in 3.1 as well? I think I could probably roll
back to 3.1 with assembly redirects. This has come up in the context of a
pretty big upgrade and it'd involve changing ~25
It's also in v3.1
The New version will be out when I have some time to release it, hopefully
next week
Krzysztof
sent from my phone
On 21/07/2013 8:35 AM, Shawn Hinsey smhin...@gmail.com wrote:
Thanks! I am glad to know it wasn't something crazy about my app. Any idea
when 3.2.1 might go
No package, but you might be able to swap the bits
Krzysztof
sent from my phone
On 21/07/2013 8:57 AM, Shawn Hinsey smhin...@gmail.com wrote:
Thanks, I will keep an eye out.
Is there a pre-release package that I could snag which has this fix, or
maybe some other kind of workaround? I ran
Hi Shawn,
It's a known issue, that's been fixed already.
That happens in a cross-appDomain usage with default scoped lifestyle involved.
I think we're due for v3.2.1 release…
HTH,
Krzysztof
--
Krzysztof Kozmic
On Sunday, 21 July 2013 at 2:11 AM, Shawn Hinsey wrote:
If it helps, we're
Good call, that sounds way easier. Thanks.
On Sat, Jul 20, 2013 at 4:08 PM, Krzysztof Koźmic
krzysztof.koz...@gmail.com wrote:
Actually, you can take a non nuget build from our team city
Krzysztof
sent from my phone
On 21/07/2013 9:07 AM, Shawn Hinsey smhin...@gmail.com wrote:
You mean
You mean with a local build of Windsor? I'll give that a shot, thanks.
On Sat, Jul 20, 2013 at 4:00 PM, Krzysztof Koźmic
krzysztof.koz...@gmail.com wrote:
No package, but you might be able to swap the bits
Krzysztof
sent from my phone
On 21/07/2013 8:57 AM, Shawn Hinsey
Actually, you can take a non nuget build from our team city
Krzysztof
sent from my phone
On 21/07/2013 9:07 AM, Shawn Hinsey smhin...@gmail.com wrote:
You mean with a local build of Windsor? I'll give that a shot, thanks.
On Sat, Jul 20, 2013 at 4:00 PM, Krzysztof Koźmic
Thanks, I will keep an eye out.
Is there a pre-release package that I could snag which has this fix, or
maybe some other kind of workaround? I ran into this as part of a larger
upgrade which I'd like to avoid having to roll back, so I don't mind a hack
(even an ugly one) if it only needs to stick
I will now, you too!
On Sat, Jul 20, 2013 at 4:27 PM, Krzysztof Koźmic
krzysztof.koz...@gmail.com wrote:
No worries. Glad it helped :)
Have a great weekend
Krzysztof
sent from my phone
On 21/07/2013 9:24 AM, Shawn Hinsey smhin...@gmail.com wrote:
That did it. Thanks a lot, I was not
No worries. Glad it helped :)
Have a great weekend
Krzysztof
sent from my phone
On 21/07/2013 9:24 AM, Shawn Hinsey smhin...@gmail.com wrote:
That did it. Thanks a lot, I was not looking forward to having to go back
to 4.0 and probably spent way too much time trying to avoid it.
On Sat,
Ah, I see what you mean now. Have you considered using a higher-order
function (or a decorator) instead of a proxy?
--
Mauricio
On Fri, Jul 19, 2013 at 6:22 AM, Kristijan Horvat khor...@icodeteam.netwrote:
Ok, np I have a BeforeInvoke method that I need to await so my code looks
more like
That did it. Thanks a lot, I was not looking forward to having to go back
to 4.0 and probably spent way too much time trying to avoid it.
On Sat, Jul 20, 2013 at 4:10 PM, Shawn Hinsey smhin...@gmail.com wrote:
Good call, that sounds way easier. Thanks.
On Sat, Jul 20, 2013 at 4:08 PM,
14 matches
Mail list logo
