Changes between Version 7 and Version 8 of BuildSetup


Ignore:
Timestamp:
Jan 26, 2011, 10:30:58 PM (11 years ago)
Author:
Matthäus Wander
Comment:

update

Legend:

Unmodified
Added
Removed
Modified
  • BuildSetup

    v7 v8  
    44
    55||= Requirement =||= Ticket =||= Implemented =||
    6 || Check for installation prerequisites (.NET 4, C++ runtimes for native DLLs). Propose download link to user. || #8, #159 || yes for .NET, no for C++ ||
     6|| Check for installation prerequisites (.NET 4, C++ runtimes for native DLLs). Propose download link to user. || #8, #159 || yes ||
    77|| After installation of CT2 any pathes (default project file, default project path) should be preconfigured to the installation directory selected by user. || #96 || yes ||
    88|| Use assembly versioning scheme which includes SVN revision number. || || yes ||
    9 || Allow coredevs to configure major/minor CT2 version in central location. || || ||
     9|| Allow coredevs to configure major/minor CT2 version in central location. || || yes ||
    1010|| Upgrade CT2 when installing newer setup file. || #144 || yes ||
    1111|| Remove obsolete files no longer included in new setup versions. || #155 || partly (cleans build directory, but does not purge files from installation directory) ||
    12 || Support inclusion of third-party libraries (e.g. msieve, peers@play, external WPF controls, bouncycastle, NativeCryptography). Let trunk developers decide which version of the library to include. Caveat 1: libs may lack strong-names (may conflict with Software Publisher Certificate signing, see below). Caveat 2: libs may lack versioning scheme (may fail upgrade installation). || #149 || ||
     12|| Support inclusion of third-party libraries (e.g. msieve, peers@play, external WPF controls, bouncycastle, NativeCryptography). Let trunk developers decide which version of the library to include. Caveat 1: libs may lack strong-names (may conflict with Software Publisher Certificate signing, see below). Caveat 2: libs may lack versioning scheme (may fail upgrade installation). || #149 || partly ||
    1313|| Support inclusion of data files outside of assemblies (e.g. statistics data, wordlists, example texts). Data store should be shared, so that multiple plugins can access the same data files. || || partly ||
    1414|| Show Apache license to user during setup. || #148 || yes ||
    15 || Include only one .exe in installation directory. || #150 || ||
    16 || Support running setup as non-admin (may ask for admin privileges if necessary, but catch failures if not granted). || #158 || ||
     15|| Include only one .exe in installation directory. || #150 || yes ||
     16|| Support running setup as non-admin (may ask for admin privileges if necessary, but catch failures if not granted). || #158 || no ||
    1717|| Automatically create nightly builds for website. || || yes ||
    1818|| Send mail if nightly build fails. || || yes ||
    1919|| Allow regular trunk developers without access to CrypWin/AnotherEditor sources to build and debug CT2 with both, Visual Studio and Visual C# Express. || || yes ||
    20 || Support internationalization/localization (I18N/L10N) in setup. Part of bigger task to support I18N in whole CT2. || #127 || ? ||
     20|| Support internationalization/localization (I18N/L10N) in setup. Part of bigger task to support I18N in whole CT2. || #127 || yes ||
    2121
    2222== Nice-to-have Requirements ==
    2323
    2424||= Requirement =||= Ticket =||= Implemented =||
    25 || Support x86 and x64. || #106 || yes ||
     25|| Support x86 and x64. || #106 || yes, x86 build supports both ||
    2626|| Use strong names signing for assemblies. || || yes ||
    2727|| Sign setup with Software Publisher Certificate. || || yes ||
    28 || Bind deployment of project samples to build of plugin, i.e. if plugin is included in build, also include its project samples. If plugin is removed from build, do not install associated project files into sample directory. || #151 || ||
    29 || Support grouping of plugins into setup components. || || ||
     28|| Bind deployment of project samples to build of plugin, i.e. if plugin is included in build, also include its project samples. If plugin is removed from build, do not install associated project files into sample directory. || #151 || partly ||
     29|| Support grouping of plugins into setup components. || || no ||