You don't *have* to use different .csprojs, it's just a possibility. I happen to like the fact that this allows you to customize the build for that platform inside VS.
On Mon, Dec 21, 2009 at 12:28 PM, Julian Birch <[email protected]>wrote: > 2009/12/21 Roelof Blom [email protected] > > >sln/csproj (references and sources) are 'automatically' in sync with >>> > what's on the disk, >>> Yes that is true, but does it really take that long to keep them in >>> sync? And in my case I use VS to do updates to the source code so >>> everything is in sync anyway. >>> >> It's not hard, it's just friction. >> One more drawback of the current build system is that it picks up every >> .cs file. >> By using .csproj you can more easily partition the build for .NET and >> Silverlight, >> by creating a .csproj for the platform you want to build on. >> >> > I'd actually say this was an advantage of the current build system. > Personally, I dislike the fact that I need a separate csproj file for > silverlight at all. In any event, the #if !SILVERLIGHT directive is pretty > explicit and arguably more workable. > > 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]> > . > 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.
