Merge pull request #151 from bugsnag/5963-strong-name-assemblies

[PLAT-5963] strong name sign assemblies

Directory.build.props

@@ -1,5 +1,7 @@
 <Project>
   <PropertyGroup>
     <OutputPath>$(BaseOutputPath)</OutputPath>
+	<AssemblyOriginatorKeyFile>$(MSBuildThisFileDirectory)Bugsnag.snk</AssemblyOriginatorKeyFile>
+    <SignAssembly>true</SignAssembly>
   </PropertyGroup>
 </Project>

UPGRADING.md

@@ -1,6 +1,14 @@
 Upgrading
 =========
 
+## 2.x to 3.x
+
+If you are targeting .NET Framework, v3.0.0 contains binary breaking changes due to the introduction of strong name signing. You will need to re-compile your application against the new version. If you are referencing a library that also references Bugsnag you may also need to add a binding redirect or enable automatic binding redirection in your project file:
+
+```
+<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
+```
+
 ## 1.x to 2.x
 
 *Our .NET notifier has gone through some major improvements, and there are some changes you'll need to make to get onto the new version.*

src/Bugsnag.AspNet.Core/Bugsnag.AspNet.Core.csproj

@@ -4,6 +4,7 @@
     <Title>Bugsnag .NET ASP.NET Core Notifier</Title>
     <Description>The Bugsnag Notifier for ASP.NET Core gives you instant notification of exceptions thrown from your ASP.NET Core applications. Any uncaught exceptions will trigger a notification to be sent to your Bugsnag project.</Description>
     <TargetFrameworks>netstandard1.3;netstandard2.0</TargetFrameworks>
+	<SignAssembly>false</SignAssembly>
   </PropertyGroup>
   <ItemGroup>
     <ProjectReference Include="..\Bugsnag\Bugsnag.csproj" />

src/Directory.build.props

@@ -1,4 +1,7 @@
 <Project>
+
+  <Import Project="..\Directory.Build.props"/>
+
   <PropertyGroup>
     <Authors>snmaynard kattrali martin308</Authors>
     <Version></Version>

tests/Directory.build.props

@@ -0,0 +1,5 @@
+<Project>
+  <PropertyGroup>
+    <SignAssembly>false</SignAssembly>
+  </PropertyGroup>
+</Project>