Assembly title will be "Castle.Windsor 2.5.4 for .NETFramework v4.0 *Client Profile*"

@K
On 11/02/2012 9:21 AM, Shawn Hinsey wrote:
Hmm, interesting, I hadn't considered that. What's the quickest test for that?

2012/2/10 Krzysztof Koźmic <[email protected] <mailto:[email protected]>>

    The only thing I can think of is that you ended up with Client
    Profile version of the assembly which doesn't have the web stuff
    in it.

    @K


    On 11/02/2012 9:16 AM, Shawn Hinsey wrote:
    Ah, interesting. The way that this problem presented itself
    wasn't specifically tied to the assembly version, we just thought
    it might be the likely culprit.

    Specifically what was happening was, relatively out of nowhere,
    we started getting the "type cannot be loaded" exception from the
    PerWebRequestLifestyle even though we could physically verify
    that the assemblies were in the bin directory.

    Does this ring any bells? As I said, it's totally possible
    something else is causing this problem, but we've been going in
    circles for awhile and have been unable to make a firm declaration.

    2012/2/10 Krzysztof Koźmic <[email protected]
    <mailto:[email protected]>>

        Windsor 2.5.x all have AssemblyVersion 2.5.1 (to allow drop
        in replacement without recompiling every dependency). Look at
        file version or description to see which version you have. It
        will say something like: Castle.Windsor 2.5.4 for
        .NETFramework v4.0

        @K


        On 11/02/2012 9:07 AM, Shawn Hinsey wrote:
        Oh, I'm not certain it's even being caused by Windsor. We
        have a fairly complex app with a lot of moving parts.

        During the process of figuring out how we wanted to package
        it up for nuget, we started running into issues where the
        2.5.3 nuget package would somehow end up
        asCastle.Windsor.dll version 2.5.1 when it was installed by
        our package. We're upgrading to 2.5.4 to see if that
        resolves it because the app makes fairly extensive use of
        type forwarding and it's not a clean upgrade to 3.x.

        While that's going on, I'm looking into what other issues we
        might run into if we decided to just ditch 2.5.x and make
        the switch.

        2012/2/10 Krzysztof Koźmic <[email protected]
        <mailto:[email protected]>>

            what assembly versioning issue?

            @K


-- You received this message because you are subscribed to
            the Google Groups "Castle Project Users" group.
            To post to this group, send email to
            [email protected]
            <mailto:[email protected]>.
            To unsubscribe from this group, send email to
            [email protected]
            <mailto:castle-project-users%[email protected]>.
            For more options, visit this group at
            http://groups.google.com/group/castle-project-users?hl=en.


-- You received this message because you are subscribed to the
        Google Groups "Castle Project Users" group.
        To post to this group, send email to
        [email protected]
        <mailto:[email protected]>.
        To unsubscribe from this group, send email to
        [email protected]
        <mailto:[email protected]>.
        For more options, visit this group at
        http://groups.google.com/group/castle-project-users?hl=en.

-- You received this message because you are subscribed to the
        Google Groups "Castle Project Users" group.
        To post to this group, send email to
        [email protected]
        <mailto:[email protected]>.
        To unsubscribe from this group, send email to
        [email protected]
        <mailto:castle-project-users%[email protected]>.
        For more options, visit this group at
        http://groups.google.com/group/castle-project-users?hl=en.


-- You received this message because you are subscribed to the
    Google Groups "Castle Project Users" group.
    To post to this group, send email to
    [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/castle-project-users?hl=en.

-- You received this message because you are subscribed to the Google
    Groups "Castle Project Users" group.
    To post to this group, send email to
    [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:castle-project-users%[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/castle-project-users?hl=en.


--
You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Castle 
Project Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/castle-project-users?hl=en.

Reply via email to