The question I asked on MSBuild forum is here http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/0275d081-d6c6-41f6-a463-82a1b3fb890d/
On Jun 7, 10:34 am, Hadi Eskandari <[email protected]> wrote: > Hello, > > I've been working to add Silverlight builds for Windsor, like we have > it for Dynamic Proxy and Core library. > > I was wondering if it was possible to use one single solution to have > different kind of projects built. Basically we have: > > .NET 3.5 Build > .NET 4.0 Build > Silverlight 3.0 Build > Silverlight 4.0 Build > > Code changes are already handled by build constants. What we need is a > way to handle Assembly References between Silverlight and .NET (e.g. > System.Core) as well as other property settings specific for > Silverlight / .NET. > > I asked in MSBuild form and there is a way to do this as I suspected > but required hacking .csproj files. > > So it all boils down to this question: Should we use two separate > Solution files (like Castle.Core) to build .NET / Silverlight projects > and use file links in Silverlight projects, or use one single solution > file and modify the .csproj file? > > Thanks for your thoughts. > > Best Regards, > Hadi -- 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.
