Hey Brant, Please see my comments inline below.
----- Original Message ----- > Scott, I have a fix for this problem as well as some other issues I found. > I want to do some more testing but it looks good so far. Here are the > issues I have fixed. Great! > > 1. It was generating <resgen> tags for resources instead of <resource> file > sets. > > 2. There was an issue with a regular expression in one of the parsing > algorithms. > > 3. It wasn't correctly handling VB Project Guids Cool. This is great. > > I have found another issue which I don't have a patch for (yet) > > 1. It seems if you define some configurations at the solution level VS > doesn't automatically apply those down to each project. > > Example: The standard configurations for VS are "Debug" and "Release", but > if you define another one like say "Test" Slingshot gets confused expecting > to find that configuration in each project file. I think the solution maps the solution config name to a project config name if it not different. > > I have a work around for this in the code (it won't crash now). > > 2. It seems that VS doesn't generate all of the proper imports (I find > System.Xml.dll) is especially troublesome. I haven't narrowed it down yet, > but VS will compile the applications but vbc compiler rightly complains. I > have looked through the project files and the imports are infact missing. I > suspect it is a compiler setting on vbc that I need to look for. > > Anyway, I should have my stuff fixed next week. Should I just send you the > code? Yes, feel free to send the code to the list, or me specifically. > > The next thing I am going to look into is the SlingShot Task for NAnt. What > I am trying to do is to have one master .build file that generates seperate > .build files using Slingshot during the build. Is this the common approach > for semi-large projects (500K lines of code/100+ project files)? Yeah, but you may want to do this the first time, and cache, or store the build files, if the corresponding project file hasn't changed. There was also a discussion about the slingshot task requiring some configuration for each project specifically, to work well. Maybe with some of your changes you will find that the default output from a slingshot run on your project files is fine, but you may want to specify other info for your build file that isn't readily available in the project file. You could always add extra, user defined, info in the project file that you could consume in slingshot task to help out. I can add more info if you need me to. The archives should be able to shed more light on this. HTH, Scott ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
