When I try to install Install-Package Google.Apis.Plus.v1, I get the following error:
Install failed. Rolling back...Install-Package : Updating 'log4net 1.2.10' to 'log4net 2.0.3' failed. Unable to find a version of 'EPiServer.Logging.Log4Net' that is compatible with 'log4net 2.0.3'.At line:1 char:1+ Install-Package Google.Apis.Plus.v1+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Install-Package], InvalidOperationException + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
I am on CMS 8.8.2.
It looks like http://nuget.episerver.com/en/OtherPages/Package/?packageId=EPiServer.Logging.Log4Net&packageVersion=2.0.0-pre-000006 hasn't changed a lot (last changed in April). Is this a good road to take or is there a better option?
Thx in advance!
It is possible to load multiple versions of the same binaries concurrently into a project, but it's not recommended, so I haven't bothered finding out how. We had the same issue for a client using EPiServer together with Google's custom search; we ended up creating a separate project for these types of integrations, using it's own log4net version. I asked Kristoffer at EPi about it and he said that they are in the process of making changes in regard to log4net; so, it might be a temporary integration project should it turn out that the architecture is better that way later on.
Uri videoEntryUrl = new Uri(@"https://www.googleapis.com/youtube/v3/videos?part=snippet&id=VidoeKey&key=DeveloperKey");
Create Web request for videoEntryUrl
dynamic decodedJson = System.Web.Helpers.Json.Decode(json);
Here is how we did tricks with log4net (you still need to do black magic with packages to get everything added to your project, you may use "ignore dependencies" even):
- v1.2.10 is located in main bin/ folder
- create separate folder for other log4net.dll version - let's say bin/log4net.1.2.11/
- both files are named the same - "log4net.dll"
- add following lines to yourweb.config:
<assemblyIdentity name="log4net" publicKeyToken="1b44e1d426115821" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-188.8.131.52" newVersion="184.108.40.206" />
<bindingRedirect oldVersion="220.127.116.11-1.2.65535.0" newVersion="18.104.22.168" />
<codeBase version="22.214.171.124" href="bin\log4net1.2.11\log4net.dll" />
The only problem here with really new log4net version could be regarding publicToken value. You just need to check this. There has been real hype around this mess made by log4net team..