7ee4e5302a
- New CAMTParser project: namespace-agnostic parser for camt.052/053/054 producing a statement/entry model aligned with the banking columns (account, amount, debit/credit, dates, counterparty, references, remittance). - BankingService now auto-detects the upload format (XML→CAMT, else MT940) and maps either into the same fds__tt__bankingtransactions DataTable, so the bam/up handler transparently accepts both. - Frontend (fis.bam.de.js) upload field now advertises accept for both MT940 (.sta/.mt940/.txt) and CAMT (.xml/.camt). - Tests (+14, 151 total): CamtParserTests cover parsing (credit/debit, namespace-version agnostic, reversals), detection, and failure/edge inputs (empty, invalid XML, non-CAMT); BankingDualFormatTests verify CAMT and MT940 both land in the same DataTable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
51 lines
2.3 KiB
XML
51 lines
2.3 KiB
XML
<Solution>
|
|
<Configurations>
|
|
<BuildType Name="db-dev.processweb.de" />
|
|
<BuildType Name="Debug" />
|
|
<BuildType Name="Release" />
|
|
<BuildType Name="server02.processweb.de" />
|
|
<Platform Name="Any CPU" />
|
|
<Platform Name="x64" />
|
|
<Platform Name="x86" />
|
|
</Configurations>
|
|
<Project Path="../../WebProjectComponents/MT940Parser/MT940Parser/MT940Parser.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|Any CPU" Project="Debug" />
|
|
<BuildType Solution="server02.processweb.de|Any CPU" Project="Debug" />
|
|
</Project>
|
|
<Project Path="CAMTParser/CAMTParser.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Debug" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="Fuchs.Tests/Fuchs.Tests.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Debug" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="Fuchs/Fuchs.csproj" />
|
|
<Project Path="Fuchs_DataService/Fuchs_DataService.csproj" />
|
|
<Project Path="MFR_RESTClient/MFR_RESTClient.csproj" />
|
|
<Project Path="OCORE/OCORE/OCORE.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Release" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="OCORE/OCORETests/OCORETests.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Release" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="OCORE_Charting/OCORE_Charting.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Release" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="OCORE_web/OCORE_web/OCORE_web.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Release" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="OCORE_web/OCORE_webTests/OCORE_webTests.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Release" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
<Project Path="OCORE_web_pdf/OCORE_web_pdf.csproj">
|
|
<BuildType Solution="db-dev.processweb.de|*" Project="Release" />
|
|
<BuildType Solution="server02.processweb.de|*" Project="Debug" />
|
|
</Project>
|
|
</Solution>
|