lsm/PdfPig
1
0
Fork 0
mirror of https://github.com/UglyToad/PdfPig.git synced 2025-07-17 05:29:19 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
00bd285262
PdfPig/src/UglyToad.PdfPig/UglyToad.PdfPig.csproj

67 lines
3.3 KiB
XML
Raw Normal View History

#18 add sourcelink package and changes
2018-11-25 19:44:08 +08:00
<Project Sdk="Microsoft.NET.Sdk">
Move the code from the forked version to clean repository
2017-11-10 03:14:09 +08:00
<PropertyGroup>
add multi targeting frameworks in the same project for net 4.5 through net 7.0 and net standard 2.0
2019-01-06 18:38:32 +08:00
<TargetFrameworks>netstandard2.0;net45;net451;net452;net46;net461;net462;net47</TargetFrameworks>
change the project name to something silly
2018-01-11 03:49:32 +08:00
<PackageId>PdfPig</PackageId>
make package nuget publishable
2018-01-07 20:09:23 +08:00
<DebugType>full</DebugType>
<Authors>UglyToad</Authors>
initial release: name package correctly
2018-01-11 06:35:09 +08:00
<Title>PdfPig</Title>
version 0.0.7
2019-08-03 23:14:58 +08:00
<Description>Reads text content from PDF documents and supports document creation. Apache 2.0 licensed.</Description>
version 0.0.11
2019-12-18 02:07:08 +08:00
<PackageLicenseExpression>Apache-2.0</PackageLicenseExpression>
add missing doc comments
2018-01-11 04:31:38 +08:00
<PackageProjectUrl>https://github.com/UglyToad/PdfPig</PackageProjectUrl>
0.0.6 - update version and sourcelink nuget version
2019-05-19 20:39:06 +08:00
<PackageTags>PDF;Reader;Document;Adobe;PDFBox;PdfPig;pdf-extract</PackageTags>
add missing doc comments
2018-01-11 04:31:38 +08:00
<RepositoryUrl>https://github.com/UglyToad/PdfPig</RepositoryUrl>
make package nuget publishable
2018-01-07 20:09:23 +08:00
<GenerateDocumentationFile>true</GenerateDocumentationFile>
version 0.0.11
2019-12-18 02:07:08 +08:00
<Version>0.0.11</Version>
<AssemblyVersion>0.0.11.0</AssemblyVersion>
<FileVersion>0.0.11.0</FileVersion>
add missing doc comments
2018-01-11 04:31:38 +08:00
<PackageIconUrl>https://raw.githubusercontent.com/UglyToad/PdfPig/master/documentation/pdfpig.png</PackageIconUrl>
<Product>PdfPig</Product>
#18 add sourcelink package and changes
2018-11-25 19:44:08 +08:00
<PublishRepositoryUrl>true</PublishRepositoryUrl>
<EmbedUntrackedSources>true</EmbedUntrackedSources>
#21 create first actual pdf document based on minimal example. writer for tokens. bump language version
2018-11-29 05:54:06 +08:00
<LangVersion>latest</LangVersion>
#18 add sourcelink package and changes
2018-11-25 19:44:08 +08:00
<AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder>
include dependencies as dlls in the published nuget by default nuget pack does not include project dependencies. this is suboptimal since it would require managing at least 5 nuget packages. this uses a workaround detailed here https://github.com/nuget/home/issues/3891 to copy the dependent dlls to the generated nuget package. this doesn't resolve the issue of how we publish the documentlayoutanalysis project, since it is the top of the dependency tree and we publish its parent, rather than it.
2020-01-05 21:56:14 +08:00
<TargetsForTfmSpecificBuildOutput>$(TargetsForTfmSpecificBuildOutput);CopyProjectReferencesToPackage</TargetsForTfmSpecificBuildOutput>
Move the code from the forked version to clean repository
2017-11-10 03:14:09 +08:00
</PropertyGroup>
#55 move support for images to page and add inline images support both xobject and inline images. adds unsupported filters so that exceptions are only thrown when accessing lazily evaluated image.bytes property rather than when opening the page. treat all warnings as errors.
2019-10-08 21:04:36 +08:00
<PropertyGroup Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|netstandard2.0|AnyCPU'">
<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
<WarningsAsErrors />
</PropertyGroup>
reorganise code for parsing font dictionaries and add the afm files as resources for adobe font metrics
2017-12-03 07:50:58 +08:00
<ItemGroup>
more work on boundaries and unit tests
2018-04-13 07:18:38 +08:00
<None Remove="Resources\CMap\*" />
<None Remove="Resources\GlyphList\*" />
reorganise code for parsing font dictionaries and add the afm files as resources for adobe font metrics
2017-12-03 07:50:58 +08:00
</ItemGroup>
<ItemGroup>
more work on boundaries and unit tests
2018-04-13 07:18:38 +08:00
<EmbeddedResource Include="Resources\CMap\*" />
<EmbeddedResource Include="Resources\GlyphList\*" />
reorganise code for parsing font dictionaries and add the afm files as resources for adobe font metrics
2017-12-03 07:50:58 +08:00
</ItemGroup>
#18 add sourcelink package and changes
2018-11-25 19:44:08 +08:00
<ItemGroup>
0.0.6 - update version and sourcelink nuget version
2019-05-19 20:39:06 +08:00
<PackageReference Include="Microsoft.SourceLink.GitHub" Version="1.0.0-beta2-18618-05">
#18 add sourcelink package and changes
2018-11-25 19:44:08 +08:00
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
</PackageReference>
</ItemGroup>
add multi targeting frameworks in the same project for net 4.5 through net 7.0 and net standard 2.0
2019-01-06 18:38:32 +08:00
move classes to new projects to make the project more useful and expose more usable classes we're rearchitecting in the following way. code used to read fonts from external file formats like truetype, adobe font metrics (afm) and adobe type 1 fonts are moving to a new project which doesn't reference most of the pdf logic. the shared logic is moving to a new flat-structured project called core. this is a sort-of onion type architecture, with core being the... core, fonts being the next layer of the onion, pdfpig itself the next. this will then support additional libraries/projects as outer layers of the onion as well as releasing standalone version of the font library as pdfbox does with fontbox.
2020-01-05 00:38:18 +08:00
<ItemGroup Condition="'$(TargetFramework)'=='net45' OR '$(TargetFramework)'=='net451' OR '$(TargetFramework)'=='net452' OR '$(TargetFramework)'=='net46' OR '$(TargetFramework)'=='net461' OR '$(TargetFramework)'=='net462' OR '$(TargetFramework)'=='net47'">
add multi targeting frameworks in the same project for net 4.5 through net 7.0 and net standard 2.0
2019-01-06 18:38:32 +08:00
<PackageReference Include="System.ValueTuple" Version="4.5.0" />
</ItemGroup>
move classes to new projects to make the project more useful and expose more usable classes we're rearchitecting in the following way. code used to read fonts from external file formats like truetype, adobe font metrics (afm) and adobe type 1 fonts are moving to a new project which doesn't reference most of the pdf logic. the shared logic is moving to a new flat-structured project called core. this is a sort-of onion type architecture, with core being the... core, fonts being the next layer of the onion, pdfpig itself the next. this will then support additional libraries/projects as outer layers of the onion as well as releasing standalone version of the font library as pdfbox does with fontbox.
2020-01-05 00:38:18 +08:00
<ItemGroup>
include dependencies as dlls in the published nuget by default nuget pack does not include project dependencies. this is suboptimal since it would require managing at least 5 nuget packages. this uses a workaround detailed here https://github.com/nuget/home/issues/3891 to copy the dependent dlls to the generated nuget package. this doesn't resolve the issue of how we publish the documentlayoutanalysis project, since it is the top of the dependency tree and we publish its parent, rather than it.
2020-01-05 21:56:14 +08:00
<ProjectReference Include="..\UglyToad.PdfPig.Core\UglyToad.PdfPig.Core.csproj" PrivateAssets="all"/>
<ProjectReference Include="..\UglyToad.PdfPig.Fonts\UglyToad.PdfPig.Fonts.csproj" PrivateAssets="all" />
<ProjectReference Include="..\UglyToad.PdfPig.Tokenization\UglyToad.PdfPig.Tokenization.csproj" PrivateAssets="all" />
<ProjectReference Include="..\UglyToad.PdfPig.Tokens\UglyToad.PdfPig.Tokens.csproj" PrivateAssets="all" />
move classes to new projects to make the project more useful and expose more usable classes we're rearchitecting in the following way. code used to read fonts from external file formats like truetype, adobe font metrics (afm) and adobe type 1 fonts are moving to a new project which doesn't reference most of the pdf logic. the shared logic is moving to a new flat-structured project called core. this is a sort-of onion type architecture, with core being the... core, fonts being the next layer of the onion, pdfpig itself the next. this will then support additional libraries/projects as outer layers of the onion as well as releasing standalone version of the font library as pdfbox does with fontbox.
2020-01-05 00:38:18 +08:00
</ItemGroup>
include dependencies as dlls in the published nuget by default nuget pack does not include project dependencies. this is suboptimal since it would require managing at least 5 nuget packages. this uses a workaround detailed here https://github.com/nuget/home/issues/3891 to copy the dependent dlls to the generated nuget package. this doesn't resolve the issue of how we publish the documentlayoutanalysis project, since it is the top of the dependency tree and we publish its parent, rather than it.
2020-01-05 21:56:14 +08:00
<Target Name="CopyProjectReferencesToPackage" DependsOnTargets="ResolveReferences">
<ItemGroup>
<BuildOutputInPackage Include="@(ReferenceCopyLocalPaths->WithMetadataValue('ReferenceSourceTarget', 'ProjectReference'))" />
</ItemGroup>
</Target>
add tools for code coverage metrics
2017-12-06 05:26:07 +08:00
Move the code from the forked version to clean repository
2017-11-10 03:14:09 +08:00
</Project>
Reference in New Issue Copy Permalink