Sourcecode: usage of shared Projects instead of folders "shared" across products
kindly ask you to use unique shared classes in a shared project (VS supports these type of "Shared Project") instead of distribution of "shares" folders in Projects for each Product.
The current usage causes differences on sourcecode level (see "WinApiNative.cs" in Project Common and FileServer - Version 2016 R1)
It's a lot of effort to merge your sources across your products to one modified project on customer site (e.g. localize the messages)
Unfortunately, we can’t use “Shared Projects” – these are only supported in Visual Studio 2015, while we still have to support Visual Studio 2008 as well.
However, we will get rid of those folders (and of duplicate WinApiNative.cs as well) in one of the next releases by moving their content into other assemblies and referencing the shared classes using the InternalsVisibleTo mechanism.
Update: These changes have been released with 2016 R3: http://www.rebex.net/sftp.net/history.aspx#2016R3