System.Data.SQLite

Check-in [a448b4c801]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Improve comments in the CHM building tool.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: a448b4c80191a8995cde104e1467728aa3c28c41
User & Date: mistachkin 2013-09-18 09:00:03.681
Context
2013-09-18
09:10
Make the new error messages in the batch build tool more consistent. check-in: aeadebd327 user: mistachkin tags: trunk
09:00
Improve comments in the CHM building tool. check-in: a448b4c801 user: mistachkin tags: trunk
08:18
Document the changes from the original NDoc3 source files. check-in: 62f517f4a6 user: mistachkin tags: trunk
Changes
Unified Diff Ignore Whitespace Patch
Changes to Doc/buildChm.tcl.
︙︙
41
42
43
44
45
46
47
48
49
50


51
52
53
54
55
56
57

  }
  return ""
}

#
# HACK: Copy our local [fixed] copy of the MSDN documenter assembly into the
#       installed location of NDoc3, if necessary.  Actually copying the file
#       will require elevated administrator privileges; otherwise, it would
#       fail.  Any errors encountered while copying the file are reported via
#       the console; however, they will not halt processing.


#
proc copyMsdnDocumenter { sourceDirectory destinationDirectory } {
  set fileNameOnly NDoc3.Documenter.Msdn.dll

  set sourceFileName [file join $sourceDirectory bin $fileNameOnly]
  set destinationFileName [file join $destinationDirectory bin $fileNameOnly]









|

|
>
>








41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

  }
  return ""
}

#
# HACK: Copy our local [fixed] copy of the MSDN documenter assembly into the
#       installed location of NDoc3, if necessary.  Actually copying the file
#       will require elevated administrator privileges; otherwise, it will
#       fail.  Any errors encountered while copying the file are reported via
#       the console; however, they will not halt further processing (i.e. the
#       CHM file will probably still get built, but it may contain some links
#       to built-in types that are blank).
#
proc copyMsdnDocumenter { sourceDirectory destinationDirectory } {
  set fileNameOnly NDoc3.Documenter.Msdn.dll

  set sourceFileName [file join $sourceDirectory bin $fileNameOnly]
  set destinationFileName [file join $destinationDirectory bin $fileNameOnly]
︙︙