Reported by michelpons, 3 years ago.

Using commit 130 build of TLB/PIA distribution leads to warnings: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(234 ,5): warning MSB8065: Custom build for item "1-1-0.rc" succeeded, but specified output "c:\users\cto\documents\tlb-pia\ cape-open idl\1-1-0\1-1-0\1-1-0.res" has not been created. This may cause incremental build to work incorrectly. [C:\Us ers\CTO\Documents\TLB-PIA\CAPE-OPEN IDL\1-1-0\1-1-0.vcxproj] C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(234 ,5): warning MSB8065: Custom build for item "1-0-0.rc" succeeded, but specified output "c:\users\cto\documents\tlb-pia\ cape-open idl\1-0-0\1-0-0\1-0-0.res" has not been created. This may cause incremental build to work incorrectly. [C:\Us ers\CTO\Documents\TLB-PIA\CAPE-OPEN IDL\1-0-0\1-0-0.vcxproj] Are these warnings to be taken into consideration?

Reported by michelpons, 3 years ago.

There is no TRUNK folder at the root of the repository. Instead there are a number of folders containing various parts of the code used to build the CAPE-OPEN TLB/PIA distribution together with a "Tags" folder. There should be a "Trunk" folder at the same level as the "Tags" folder. That would make the repository structure in accordance with the best practice guidelines for a SVN-based repository.

Reported by jasper, 3 years ago.

The .NET SDK is harder and harder to obtain - does not ship out with VS2019 anymore, and the online downloads is 7.1A (not 7.0A as the scripts require).

The two tools needed from there are now part of the repo.