Skip to content

Commit

Permalink
Releasing 5.9.6
Browse files Browse the repository at this point in the history
  • Loading branch information
ENikS committed Mar 2, 2019
1 parent bdfde74 commit 198a9a7
Show file tree
Hide file tree
Showing 17 changed files with 17 additions and 27 deletions.
2 changes: 1 addition & 1 deletion Configuration
2 changes: 1 addition & 1 deletion Interception
2 changes: 1 addition & 1 deletion Log4net
2 changes: 1 addition & 1 deletion MVC
2 changes: 1 addition & 1 deletion Microsoft.Logging
2 changes: 1 addition & 1 deletion Microsoft.Options
2 changes: 1 addition & 1 deletion NLog
12 changes: 1 addition & 11 deletions Package.nuspec
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
<package >
<metadata>
<id>Unity</id>
<version>5.9.5</version>
<version>5.9.6</version>
<authors>Unity Container Project</authors>
<owners>Unity Container Project</owners>
<licenseUrl>https://github.com/unitycontainer/unity/blob/v5.x/LICENSE</licenseUrl>
Expand All @@ -14,35 +14,25 @@
<copyright>Copyright © Unity Container Project 2018</copyright>
<tags>Unity Container unitycontainer Microsoft.Practices.Unity IoC</tags>
<dependencies>
<group targetFramework=".NET4.0">

This comment has been minimized.

Copy link
@itsho

itsho Mar 4, 2019

It was worth mentioning that this version no longer supports .NET 4.0 :-)

This comment has been minimized.

Copy link
@ENikS

ENikS via email Mar 4, 2019

Author Collaborator

This comment has been minimized.

Copy link
@itsho

itsho Mar 4, 2019

You are correct.
the net40 does exists, but when I tried to use 5.9.6 in .NET 4.0 project, I got an exception which got away after getting back to version 5.9.5.

I'll test it again and will report with the exact error I had.

and still - I wonder how does the net40 is there if you removed the line from the .nuspec file?

This comment has been minimized.

Copy link
@ENikS

ENikS Mar 4, 2019

Author Collaborator

Restored group in 5.9.7

This comment has been minimized.

Copy link
@itsho

itsho Mar 4, 2019

  1. My apologies. it was a misconfiguration on my end (PackageReference vs packages.config).
  2. I've tested again with 5.9.7, and its working well.

Thank you.

<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NET4.5">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NET4.6">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NET4.7">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NETCoreApp1.0">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NETCoreApp2.0">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NETStandard1.0">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
<group targetFramework=".NETStandard2.0">
<dependency id="System.ValueTuple" version="4.5.0" exclude="Build,Analyzers" />
<dependency id="System.Runtime.CompilerServices.Unsafe" version="4.5.2" exclude="Build,Analyzers" />
</group>
</dependencies>
Expand Down
2 changes: 1 addition & 1 deletion ServiceLocation
2 changes: 1 addition & 1 deletion WCF
2 changes: 1 addition & 1 deletion WebAPI

0 comments on commit 198a9a7

Please sign in to comment.