|FreeImage||2015-01-30||Daniel Kraus||[7a1376] Build FreeImage without OpenMP support.|
|UnitTests||2015-06-25||Daniel Kraus||[3c74c1] Add conditional use of Bovender assembly for un...|
|XLToolbox||2015-06-25||Daniel Kraus||[92a2f4] Use correct WorkbookStorage key for export path.|
|XLToolboxForExcel||2015-06-24||Daniel Kraus||[411feb] Repair project files that were broken by NuGet ...|
|publish||2015-05-25||Daniel Kraus||[79786d] Add utility script to build development installer.|
|.gitignore||2015-01-06||Daniel Kraus||[b7bbf2] Add Doxygen configuration file and ignore the d...|
|Doxyfile||2015-01-06||Daniel Kraus||[b7bbf2] Add Doxygen configuration file and ignore the d...|
|LICENSE-FREEIMAGE.TXT||2015-01-04||Daniel Kraus||[edf412] Add Apache license files.|
|LICENSE-MS-SDK.TXT||2015-01-04||Daniel Kraus||[be3f56] Add Microsoft license information.|
|LICENSE-MS-VSTO.TXT||2015-01-04||Daniel Kraus||[be3f56] Add Microsoft license information.|
|LICENSE.TXT||2015-01-04||Daniel Kraus||[edf412] Add Apache license files.|
|Makefile||2014-07-13||Daniel Kraus||[671fd2] Implement WindowHtmlViewer for license and cred...|
|NG.sln||2015-06-24||Daniel Kraus||[4bf11e] Add project configuration 'Debug (Bovender via ...|
|NOTICE.TXT||2015-03-09||Daniel Kraus||[cc4914] Copy DocumentFormat.OpenXml to output folder.|
|README-DOCS.md||2015-01-06||Daniel Kraus||[b7bbf2] Add Doxygen configuration file and ignore the d...|
|README.md||2015-06-24||Daniel Kraus||[4bf11e] Add project configuration 'Debug (Bovender via ...|
|VERSION||2015-06-25||Daniel Kraus||[c81c0c] Bump version number.|
|common.licenseheader||2015-01-04||Daniel Kraus||[b1ec5f] Add common.licenseheader and symbolic links in ...|
The XL Toolbox NG source code is written in (mostly) C# with Visual Studio
Professional 2013 and target for the .NET framework 4.0.
For more information about this project, see http://xltoolbox.sf.net.
This project uses the Git source code management system. You can find the
repository at https://sf.net/p/xltoolbox/ng-code.
The Visual Studio project files have been hand-edited to use different
sources of the Bovender assembly: In the Debug configuration, the
assembly is referenced locally. In the Release configuration, the
assembly is referenced as a NuGet package. This has the advantage (for
me) that I can make changes to Bovender without having to release a
new NuGet package every time I want to test it in the NG solution.
This is my directory structure:
x:\ Code bovender\ Bovender\ BovenderUnitTests\ xltoolbox\ NG\ XLToolbox\ XLToolboxForExcel\ UnitTest\
The bovender assembly is thus referenced from the XLToolbox project file
(which resides in
If you want to build with Debug configuration, but do not have the
Bovender assembly in the same directory structure as I have, you can
(and should) use the Debug (Bovender via NuGet) configuration.
The sources do of course not include the confidential strong name key (.snk)
file that is needed to sign the binaries. If you want to build the solution
yourself, you have different options:
Clone the Git repository on a *nix file system. The repository
contains symbolic links named "xltb.snk" in the subdirectories that
point to a strong name key file in an unrelated directory
"../private/" that lies outside of the repository. Therefore you would
only need to create such directory and put the strong name key file in
there. For instance:
# make new directory that holds everything and enter it mkdir XLToolbox chdir XLToolbox # clone the repository into `source` git clone git://git.code.sf.net/p/xltoolbox/ng-code source # make directory for strong name key file mkdir private # Then, start Windows and create a new strong name key file # named `xltb.snk` in the `private` directory.
Visual Studio comes with the
sn.exe tool that you can use to create a .snk
file. It is somewhat hidden; you may for example find it in:
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin
In the command window,
cd to this directory and execute:
sn.exe -k xltb.snk move xltb.snk <drive:\path\to\sources_or_private>
Whether you have to move the .snk file to the
private directory or to the
source directory depends on what method you have chosen above. On
Windows-only systems where you will likely not be using symlinks, you need
to copy the .snk file to each and every subdirectory in the source tree.
It should go without saying that you cannot of course mix binaries from the
original distribution with binaries that you build yourself, as they do not
share the same strong name key.
Daniel's XL Toolbox NG Copyright (C) 2014-2015 Daniel Kraus <firstname.lastname@example.org> Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.