Dangl.AVACloud.Client.Public 1.7.8

• .NETStandard 2.0

  • Dangl.AVACloud.Client.Shared (>= 1.7.8)

## v1.7.8:
- The Swagger definitions were updated to include better formatted descriptions

## v1.7.5:
- The Swagger definitions for the API specification were updated to be better compatible with third party code generators

## v1.7.4:
- Update **Dangl.GAEB** and **Dangl.AVA.Converter** to be able to import GAEB XML files with an invalid exchange phase (`Award.DP` field)

## v1.7.1:
- Fix startup error that triggered for specific configuration in Azure App Services and prevented the app from starting

## v1.7.0:
- **AVACloud** can now export to ÖNorm 2063
- **AVACloud** can now import and export the Swiss SIA 451 format

## v1.6.2:
- Fixed wrong return type in generated .NET client code
- Include `AvaConversionClient` in client factory in public package

## v1.6.0:
- Introduced support for the German REB DA11 file format. This format is used for quantity takeoff and quantity calculations
- The **Dangl.AVA**, **Dangl.GAEB** and **Dangl.AVA.Converter** dependencies were updated

## v1.5.10:
- Dependencies update for latest bugfixes with GAEB XML import and export

## v1.5.6:
- Dependencies were updated. **Dangl.AVACloud** now supports the overrides introduced with the latest **Dangl.AVA.IO** release for some properties
- The public documentation was updated with information about the unified **Dangl.AVA** project model

## v1.5.4:
- The **Dangl.GAEB** dependency was updated

## v1.5.3:
- The **Dangl.AVA** and **Dangl.AVA.Converter** dependencies were updated to include the latest additions of properties

## v1.5.2:
- All parameters of type `IFormFile` are now checked to ensure their length is greater than zero. Otherwise, the request will return a `400 - Badrequest` status code without hitting the controller

## v1.5.1:
- Added `AvaProjectDtoValidationAttribute` to ensure that invalid AVA Projects sent as parameters lead directly to a 400 - Bad Request response and don't hit the conversion service at all
- Updated **Dangl.GAEB** to `v1.6.7` for latest improvements to deserialize GAEB XML files with missing GAEBInfo declarations

## v1.5.0:
- The **Dangl.AVA** dependencies were updated to `v2.1.0`. This now also includes support for the new destination GAEB phases `SideOffer` and `CostEstimate`
- When sending invalid AVA-projects via the API where elements of type `IElementDto` contain an invalid `ElementTypeDiscriminator` value, an error message is sent as response with the offending value

## v1.4.6:
- The **Dangl.GAEB** module was updated to make importing of malformed GAEB XML files more robust

## v1.4.5:
- GAEB exports now contain a `GAEBInfo.ProgName` to indicate their origin as coming from AVACloud

## v1.4.3:
- Update dependencies for latest bugfixes and performance improvements

## v1.4.3:
- Update dependencies. GAEB files which have no item numbers and no item number schema defined should now get automatically generated item numbers

## v1.4.2:
- Update dependencies

## v1.4.1:
- Fix some issues where the new ASP.NET Core 2.2 InProcess hosting model would sometimes fail to load the OS-dependant `System.Drawing.Common.dll` in Azure App Service environments
- Fixed issue where the Swagger definition contained duplicated enum value

## v1.4.0:
- The **Dangl.AVA** & **Dangl.GAEB** dependencies were updated to the latest version `v2.0.0`
- The server side was upgrade to ASP.NET Core 2.2

## v1.3.3:
- Update of dependencies to fix bugs related to empty tables in some GAEB XML Html long texts

## v1.3.1:
- Exports to GAEB 90 no longer include the branding comment, since this caused problems with some importing applications
- The `DestinationGaebType``for GAEB 2000 Commerce was renamed from `GAEB2000Commerce` to `Gaeb2000Commerce`. The old value may still be used by clients

## v1.3.0:
- The public and internal Swagger endpoints were unified to a single one
- The public client does now also include all operations with AVA models. It uses generated models instead of the **Dangl.AVA.IO** package

## v1.2.4:
- Bugfix: The .NET client had a bug around JSON deserialization of OAuth2 token responses

## v1.2.3:
- Update **Dangl.AVA** dependencies for latest bugfixes

## v1.2.2:
- The Admin Ui Dashboard can now optionally store and display options that were used during conversion processes

## v1.2.1:
- Update **Dangl.AVA.Converter.Excel** and **Dangl.Oenorm** for latest bugfixes and improvements

## v1.2.0:
- **Dangl.AVA** models were updated to indicate properties that are `readonly`. This should make integration with clients more straightforward

## v1.1.2:
- Bugfix where non-schema compliant GAEB XML files with invalid decimal values could not be read

## v1.1.1:
- Bugfix where GAEB 90 exports with very high absolute values for deductions failed

## v1.1.0
- The API now accepts Austrian OENorm 2063 files as input

## v1.0.13:
- Update **Dangl.AVA** dependencies for latest bugfixes

## v1.0.12:
- The app is now published with all dependencies. This results in slightly larger deployment sizes, but makes hosts no longer require to have the correct .NET Core runtime installed

## v1.0.11:
- Update **Dangl.GAEB** && **Dangl.AVA** dependencies for latest bugfixes
- Prettify Admin UI Dashboard
- Update to ASP.NET Core 2.1.3

## v1.0.10:
- Update Admin UI Dashboard to include more statistics

## v1.0.9:
- Update dependencies to be able to read `NoteText` elements from GAEB 2000 commerce exchange phase files

## v1.0.8:
- All `DateTime` Json response objects have now their timezone attached

## v1.0.5:
- Added AVACloud Admin UI Dashboard to monitor service health and metrics
- Added option to normalize file names, so that when files are converted with their full path & filename, only the filename portion is used for the result

## v1.0.4:
- Add support for `GAEBXML_V3_1` destination type

## v1.0.3:
- When supplying an invalid `culture` to endpoints returning Excel, the culture will now default to `en`

## v1.0.2:
- Fix Swagger discriminator propeties not being correctly camelCased in the Swagger definitions

## v1.0.1
- Fix Swagger schema being set to only `http` when first hit by Azure App Service warmup via non-secure http route

## v1.0.0
- Initial Release