Skip to content

Commit 345c791

Browse files
giometrixgiometrix
committed
Added sourcelink
1 parent ae60aee commit 345c791

File tree

1 file changed

+53
-42
lines changed

1 file changed

+53
-42
lines changed

‎src/TableStorage.Abstractions.POCO/TableStorage.Abstractions.POCO.csproj‎

Lines changed: 53 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,55 @@
11
<Project Sdk="Microsoft.NET.Sdk">
22

3-
<PropertyGroup>
4-
<TargetFramework>netstandard2.0</TargetFramework>
5-
<Version>2.7.0.0</Version>
6-
<Authors>Giovanni Galbo</Authors>
7-
<Company>Giovanni Galbo</Company>
8-
<Description>A repository wrapper for Azure Table Storage that uses POCOs (Plain Old CLR Objects) instead of objects that implemeent ITableEntity.
9-
10-
The Azure Storage SDK requires that objects that it works with to implement the ITableEntity interface. This puts us into one of two places that are often not desirable:
11-
12-
You implement the ITableEntity interace, or inherit from TableEntity. This is easy, but now you've got a leaky abstraction, as well as properties that won't make much sense in your domain (e.g. instead of a UserId, you've now got a RowKey, of the wrong type), or you have fields that are out of place, like ETag and Timestamp.
13-
You create DTOs to save to ship data back and forth from the domain to Table Storage. This is a common style, but often is overkill, especially if we're just looking for a simple abstraction on top of Azure Table Storage.
14-
This simple library seeks to take care of the mapping for us, so that you can continue to write your domain objects as POCOs, while still being able to leverage the Azure Storage SDK.
15-
16-
The library will convert simple properties to fields in Azure Table Storage. Complex types will serialize as json.</Description>
17-
<Copyright>© Giovanni Galbo 2020</Copyright>
18-
<PackageLicenseUrl></PackageLicenseUrl>
19-
<PackageProjectUrl>https://github.com/giometrix/TableStorage.Abstractions.POCO</PackageProjectUrl>
20-
<RepositoryUrl>https://github.com/giometrix/TableStorage.Abstractions.POCO</RepositoryUrl>
21-
<PackageTags>table-storage azure-table-storage poco table-entities tableentity</PackageTags>
22-
<PackageReleaseNotes>Bug fix to prevent exceptions when deserializing objects with readonly properties</PackageReleaseNotes>
23-
<GeneratePackageOnBuild>true</GeneratePackageOnBuild>
24-
<PackageLicenseExpression>MIT</PackageLicenseExpression>
25-
<AssemblyVersion>2.6.1.0</AssemblyVersion>
26-
<FileVersion>2.6.1.0</FileVersion>
27-
<PackageIcon>xtensible-x.png</PackageIcon>
28-
<PackageIconUrl />
29-
</PropertyGroup>
30-
31-
<ItemGroup>
32-
<PackageReference Include="TableStorage.Abstractions" Version="3.1.0" />
33-
<PackageReference Include="TableStorage.Abstractions.TableEntityConverters" Version="1.3.0" />
34-
<PackageReference Include="Xtensible.Time.Clock" Version="1.1.0" />
35-
</ItemGroup>
36-
37-
<ItemGroup>
38-
<None Include="xtensible-x.png">
39-
<Pack>True</Pack>
40-
<PackagePath></PackagePath>
41-
</None>
42-
</ItemGroup>
43-
44-
</Project>
3+
<PropertyGroup>
4+
<TargetFramework>netstandard2.0</TargetFramework>
5+
<Version>2.7.1.0</Version>
6+
<Authors>Giovanni Galbo</Authors>
7+
<Company>Giovanni Galbo</Company>
8+
<Description>
9+
A repository wrapper for Azure Table Storage that uses POCOs (Plain Old CLR Objects) instead of objects that implemeent ITableEntity.
10+
11+
The Azure Storage SDK requires that objects that it works with to implement the ITableEntity interface. This puts us into one of two places that are often not desirable:
12+
13+
You implement the ITableEntity interace, or inherit from TableEntity. This is easy, but now you've got a leaky abstraction, as well as properties that won't make much sense in your domain (e.g. instead of a UserId, you've now got a RowKey, of the wrong type), or you have fields that are out of place, like ETag and Timestamp.
14+
You create DTOs to save to ship data back and forth from the domain to Table Storage. This is a common style, but often is overkill, especially if we're just looking for a simple abstraction on top of Azure Table Storage.
15+
This simple library seeks to take care of the mapping for us, so that you can continue to write your domain objects as POCOs, while still being able to leverage the Azure Storage SDK.
16+
17+
The library will convert simple properties to fields in Azure Table Storage. Complex types will serialize as json.
18+
</Description>
19+
<Copyright>© Giovanni Galbo 2020</Copyright>
20+
<PackageLicenseUrl></PackageLicenseUrl>
21+
<PackageProjectUrl>https://github.com/giometrix/TableStorage.Abstractions.POCO</PackageProjectUrl>
22+
<RepositoryUrl>https://github.com/giometrix/TableStorage.Abstractions.POCO</RepositoryUrl>
23+
<PackageTags>table-storage azure-table-storage poco table-entities tableentity</PackageTags>
24+
<PackageReleaseNotes>Added sourcelink</PackageReleaseNotes>
25+
<GeneratePackageOnBuild>true</GeneratePackageOnBuild>
26+
<PackageLicenseExpression>MIT</PackageLicenseExpression>
27+
<PublishRepositoryUrl>true</PublishRepositoryUrl>
28+
<EmbedUntrackedSources>true</EmbedUntrackedSources>
29+
<IncludeSymbols>true</IncludeSymbols>
30+
<SymbolPackageFormat>snupkg</SymbolPackageFormat>
31+
32+
<AssemblyVersion>2.7.1.0</AssemblyVersion>
33+
<FileVersion>2.7.1.0</FileVersion>
34+
<PackageIcon>xtensible-x.png</PackageIcon>
35+
<PackageIconUrl />
36+
</PropertyGroup>
37+
38+
<ItemGroup>
39+
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.0.0">
40+
<PrivateAssets>all</PrivateAssets>
41+
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
42+
</PackageReference>
43+
<PackageReference Include="TableStorage.Abstractions" Version="3.2.2" />
44+
<PackageReference Include="TableStorage.Abstractions.TableEntityConverters" Version="1.3.1" />
45+
<PackageReference Include="Xtensible.Time.Clock" Version="1.1.0" />
46+
</ItemGroup>
47+
48+
<ItemGroup>
49+
<None Include="xtensible-x.png">
50+
<Pack>True</Pack>
51+
<PackagePath></PackagePath>
52+
</None>
53+
</ItemGroup>
54+
55+
</Project>

0 commit comments

Comments
 (0)