.net 4 builds

[Krzysztof Koźmic]

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

[Julian Birch]

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

> --
> 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 castle-pro...@googlegroups.com.
> To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
>
>

[Krzysztof Koźmic]

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?

[Henry Conceição]

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 <krzyszto...@gmail.com>:

[Julian Birch]

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

[Roelof Blom]

Yup. Don't know if it works right away as I did not really try v4 at the time.

Of course you'll need to build with MSBuild 4.0. MSB4 is also capable of building v3.5 projects, so basically we would only need a v4 solution and tell MSB to target v3.5.

-- Roelof.

2010/3/30 Henry Conceição <henry.c...@gmail.com>

[Krzysztof Koźmic]

What's the status on this?

Do we have .NET runtime/SDK on the build server?
Do we have build configuration for .NET 4 in place?
Is anyone doing anything about it?

cheers,
Krzysztof

[Krzysztof Kozmic]

you clearly are

-- 

Krzysztof Kozmic

On Friday, 24 August 2012 at 2:57 AM, Lee James wrote:

Is anything happening on anymore?

It's been 2 years and still there is no download on the project pages for a .NET 4 version of Core/Windsor.

Or have I missed something obvious somewhere?

Lee

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/castle-project-devel/-/TdJnuQDF-1MJ.

[Mauricio Scheffer]

Binaries for .NET 4 have been available since Windsor 2.5 on Sourceforge (  http://sourceforge.net/projects/castleproject/files/Windsor/  ) and NuGet (  https://nuget.org/packages/Castle.Windsor  ).

BTW since .NET is mostly backwards compatible, you can use DLLs compiled for previous versions of .NET just fine.

Cheers

Mauricio