Yes - that's what I'm saying.
Let's first try to generate all versions we need (.NET 3.5, 4, 4 ClientProfile, Sl3 and Sl4) from single set of files using MsBuild 4.
That would be the best solution, since it has least moving parts.

K

On 2010-06-11 08:18, Julian Birch wrote:
I'm a bit confused here. I thought you had the solution file generating both silverlight and .net now. If you need ST, there's a fork at http://github.com/JulianBirch/Castle.Core which generates a working solution file using the targets in the build file. (It's also got the artefacts checked in, but I wouldn't do that on trunk...)

One day, I need to understand MSBuild 4 properly...

J

2010/6/10 Krzysztof Koźmic <[email protected] <mailto:[email protected]>>

    That would complicate things I think.

    We might add a target to the build file at some point to have it
    generate the files using just one click, but that's future. For
    now I want to get the build going and it's best if we stick to
    just single solution for that.

    K


    On 2010-06-11 07:35, John Simons wrote:
    Also, if we are using Julian's solution to keep VS
    solutions/projects in sync, wouldn't make sense to use the
    generated sln/proj files to build, this would validate that we
    have valid files. and since the files are auto gen anyway, there
    is no overhead right?

    Just my 2 cents
    John

    ------------------------------------------------------------------------
    *From:* Krzysztof Koźmic <[email protected]>
    <mailto:[email protected]>
    *To:* [email protected]
    <mailto:[email protected]>
    *Sent:* Fri, 11 June, 2010 7:22:51 AM
    *Subject:* Re: silverlight build

    No we're not.

    That's what Julian's Solution Transform tool was created for -
    create SL solution based on .NET solution.

    K

    On 2010-06-11 07:20, John Simons wrote:
    Oops, I think that was me!
    But if we not using the silverlight solution file then how do I
    go about opening the VS solution for silverlight? Are we keeping
    it in sync?

    Cheers
    John

    ------------------------------------------------------------------------
    *From:* Krzysztof Koźmic <[email protected]>
    <mailto:[email protected]>
    *To:* [email protected]
    <mailto:[email protected]>
    *Sent:* Thu, 10 June, 2010 10:46:41 PM
    *Subject:* Re: silverlight build

    I couldn't agree more, and looking at one of recent build logs:
    
http://builds.castleproject.org/viewLog.html?buildId=5710&tab=buildResultsDiv&buildTypeId=bt50
    
<http://builds.castleproject.org/viewLog.html?buildId=5710&tab=buildResultsDiv&buildTypeId=bt50>
    it looks like we did that, so I think it's a recent change that
    affected that somehow.

    K

    On 2010-06-10 22:37, Roelof Blom wrote:
    I think it's a relic and we should try and build from one solution.

    2010/6/10 Krzysztof Koźmic <[email protected]
    <mailto:[email protected]>>

        Did we change something WRT how Silverlight version of Core
        get built?

        Last time I checked SL version was built from the same
        solution as .NET version, and now it tries (and fails) to
        find dedicated SL solution.

        Was that a conscious change?

        K

-- You received this message because you are subscribed to the
        Google Groups "Castle Project Development List" 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-devel%[email protected]>.
        For more options, visit this group at
        http://groups.google.com/group/castle-project-devel?hl=en.


-- You received this message because you are subscribed to the
    Google Groups "Castle Project Development List" 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-devel?hl=en.

-- You received this message because you are subscribed to the
    Google Groups "Castle Project Development List" 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-devel?hl=en.

      --
    You received this message because you are subscribed to the
    Google Groups "Castle Project Development List" 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-devel?hl=en.

-- You received this message because you are subscribed to the
    Google Groups "Castle Project Development List" 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-devel?hl=en.

      --
    You received this message because you are subscribed to the
    Google Groups "Castle Project Development List" 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-devel?hl=en.

-- You received this message because you are subscribed to the Google
    Groups "Castle Project Development List" 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-devel%[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/castle-project-devel?hl=en.


--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.

--
You received this message because you are subscribed to the Google Groups "Castle 
Project Development List" 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-devel?hl=en.

Reply via email to