Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX


eXtreme .NET: Practice Your XP with a Fictional Case Study : Page 4

Here's a perfect chance to be the proverbial 'fly on the wall' as you listen in on a team's efforts to use XP (eXtreme Programming) techniques to improve the way they deliver software.

Exploring Cruise Control .NET (continued)
Panic Pete: How are you guys getting on?

Skeptic Sue: Pretty good, actually.

eXtreme Eddie: Yah, we've got a simple Cruise Control script running and rebuilding the application every 60 seconds.

Panic Pete: Can I see the build results? Are they available online somewhere?

eXtreme Eddie: Not yet, but we should look at doing that next.

Skeptic Sue: OK.

Panic Pete: Cool!

Deepak looks over at the group.

.NET Deepak: Pete! Are you going to help me with this menu control or what?

Panic Pete: Yah, I'll be right there.

Pete goes back to working with Deepak, leaving Sue and Eddie to carry on setting up Cruise Control.

Skeptic Sue: How do we set this up to display results in a browser?

eXtreme Eddie: I think we need to somehow get IIS to use the Web folder in our Cruise Control folder.

Skeptic Sue: I know how to do that. Go to Control Panel and in the Admin Tools folder, open the Internet Information Services application.

eXtreme Eddie: OK.

Skeptic Sue: Now, expand the local computer folders, expand the Web site's folder and right-click on the Default Web Site icon. In that popup menu, select "New" and then "Virtual Directory."

eXtreme Eddie: There's a wizard for this. You've got to love those guys at Microsoft; there are wizards for everything!

Skeptic Sue: We'll need to set an alias for the virtual directory.

eXtreme Eddie: How about CCNET?

Skeptic Sue: Sure, that'll do. Then browse to the C:\Projects\SportSPeak\CruiseControl.NET\Web folder to use as the virtual directory.

eXtreme Eddie: OK, what about access permissions?

Skeptic Sue: The default ones are fine; we only need to read and run scripts.

eXtreme Eddie: Great. That's it? Hmmm. Seems too easy! Let's see what the page looks like.

Eddie opens a browser and navigates to http://localhost/CCNET. The page comes up with: Server Error Can't Find Log Directory.

Skeptic Sue: (Frustrated.) It doesn't work.

eXtreme Eddie: Maybe we need to publish the build results to a log for the Web application to read.

Skeptic Sue: OK, that makes sense. I guess that is another section in the config file.

Sue and Eddie browse the online Help for a few minutes before finding that they need a Publishers element in their ccnet.config file. They add a section to the file after the build element:

<publishers> <xmllogger> <logDir> C:\Projects\SportSPeak\CruiseControl.NET\web\log </logDir> </xmllogger> </publishers>

eXtreme Eddie: Let's run Cruise Control again and check that the file is being created.

They run ccnet.exe from the command line again and check that a file is created in the log's folder.

Skeptic Sue: That looks good. Does the Web app work now?

Sue refreshes the browser but the same server error appears.

Skeptic Sue: Drat.

eXtreme Eddie: Maybe we need to tell the Web application where to look for this log file?

Skeptic Sue: Let's look in the Web.config file and see if it's in there.

eXtreme Eddie: Yes! Look in the appSettings element. If there is a logdir key, we should change that to the path of the log file we just created.

Skeptic Sue: Well spotted!

Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date