The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

aflores57 (3) [Avatar] Offline
#1
Perhaps you can use this thread to consolidate this type of information:

4.4 Continuous Integration with TeamCity, third paragraph (pdf page #10smilie
reads:
It has a very neat future (should be: feature) that lets you forget the manual build technique we discussed
earlier in this chapter. It verifies (add: "that the") code compiles and passes unit tests before committing your
source code into the repository. Look at the Figure 4.11 to better understand the difference.
craig.berntson (25) [Avatar] Offline
#2
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Thanks. I'll be correcting that in the near future. Keep in mind that the book has not yet been copy edited.
ifolarin (3) [Avatar] Offline
#3
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Page 49, last paragraph

Conflicts occur rather infrequently in a well organized team. But when they do occur you
have to resolve them manually. A clean code base is very important for a frictionless CI
process. TortoiseSVN les (should be lets) you very easily resolve the conflicts with a Merge dialog (Figure
2.20).
craig.berntson (25) [Avatar] Offline
#4
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Thanks. The manuscript is currently going through copy edit. These things will get resolved there.
ifolarin (3) [Avatar] Offline
#5
Re: Typos, Corrections and Related Suggestions (Any Chapter)
And here is some more...
Pg 67, Section 2.5 Summary, paragraph before the last

If you are planning to use Microsoft Team Foundation Server, which in his 2010 Version is
a big milestone, especially for smaller teams, you should seriously consider using TFS Source
Control to host the changes in your source code. TFS 2010 is affordable and is keeping up in
means of features with the best Open Source revision control systems.
michielovereem (1) [Avatar] Offline
#6
Re: Typos, Corrections and Related Suggestions (Any Chapter)
I have found some typos:

start of page 26 "we do this eliminate all the unnecessary noise"

on page 41, you mention "Framework, P001 and P002" with respect to figure 2.9. But the figure doesn't show P001 or P002

paragraph 5.4.3 "TFS 2010 very extensible in regards to notificaton."
lvmisooners (4) [Avatar] Offline
#7
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Hello,

On page 68 (first page of chapter 3), there is a sentence:

When you press this button you are start a build process that
leads to working software.

"start" should be "starting" OR "are" should be removed.

Enjoying the book so far. Thanks!
lvmisooners (4) [Avatar] Offline
#8
Re: Typos, Corrections and Related Suggestions (Any Chapter)
on page 81, below figure 3.7, you have

These taks let us archive our software, give the archive a unique name,
and send it over using email.

I believe "taks" was meant to be tasks
lvmisooners (4) [Avatar] Offline
#9
Re: Typos, Corrections and Related Suggestions (Any Chapter)
on page 93, section 3.5, second paragraph:

Plain text makes it easy to check and change the things are done.

maybe add "that" before "are" or change to "change how things are done"
lvmisooners (4) [Avatar] Offline
#10
Re: Typos, Corrections and Related Suggestions (Any Chapter)
section 3.5 2nd paragraph:

Sooner or later you encounter a problem you will have to deal by extending you tool.

"you" should be "your"
jimm3rs (12) [Avatar] Offline
#11
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Page 27 of the PDF file, Figure 1.17 has Class1.cs shown. Just above the figure there is text:

17. Delete the default Class1.cs file.
jimm3rs (12) [Avatar] Offline
#12
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Figure 1.12: left tree structure has directory named doc, right does not. Right has config and tools directories, left does not. Looks inconsistent.
jimm3rs (12) [Avatar] Offline
#13
Re: Typos, Corrections and Related Suggestions (Any Chapter)
2.2.1 Installing VisualSVN Server:

...
"It will be difficult to read the content of the files you host on the source control server if you are not authorized to do this"
...

The above sentence is in the part discussing SSL: how authorization is connected to encrypting traffic?
jimm3rs (12) [Avatar] Offline
#14
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Figure 2.7: tip "Server name/IP" should include port too.
jimm3rs (12) [Avatar] Offline
#15
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Text under Figure 2.9: "Look closely at the URLs shown in Figures 2.8 and 2.9. Do you see the difference? With SVN you can pull only a given directory. You don't have to work at the repository level."

In fact both URLs mentioned point to repositories.
jimm3rs (12) [Avatar] Offline
#16
Re: Typos, Corrections and Related Suggestions (Any Chapter)
3.2 The Microsoft worker MSBuild

...
"All of the subfolders v2.0, v.3.5, and v4.0 contain MSBuild.exe"
...

On my box directory C:WindowsMicrosoft.NETFrameworkv4.0.30319 does not contain MSBuild.exe, while directories v2.0.50727 and v3.5 do contain it.
jimm3rs (12) [Avatar] Offline
#17
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Text below figure 2.38:

"Repeat these steps for the WebCalc and WinCalc solutions."

WebCalc and WinCalc are in fact projects, solutions are named WebCalculator and WindowsCalculator in the beginning of the book.
jimm3rs (12) [Avatar] Offline
#18
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Figure 2.36 text mentions server named tfs1 but this information is not on the picture itself.
Moreover, on Figure 2.32 the Path field contains "tfs".
jimm3rs (12) [Avatar] Offline
#19
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Listing 3.5 mentions Microsoft.VisualBasic.targets while demo project is in C#. Is that correct?
jimm3rs (12) [Avatar] Offline
#20
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Listing 3.6 MSBuild task to read assembly version from AssemblyInfo.cs file:

The class inherits from Microsoft.Build.Utilities.Task. This means that the Microsoft.Build.Framework.dll and Microsoft.Build.Utilities.dll should be referenced from the project. This is not mentioned.
jimm3rs (12) [Avatar] Offline
#21
Re: Typos, Corrections and Related Suggestions (Any Chapter)
3.5 Summary says the following:
"No matter where the CI process lives, it should live alone as most of the time it runs on an unmanaged process that works automatically."

Provided that the "unmanaged" in .NET community has special meaning wouldn't it be better to name it unattended instead?
TheDoctor (1) [Avatar] Offline
#22
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Based on Last Update 07/05/2010...
There is a intermix of the solution name "WindowsCalculator and WinCalculator".
Chapter 1 refers to "WindowsCalculator" while chapter 2 refers to "WinCalculator"

Section 1.2.4. Calculators
24. Name the solution WindowsCalculator

Figure 1.20

Message was edited by:
TheDoctor
selkind (1) [Avatar] Offline
#23
Re: Typos, Corrections and Related Suggestions (Any Chapter)
In chapter 4, page 100 in the PDF, the link to the ThoughtWorks CI tool comparison is broken, it gets forwarded to a SourceForge site where I could not immediately find a replacement. (http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix). I have not been able to find a replacement...
nuggetboy (6) [Avatar] Offline
#24
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Please see the apparent error in the thread here:
http://www.manning-sandbox.com/thread.jspa?threadID=39175

See pp71-72. The code listing as well as the sidebar, "Passing parameters to MSBuild scripts," makes reference to the condition '$(Delete)'=='', however shouldn't this be the condition '$(Debug)'==''? There is no context for a "Delete" property.

The whole property should be:
<Debug Condition="'$(Debug)'==''">true</Debug>
nuggetboy (6) [Avatar] Offline
#25
Re: Typos, Corrections and Related Suggestions (Any Chapter)
The whole property should be:
<Debug Condition="'$(Debug)'==''">true</Debug>
nuggetboy (6) [Avatar] Offline
#26
Re: Typos, Corrections and Related Suggestions (Any Chapter)
p87, the XML open element should be "MSBuildCommunityTasksPath", not the singular "MSBuildCommunityTaskPath".
nuggetboy (6) [Avatar] Offline
#27
Re: Typos, Corrections and Related Suggestions (Any Chapter)
Same page, the element </ItemGroup> is never opened.