Solution Transform can handle the conversion of csproj and sln files,
for .net 4 and Vs2010.  I'm afraid I can't actually work on this right
now, because my home computer has finally given up the ghost.  But
anyone who has the time can take a look at the ST integration of core
on my github account.  There's one bugfix to the common targets file
there as well.

J

On Tuesday, March 30, 2010, Henry Conceição <[email protected]> wrote:
> Roelof, correct if I'm wrong: you just need to add a new
> settings-v4.0.proj containing the conditional compilation symbols and
> target a build to use the v4.0
>
> Cheers,
> Henry Conceição
>
>
>
> 2010/3/30 Krzysztof Koźmic <[email protected]>:
>> do we need .NET 4.0 .csproj .sln files on the buildserver or can
>> MSBuild pick and compile them from .NET 3.5 projects?
>>
>> Roelof, Henry - could you guys take a look at it?
>>
>> On Mar 17, 9:21 pm, Julian Birch <[email protected]> wrote:
>>> I've spent very little time on this, but I got the impression you
>>> could get it going in parallel with Silverlight, so no real need for a
>>> branch.  Most of the supports already in MsBuild and I can add a line
>>> to generate the solutions.
>>>
>>> Update: I've got the Silverlight solution generation working from
>>> command line last weekend.  I'm hoping to figure out the build system
>>> a bit more this weekend.  Current progress is on github.  Silverlight
>>> passes 95% of the tests.  .net 4 won't compile because of deprecated
>>> methods: mostly permissioning.
>>>
>>> J
>>>
>>> On Wednesday, March 17, 2010, Krzysztof Koźmic
>>>
>>>
>>>
>>> <[email protected]> wrote:
>>> > did anyone start looking into this?
>>>
>>> > I'd like to create a .NET 4 branch for Core/DP and Windsor and have it 
>>> > plugged into our TeamCity
>>>
>>> > Krzysztof
>>>
>>> > --
>>> > 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 
>>> > athttp://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.
>
>

-- 
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