Johann MacDonagh wrote: > Is anyone opposed to me replacing */* in the .csproj files to a list > of actual files? There's really only one reason: > > Compatibility with MonoDevelop. MonoDevelop can open the .sln and > .csproj files just fine, but chokes on the wildcard file specifiers > (it says that the project has one file, and it's called *). > MonoDevelop is still able to build the project just fine, it's just > not possible to see and edit files. > It makes sure that everything is kept up to date in the .cproj, since most of us use Nant. But if there are no obligations then I suppose so (as long as it is guaranteed to work under Linux). I for one would have no issues with it. > I'm not sure if most developers use text editors for developing, in > which case the wild card specifiers make it easier. If most people are > using IDE's then it can take care of adding the files to the project > file. > > Also, should we focus primarily on MSBuild support and remove the Nant > support? From what I've read on the Mono ML's, Nant development seems > stunted, while MSBuild is doing great. Having just MSBuild files (with > individual file specifiers rather than wildcards), gives us the best > compatibility and only a single file to edit when making changes. > Interesting, and disappointing. I have grown rather fond of Nant. Back in the day (Okay, last week) when I decided to write a meta-builder (a la qmake) I thought I might do it using Yaml. SharpOS is going to need it's one build language one day: why don't I just make a full-blown builder that uses Yaml: It's a long term idea and probably won't be around till ms 0.0.4 or so, but Yaml is SOOO much nicer to edit than XML. And I could (try) make a converter for it, which may not be necessary in itself (we could just tack it onto the end of the MSBuild process).
We could then throw in our own custom steps such as buildkeys and such goodness. If we do make the transition to MSBuild, guys, try to make your compilers emit VS compliant console messages: http://blogs.msdn.com/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx It shouldn't be too hard: luckily for darxkies this excludes him :). And then we should add our own MSBuild tasks and get squigglies in our keymaps (does mono-develop have those?). > Johann > -- Jonathan Dickinson ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
