RE: [nant-dev] Building and deploying applications with Nant
Hi Scott, The following is an example of a build that I perform: !-- Core infrastructure components -- target name=level1 csc target=library output=Core.dll sources includes name=*.cs/ /sources /csc ... other base level components /target !-- Business Objects -- target name=level2 depends=level1 csc target=library output=customer.dll sources includes name=*.cs/ /sources /csc /target !-- Web Services -- target name=level3 depends=level2 csc target=library output=customerWS.dll sources includes name=*.cs/ /sources /csc /target !-- Web Pages -- target name=level4 depends=level3 csc target=library output=businessportal.dll sources includes name=*.cs/ /sources /csc /target In this example I have a core.dll, customer.dll, customerWS.dll and a businessportal.dll. If something in businessportal.dll changes then as far as I know a complete build needs to be performed. However in theory only the businessportal.dll should need to be recompiled. This means that the entire site has to be recompiled (because I am using strong names) and more importantly redeployed. The scale of the problem becomes a lot larger when you have deployments over multiple machines. Then the deployment scenario for a small change becomes a lot more horrendous. Down time is a critical factor in our business and if we don't achieve a certain level of uptime then we violate or contractual obligations. It would be good to hear from some other people to see whether they are experiencing the same types of problems. Thanks Ben -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED]] Sent: Friday, 17 January 2003 7:15 PM To: Ben Singh; [EMAIL PROTECTED] Subject: Re: [nant-dev] Building and deploying applications with Nant Can you send us an example of a real-world data centre situation where you need to do dependency related stuff. I've been thinking about adding a uptodate conditional task. It would allow you to only do certain things if something was not up to date. Kinda like this: uptodate sourcefile=test.cs updatedfile=test.dll ... stuff to do call target=build/ /uptodate It would probably work very similar, but a little simpler than the ant uptodate task. http://jakarta.apache.org/ant/manual/CoreTasks/uptodate.html - Original Message - From: Ben Singh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 16, 2003 9:20 PM Subject: [nant-dev] Building and deploying applications with Nant Hi, I was wondering whether I could get some feedback about the scenarios people are using Nant for. The current scenario I am faced with is a data centre operation with high availability requirements. My problem is that making even minor changes requires a full build with Nant and subsequently a full deployment which results in down time. Surely there has to be a better way. My previous posting on how to create a patch went unanswered. I suspect this is a very difficult question to answer and that Nant is probably not designed to handle what I think is a pretty common scenario. If I'm totally wrong someone please shoot me down. Ben --- 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 ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NUnit Error With NAnt...
Scott, Yes, the fork option was removed and made the default(sort of). Now (as of oct I think) nunit2 tests create a new appdomain to execute in. Indeed, this should be how it always works, now (assuming nobody undid the changes I made last time to it g). It's worthwhile to notice that this is essentially what NUnit 2.0 own console and GUI drivers do, too. -- Tomas Restrepo [EMAIL PROTECTED] --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NUnit Error With NAnt...
True. It took me a little while to see this. But now I understand things much better. And I think I better understand where some of the issues are coming from. In addition to the changes you made, I think we need to set the environment working/current directory to the nunit2 basedir. This will allow tests to open files and work with IO related operations as they might expect. Then after the task finishes, we can set the current directory back. This is a process level change, so we kinda have to be careful. - Original Message - From: Tomas Restrepo [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, January 19, 2003 5:41 PM Subject: Re: [nant-dev] NUnit Error With NAnt... Scott, Yes, the fork option was removed and made the default(sort of). Now (as of oct I think) nunit2 tests create a new appdomain to execute in. Indeed, this should be how it always works, now (assuming nobody undid the changes I made last time to it g). It's worthwhile to notice that this is essentially what NUnit 2.0 own console and GUI drivers do, too. -- Tomas Restrepo [EMAIL PROTECTED] --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NUnit Error With NAnt...
Yeah, I'm there with you, maybe some documentation would solve this problem. Also, maybe this isn't the optimal solution, but we could add an option to change the current directory if you want to have the current env dir set. As long as we differ from the NUnit console/gui, there will be confusion and complaints. - Original Message - From: Tomas Restrepo [EMAIL PROTECTED] To: Scott Hernandez [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, January 19, 2003 6:55 PM Subject: Re: [nant-dev] NUnit Error With NAnt... Hi Scott, True. It took me a little while to see this. But now I understand things much better. And I think I better understand where some of the issues are coming from. In addition to the changes you made, I think we need to set the environment working/current directory to the nunit2 basedir. This will allow tests to open files and work with IO related operations as they might expect. Then after the task finishes, we can set the current directory back. This is a process level change, so we kinda have to be careful. Actually, I struggled with this while making my changes... the original NUnit2.0 code does this, I think, but I believe this is fundamentally wrong, and will actually end up hiding latent bugs. Let me put it this way: Any code that relies on the CurrentDir to be set to a specific value at application startup is fundamentally broken, and likely reveals the developer's not familiar with the real usage of the CurrentDir setting. If tests need to ensure the code has a known current directory before invoking the tested methods, they should explicitly set it themselves or on the tests StartUp() routine. -- Tomas Restrepo [EMAIL PROTECTED] --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers