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