> -----Original Message----- [snip] > Anyone have any ideas on how to get around this. When I build I need to > register and unregister on my development machine but it is not absolutely > necessary on the continious integration machine although . It doesn't > have > a problem with the 'ProjectDir', 'OutDir' or 'TargetPath' macros. I'm not > for sure how to approach this. I can delete the pre and post build event > and just run the bat files manually but I really don't want to do that > because I'm lazy. :) [snip]
The SolutionTask is one of my hobby horses. It's been broken since the day before they invented it. I don't use it; I won't use it. <insert me doing my best impression of the Frenchman from Monty Python's "Quest for the Holy Grail" in the direction of SolutionTask. Elderberries and all. /> In the unlikely event that me doing Monty Python doesn't cause you to "Run away! Run away!" from the SolutionTask, I'll tell you that I use CscTask to compile all of our assemblies and maintain a very simple inclusion list of source as part of each build script, etc. Here's why: In a spurt of optimism about six months ago, I briefly experimented with using xsl and simple string operations to manipulate the sln and csproj files so that the wacky SolutionTask would work on them as Local projects instead of Web projects, because SolutionTask was horribly broken with respect to Web projects. I then decided that it was easier to just convert them all to Local projects instead of Web projects 100% of the time instead... Which is how we develop our web apps now; much nicer than before, so some good did come of it. But then something else in SolutionTask broke for me which is too painful to recall, and I gave up again on the SolutionTask... [Don't even think about trying to use ExecTask to call devenv.exe directly. That's even worse than trying to use SolutionTask, if you can believe it.] The SolutionTask is the one reason that I'm looking forward to MSBuild. Because SolutionTask offends me. ;) NAnt with CscTask does me just fine right now, but I find the whole exercise of trying to reinvent devenv.exe to be wasteful, counterproductive and well, nevermind - I'll keep it professional. :) Of course, I'm emotionally preparing myself to be woefully disappointed by MSBuild (as with any version 1 M$ product). Here are some options. You could: 1. Dive into the NAnt code and implement the unimplemented macro. 2. Strip the offending line(s) out at run time (what effect this will have on build success, I don't know). 3. Switch to using csc to build your assemblies. 4. Ask the NAnt developers to hurry up already. :P In the event that this post wasn't helpful, at least you have my sympathies. And I feel better. I may not even need that extra therapy session this week. Heh. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Draconet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/draconet-users
