System.Data.SQLite
Check-in [51270bcb44]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Make sure the assembly built for .NET Core is strong named signed.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 51270bcb44d100d3e9a7a57491813073d6ce085f
User & Date: mistachkin 2018-07-07 16:10:50
Context
2018-07-10
01:53
Do not allow read-only connections into (or out of) the connection pool. check-in: 14d18ee826 user: mistachkin tags: trunk
2018-07-07
16:10
Make sure the assembly built for .NET Core is strong named signed. check-in: 51270bcb44 user: mistachkin tags: trunk
05:29
Fix compilation issues when the 'UseSqliteStandard' MSBuild property is used. check-in: 1f44df4816 user: mistachkin tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to System.Data.SQLite/System.Data.SQLite.NetStandard20.csproj.

    57     57     <PropertyGroup>
    58     58       <TargetFramework>netstandard2.0</TargetFramework>
    59     59       <GenerateAssemblyInfo>false</GenerateAssemblyInfo>
    60     60       <Deterministic>False</Deterministic>
    61     61       <EnableDefaultItems>false</EnableDefaultItems>
    62     62     </PropertyGroup>
    63     63   
           64  +  <!--
           65  +  ******************************************************************************
           66  +  ** .NET Standard 2.0 Specific Eagle Strong Name Signing Property Overrides  **
           67  +  ******************************************************************************
           68  +  -->
           69  +
           70  +  <PropertyGroup>
           71  +    <!--
           72  +        NOTE: Apparently, the .NET Core build system sets the SignAssembly
           73  +              property to false; therefore, reset it to true.  Also, delay
           74  +              signing is currently non-functional due to the inability to
           75  +              run the strong name signing tool (sn.exe).  It behaves badly
           76  +              when run against a .NET Core assembly.
           77  +    -->
           78  +    <SignAssembly>true</SignAssembly>
           79  +    <DelaySign>false</DelaySign>
           80  +
           81  +    <!--
           82  +        TODO: Why is this needed?  It seems that public signing is quite
           83  +              similar to delay signing.  Why is this necessary when not
           84  +              running on Windows?
           85  +    -->
           86  +    <PublicSign Condition="'$(OS)' != 'Windows_NT'">true</PublicSign>
           87  +  </PropertyGroup>
           88  +
    64     89     <!--
    65     90     ******************************************************************************
    66     91     **                    .NET Standard 2.0 Specific Targets                    **
    67     92     ******************************************************************************
    68     93     -->
    69     94   
    70     95     <Target Name="GenerateResourcesForNetStandard20"