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

Reply via email to