Other than Mono we also have .NET 4 (and SL4 soon).
Can we setup .NET 4 builds ?
On 2010-04-13 01:03, Henry Conceição wrote:
About mono and xbuild:
http://groups.google.com/group/castle-project-devel/msg/6d10135332287a32
Cheers,
Henry Conceição
2010/4/12 John Simons<[email protected]>:
Here is the error we getting:
http://builds.castleproject.org/viewLog.html?tab=buildLog&buildTypeId=bt21&buildId=5371
when trying to use xbuild.
There seems to be also a lot of projects still configured to build
with nant for mono + svn!
Cheers
John
On Apr 13, 8:50 am, John Simons<[email protected]> wrote:
Right now the reason builds are failing is because the agent is
disconnected:http://builds.castleproject.org/agents.html?unregistered=true
But before that i think it was because we are not using nant and
instead are using msbuild.
if we get a build agent with mono on windows.
What's wrong with using the build agent we already have for .net3.5?
All we have to do is install mono for windows on that machine :)
Cheers
John
On Apr 13, 8:07 am, Krzysztof Koźmic<[email protected]>
wrote:
if we get a build agent with mono on windows.
Why do mono builds fail on Linux btw?
is that because of MsBuild?
W dniu 12 kwietnia 2010 23:20 użytkownik John Simons
<[email protected]> napisał:
How about mono builds?
Which btw have been broken for the last 2 mths!
I think mono builds would work fine if we do it in windows instead and
this way at least we have a mono build that works and we are able to
debug if required, thoughts?
Cheers
John
On Apr 12, 11:58 pm, Krzysztof Koźmic (2)<[email protected]> wrote:
ok, as long as it works I don't really care.
What about .NET 4 and SL 4 support. Can we start doing builds for
these please?
And can we fix SL3 build (migrate it to multitargetting if needed).
Do all committers have access to VS2010?
For the beginning there should be 90days trial available so that we
get 3 months before we upgrade.
Krzysztof
On 12 Kwi, 15:33, Roelof Blom<[email protected]> wrote:
Yes, you can make assembly references conditional. It looks a bit weird in
the VSNET UI though, you'll have multiple occurences of the same assembly in
the references list, with a small yellow exclamation mark next to it.
It works correctly though.
Here's some good info on it:http://goo.gl/JzFRhttp://goo.gl/oCyZ
-- Roelof.
2010/4/12 Krzysztof Ko 1/4 mic (2)<[email protected]>
would multitargetting be able to pick up different versions of
dependencies from different subfolders?
like:
..\tools\net-35\nunit.dll
..\tools\sl-30\nunit.dll
On 12 Kwi, 10:16, John Simons<[email protected]> wrote:
Roelof,
My wish is satisfied with MSBuild multitargetting :)
Very nice read:
http://msdn.microsoft.com/en-us/library/ee395432%28v=VS.100%29.aspx
My only concern is that if we go down this path, we basically saying
that we only support VS2010 from now on, which btw is not a problem
for me ;)
Cheers
John
On Apr 12, 6:02 pm, Roelof Blom<[email protected]> wrote:
I could be way off, but IMHO the multi-targeting support in MSBuild 4.0
is
able create binaries for different platforms from a single set of
project
files.
So contrary to John's wish I would love to see only one solution for
each
project. More sln/csproj means more work, even if using a tool, and it
will
clutter the root folder of each project even more than today.
On Mon, Apr 12, 2010 at 8:20 AM, Julian Birch<[email protected]
wrote:
It's basically the same as the assemblyinfo.cs issue: we exclude
because it would complicate source control. The only problem is,
Roelof's code to auto-generate them relies on there being a solution
in the first place, which doesn't apply in this case.
I would love it if we could come up with a better solution to this
problem. But at the moment all I can think of as an alternative is
complex check-ins which keep all the solutions up to date. And then
you get problems if someone modifies two solutions in different
ways...
J
On Sunday, April 11, 2010, John Simons<[email protected]>
wrote:
Julian,
What do you mean by "-SL3 and other solutions are generated by the
build" ?
Regarding solution + project files, I would like to see all our
projects to have a solution and project files for:
- VS2008
- VS2010
- VS2010 + SL4
- VS2008 + SL3
This makes it easier for anyone to pop the solution open and work
on
it.
No "run this before" or "sorry we don't have that"!
Cheers
John
On Apr 12, 1:15 am, Julian Birch<[email protected]> wrote:
Hi, sorry to make it more clear:
- We keep a master sln and csproj file (maybe two) called
-vs2008 or
-vs2010.
- -SL3 and other solutions are generated by the build.
That's basically how Solution Transform works: have a master
project and
all
the others are generated from it. This keeps synchronization
costs to a
minimum.
As far as your moq problems go, though, I think you may need to
approach
it
a different way. Is it possible to run WP7 code hosted within
ordinary
.NET
code? That'd solve the problem (ish).
J
On 11 April 2010 16:04, Michael Sync<[email protected]> wrote:
Hi Julian,
Why do you want to remove sln and csproj files? How shall we
open the
project in Visual Studio?
Add cmd file to generate alternative projects.
I'm not very sure on this. What kind of projects that you want
to
generate
from console?
Thanks and Best Regards,
Michael Sync
Don't go the way life takes you.
Take life the way you go
http://michaelsync.net
On Sun, Apr 11, 2010 at 9:49 PM, Julian Birch<
[email protected]
wrote:
Krzysztof has checked out the new SL build, and has identified
the
following tasks once I've got my new machine:
- Remove superfluous SLN/CSPROJ files (me)
- Standardize naming. (-SL to -SL3, others???) (me)
- Add cmd file to generate alternative projects. (me)
- Get SL3 on CI server using msbuild integration (Krzysztof)
Anything else anyone can think of before we switch over?
J
--
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]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<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]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<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]<castle-project-devel%[email protected]>
<castle-project-devel%[email protected]<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
...
read more>>
--
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.
