From 3486ade8396e706509fa5e811077ad00e6b993fa Mon Sep 17 00:00:00 2001 From: Oren Novotny Date: Wed, 8 Mar 2017 08:56:15 -0500 Subject: use pack targets --- crypto/src/AssemblyInfo.cs | 59 ---------------------------------------------- crypto/src/crypto.csproj | 35 ++++++--------------------- 2 files changed, 7 insertions(+), 87 deletions(-) (limited to 'crypto/src') diff --git a/crypto/src/AssemblyInfo.cs b/crypto/src/AssemblyInfo.cs index 053364594..022895b0a 100644 --- a/crypto/src/AssemblyInfo.cs +++ b/crypto/src/AssemblyInfo.cs @@ -9,65 +9,6 @@ using System.Linq; using System.Runtime.InteropServices; #endif -// -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -// -[assembly: AssemblyTitle("BouncyCastle.Crypto")] -[assembly: AssemblyDescription("Bouncy Castle Cryptography API")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("The Legion of the Bouncy Castle Inc.")] -[assembly: AssemblyProduct("Bouncy Castle for .NET")] -[assembly: AssemblyCopyright("Copyright (C) 2000-2015")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Revision and Build Numbers -// by using the '*' as shown below: - -[assembly: AssemblyVersion("1.8.1.0")] -[assembly: AssemblyFileVersion("1.8.15362.1")] -[assembly: AssemblyInformationalVersion("1.8.1")] - -// -// In order to sign your assembly you must specify a key to use. Refer to the -// Microsoft .NET Framework documentation for more information on assembly signing. -// -// Use the attributes below to control which key is used for signing. -// -// Notes: -// (*) If no key is specified, the assembly is not signed. -// (*) KeyName refers to a key that has been installed in the Crypto Service -// Provider (CSP) on your machine. KeyFile refers to a file which contains -// a key. -// (*) If the KeyFile and the KeyName values are both specified, the -// following processing occurs: -// (1) If the KeyName can be found in the CSP, that key is used. -// (2) If the KeyName does not exist and the KeyFile does exist, the key -// in the KeyFile is installed into the CSP and used. -// (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility. -// When specifying the KeyFile, the location of the KeyFile should be -// relative to the project output directory which is -// %Project Directory%\obj\. For example, if your KeyFile is -// located in the project directory, you would specify the AssemblyKeyFile -// attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")] -// (*) Delay Signing is an advanced option - see the Microsoft .NET Framework -// documentation for more information on this. -// -[assembly: AssemblyDelaySign(false)] -#if STRONG_NAME -[assembly: AssemblyKeyFile(@"../BouncyCastle.snk")] -#endif - [assembly: CLSCompliant(true)] #if !PORTABLE [assembly: ComVisible(false)] diff --git a/crypto/src/crypto.csproj b/crypto/src/crypto.csproj index afbee9d5c..6175a6db2 100644 --- a/crypto/src/crypto.csproj +++ b/crypto/src/crypto.csproj @@ -5,22 +5,10 @@ crypto ..\..\BouncyCastle.snk true - false - false - false - false - false - false - false - false - false - false - false - - - .NETPortable - v4.0 - Profile328 + Bouncy Castle for .NET ($(TargetFramework)) + Copyright (C) 2000-2017 + The Legion of the Bouncy Castle Inc. + Bouncy Castle Cryptography API true @@ -41,17 +29,8 @@ + + - - - - - - - - - - - - + \ No newline at end of file -- cgit 1.5.1