1. cool. 2. well, this is checking it out - true test of fire ;) 3. yeap - we'll need to integrate ST into the CI process once we know it works.
We'll need to rely on it to keep all our solutions in sync. We have .NET 3.5 and SL3 for now (Mono builds from .NET solutions) but we need to start builds for .NET 4 and SL4 and also version of Windsor for compact framework is highly requested on UserVoice so I think we need to integrate ST into our process ASAP. Krzysztof On 8 Kwi, 09:17, Julian Birch <[email protected]> wrote: > It does: it just ignores them and copies them through. ST isn't live > atm: it's still on my github. There's also a patch to the targets > file to make it work. Anyway, I need someone to check it out and then > I need to clean it up a bit. > > So, yes, what's in trunk is a manual solution. And, tbh, it isn't > tracking the main solution at all from what I can see. > > J > > On Thursday, April 8, 2010, Krzysztof Koźmic (2) <[email protected]> wrote: > > > ok, I see. > > > Did we create the .sl project manually or with Solution Transform? > > > We'll need ST to keep them in sync - work on .NET .sln and on the > > build server > > generate silverlight version of it, and build silverlight binaries > > from that. > > > Julian - will ST handle custom tasks in .csproj files? > > > Krzysztof > > > On 8 Kwi, 08:57, John Simons <[email protected]> wrote: > >> That's right, we didn't use them becuase of nant, but now that we use > >> VIsual Studio/MSBuild to build our projects, I assume we have to use > >> specific versions for each compile. > > >> Cheers > >> John > > >> On Apr 8, 4:43 pm, Krzysztof Ko 1/4 mic (2) <[email protected]> wrote: > > >> > do we even use the SL specific .sln and .csproj files? > >> > I though we weren't, but perhaps it was only in NAnt times. > > >> > Krzysztof > > >> > On 7 Kwi, 23:28, Julian Birch <[email protected]> wrote: > > >> > > Tweaking for Silverlight is a bit tricky, yes... :) > > >> > > On Wednesday, April 7, 2010, John Simons <[email protected]> > >> > > wrote: > >> > > > I think there is more than that. > >> > > > The SL solution/projects for Core are all screwed up, they need > >> > > > fixing. > > >> > > > Cheers > >> > > > John > > >> > > > On Apr 8, 7:18 am, Krzysztof Ko 1/4 mic <[email protected]> > >> > > > wrote: > >> > > >> so the way I understand it in SL mscorlib is being referenced more > >> > > >> than once? > >> > > >> That seems odd provided you generally don't reference mscorlib > >> > > >> explicitly (at least in .NET, perhaps the story is different for > >> > > >> Silverlight) > > >> > > >> On Apr 7, 8:09 am, Roelof Blom <[email protected]> wrote: > > >> > > >> > Now it fails during compile. > > >> > > >> >http://builds.castleproject.org/viewLog.html?buildId=5492&tab=buildRe... > > >> > > >> > <http://builds.castleproject.org/viewLog.html?buildId=5492&tab=buildRe...> > > >> > > >> > On Wed, Apr 7, 2010 at 7:59 AM, Roelof Blom > >> > > >> > <[email protected]> wrote: > >> > > >> > > Added Silverlight build settings inhttp://goo.gl/tXp4 > > >> > > >> > > On Wed, Apr 7, 2010 at 3:19 AM, John Simons > >> > > >> > > <[email protected]>wrote: > > >> > > >> > >> It looks like that the Silverlight build is actually using the > >> > > >> > >> Castle.Core-vs2008.sln. > >> > > >> > >> Shouldn't instead use Castle.Core-SL-vs2008.sln ? > > >> > > >> > >> Roelof, can you shed some light on this? > > >> > > >> > >> Cheers > >> > > >> > >> John > > >> > > >> > >> On Apr 7, 7:53 am, Krzysztof Ko 1/4 mic > >> > > >> > >> <[email protected]> > >> > > >> > >> wrote: > >> > > >> > >> > fails, > >> > > >> > >>http://builds.castleproject.org/viewLog.html?buildId=5490&buildTypeId... > > >> > > >> > >> > looks like the SILVERLIGHT flag is not being set? > > >> > > >> > >> > 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]<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 > >> > > > 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 > > 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.
