I am very strongly AGAINST using more than one solution/project for
projects. Simply because it's just pure overhead and sooner or later
they're bound to go out of sync. We could use a tool like Solution
Transform developed by Julian to generate silverlight projects on the
fly out of .NET projects, but if we can stick to just single solution
that would be best.
Plus we already have customized our .csproj files so I see no problem in
taking it to the next level. They're supposed to be "just" msbuild files
after all.
Krzysztof
On 2010-06-07 16:34, Hadi Eskandari 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.
