Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Google.ortools 7.2.6977 C# Could not load file or assembly 'Google.OrTools' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045) #1421

Closed
manofglass1 opened this issue Jul 12, 2019 · 73 comments
Closed

Google.ortools 7.2.6977 C# Could not load file or assembly 'Google.OrTools' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045) #1421

manofglass1 opened this issue Jul 12, 2019 · 73 comments
Assignees
@Mizux
Labels
Build: Makefile Makefile based build issue Lang: .NET .Net wrapper issue
Milestone
v7.5

Comments

@manofglass1
Copy link

My system configuration:
Windows 7 Ultimate
Visual Studio 2017

Installation steps:
I followed the installation steps from Installing OR-Tools for .Net from Binary on Windows. I did all the steps, and was able to execute the make successfully - examples all passed. There was no mention of the Nuget install for ORTools in these instructions.

Within visual studio 2017 I brought down the Google.OrTools by Laurent Perron v7.2.6977 from Nuget.

image
image

Google.Protobuf was added as a reference, but Google.OrTools was not

image

I manually added Google.OrTools as a reference to my project.

image

Built my web project and when I went to run I got the strong name error:

Could not load file or assembly 'Google.OrTools' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'Google.OrTools' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Google.OrTools' could not be loaded.

=== Pre-bind state information ===
LOG: DisplayName = Google.OrTools
(Partial)
WRN: Partial binding information was supplied for an assembly:
WRN: Assembly Name: Google.OrTools | Domain ID: 2
WRN: A partial bind occurs when only part of the assembly display name is provided.
WRN: This might result in the binder loading an incorrect assembly.
WRN: It is recommended to provide a fully specified textual identity for the assembly,
WRN: that consists of the simple name, version, culture, and public key token.
WRN: See whitepaper http://go.microsoft.com/fwlink/?LinkId=109270 for more information and common solutions to this issue.
LOG: Appbase = file:///C:/Users/Ed/Documents/Visual Studio 2017/Projects/WasteManagement/WasteManagement/
LOG: Initial PrivatePath = C:\Users\Ed\Documents\Visual Studio 2017\Projects\WasteManagement\WasteManagement\bin
Calling assembly : (Unknown).

LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Users\Ed\Documents\Visual Studio 2017\Projects\WasteManagement\WasteManagement\web.config
LOG: Using host configuration file: C:\Users\Ed\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/vs/75ffe19c/831bc11c/Google.OrTools.DLL.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/vs/75ffe19c/831bc11c/Google.OrTools/Google.OrTools.DLL.
LOG: Attempting download of new URL file:///C:/Users/Ed/Documents/Visual Studio 2017/Projects/WasteManagement/WasteManagement/bin/Google.OrTools.DLL.
LOG: Using application configuration file: C:\Users\Ed\Documents\Visual Studio 2017\Projects\WasteManagement\WasteManagement\web.config
LOG: Using host configuration file: C:\Users\Ed\Documents\IISExpress\config\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: Google.OrTools, Version=7.2.6977.0, Culture=neutral, PublicKeyToken=77370d3086a71853
ERR: Failed to complete setup of assembly (hr = 0x80131045). Probing terminated.

Stack Trace:
[FileLoadException: Could not load file or assembly 'Google.OrTools' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]

[FileLoadException: Could not load file or assembly 'Google.OrTools, Version=7.2.6977.0, Culture=neutral, PublicKeyToken=77370d3086a71853' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +0
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) +225
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) +110
System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +22
System.Reflection.Assembly.Load(String assemblyString) +34
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +88

[ConfigurationErrorsException: Could not load file or assembly 'Google.OrTools, Version=7.2.6977.0, Culture=neutral, PublicKeyToken=77370d3086a71853' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +1259
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +474
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +120
System.Web.Configuration.AssemblyInfo.get_AssemblyInternal() +76
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +247
System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies() +77
System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) +204
System.Web.Compilation.BuildManager.ExecutePreAppStart() +226
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +1415

[HttpException (0x80004005): Could not load file or assembly 'Google.OrTools, Version=7.2.6977.0, Culture=neutral, PublicKeyToken=77370d3086a71853' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +555
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +154
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +844

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.3429.0
@Mizux Mizux added Build: Makefile Makefile based build issue Lang: .NET .Net wrapper issue labels Jul 16, 2019
@neeman1
Copy link

neeman1 commented Jul 24, 2019

Same issue, any updates on resolution or workarounds?
Have no issues in building/running Console 64bit .Net Framework 4.7.2 project, but the same setup in web api 64bit class library output running .Net Framework 4.7.2 is producing the same error above.

@lperron
Copy link
Collaborator

lperron commented Jul 24, 2019 via email

@lperron
Copy link
Collaborator

lperron commented Aug 7, 2019

Do you still have the issue with 7.3 ?

@manofglass1
Copy link
Author

manofglass1 commented Aug 7, 2019 via email

@manofglass1
Copy link
Author

manofglass1 commented Aug 7, 2019 via email

@lperron
Copy link
Collaborator

lperron commented Aug 7, 2019 via email

@lperron
Copy link
Collaborator

lperron commented Aug 7, 2019 via email

@manofglass1
Copy link
Author

manofglass1 commented Aug 8, 2019 via email

@lperron
Copy link
Collaborator

lperron commented Aug 8, 2019 via email

@ptr1120
Copy link
Contributor

ptr1120 commented Aug 11, 2019

Hello,

First of all - thank you for the ortools - it is extremely good and has almost all the functionality I need.
Unfortunately, I also experience FileLoadException when using OrTools 7.3 in VisualStudio 2019 and Rider 2019. Some things that may affect this issue:

  1. Nuget folder structure: To me the folder structure of the generated Nuget looks not standard.
  • Google.OrTools.7.3.7083 is the Nuget for providing the managed Google.OrTools.dll dependency. It contains the Google.OrTools.dll in a folder ref/netstandard2.0, but it should be rather in a folder named lib/netstandard2.0 (See also)
  • Netstandard2.0 is compatible with netframework 4.6.1 (See also). Typically, when building a netstandard package a compatible netframework package is built in order to support net framework.

For an example with a "similar" project that also uses a managed Nuget with a platform-dependent native NuGet see LibGit2Sharp:
Capture

  1. Duplicated managed dll: Google.OrTools.7.3.7083 Nuget contains a managed .Net Google.OrTools.dll with a size of 598 KB. This dll contains only method empty stubs:
    Capture2
    Whereas google.ortools.runtime.win-x64.7.3.7083 Nuget also contains a managed .Net Google.OrTools.dll under runtimes/win-x64/lib/netstandard2.0 but with a size 962 kb. This dll contains the correct managed code for the Google.OrTools dependency but should be provided by the Google.OrTools NuGet package (in my opinion).

  2. Nice to haves:

  • It would be great to include the symbols (Google.OrTools.pdb) for the managed dll in the Nuget in order to improve the debugging experience.
  • It would be nice to include the generated documentation file (Google.OrTools.xml) in the Nuget.
  • It would be also nice to remove the content files in the Google.OrTools Nuget. Currently, all proto files are added to the content folder of the Nuget and are therefore included in the project that consumes the dependency and results in a lot of unnecessary files and folders in the project.
    Capture3

Best regards,
Peter

@lperron
Copy link
Collaborator

lperron commented Aug 11, 2019 via email

@ptr1120
Copy link
Contributor

ptr1120 commented Aug 11, 2019

Of course, I will have a look at it, hoping to understand the cmake things, where I am not knowing much of...

@lperron
Copy link
Collaborator

lperron commented Aug 11, 2019 via email

@ptr1120
Copy link
Contributor

ptr1120 commented Aug 11, 2019

@Mizux : do you know, why the Nuget for the C# Wrapper for OrTools (Google.OrTools.nuget) is platform dependent? Does Swig generate platform-dependent code for the wrapper?

@lperron
Copy link
Collaborator

lperron commented Aug 11, 2019 via email

@ptr1120
Copy link
Contributor

ptr1120 commented Aug 13, 2019

@lperron : Sorry I need to ask again more clearly. Do you know whether the Swig generated C# code (cs files) is paltform dependent? I would like to make one package for the managed C# code and again 3 for the native, platform dependent Swig c wrapper and ortools binary.

@lperron
Copy link
Collaborator

lperron commented Aug 13, 2019 via email

@ylmzkaan
Copy link

ylmzkaan commented Sep 2, 2019

There is a pull request to fix this problem but as @lperron said, it won't published until September at best. So, is there a workaround for this problem like using different VS version or .Net framework?

@lperron
Copy link
Collaborator

lperron commented Sep 7, 2019

I merged your PR.

Thanks

@lperron lperron closed this as completed Sep 7, 2019
@pablojmp
Copy link

pablojmp commented Oct 18, 2019 •
edited

Hi, this issue still happens on version 7.4.7247.0 when consuming the or tools nuget package from a web application targeting .NET Framework 4.6.2 in Visual Studio 2019.
I used sn.exe to check if the assembly had any strong name verification issues and i got this:

sn -v .\Google.OrTools.dll

Microsoft (R) .NET Framework Strong Name Utility  Version 4.0.30319.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Failed to verify assembly -- Strong name validation failed.

Any ideas?

Edit: opened #1655 for this issue

@ranjithota
Copy link

ranjithota commented Oct 18, 2019 •
edited

I am too struggling to figure out, whats going wrong.

Could not load file or assembly 'Google.OrTools' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)

Developed .NET Standard 2.0 wrapper library for processing data using Google.ORTool 7.4.7247.0 linear solver
Calling it from 4.7.1 WebAPI X64.
First it complained the WebAPI project also need Google.OrTool. Installed the Google.ORTool 7.4.7247.0 and all it dependencies.

I also Tried to copy the dlls and use it as fixed dll reference in standard library. Its giving the same error.

@ptr1120
Copy link
Contributor

ptr1120 commented Oct 18, 2019

Looks like something went wrong during singning of the build binaries, maybe the signing key was wrong/missing?

@pablojmp pablojmp mentioned this issue Oct 18, 2019
Closed
@ranjithota
Copy link

How do I fix it now? I have no idea...

Thinking of removing the whole signing thing and get dlls and use them.

@ptr1120
Copy link
Contributor

ptr1120 commented Oct 18, 2019

If you build the ortools manually you will get a working nuget that you can reference.

@ranjithota
Copy link

Don't know whats going wrong.
Any direction from here.

image

@pablojmp
Copy link

pablojmp commented Oct 18, 2019 •
edited

@ranjithota did you followed this installation guide?

btw, i ran sn -v on previous versions (6.9 onwards) and they all gave a strong name validation failed output

@zohaibdhukka
Copy link

and how do i sign locally

@pablojmp
Copy link

@zohaibdhukka Hi, try this test project

You'll need to run nuget restore first, then for some reason it fails if you don't do

Update-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform -r

on the package manager console.

Hope it works

@pablojmp
Copy link

pablojmp commented Oct 24, 2019 •
edited

Use NuGet Package Restore to download them; there's your problem.

See my previous comment

You'll need to run nuget restore first, then for some reason it fails if you don't do
Update-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform -r
on the package manager console.

@zohaibdhukka
Copy link

and test project also give me the same "Could not load file" error

@ranjithota
Copy link

@ranjithota how to bypass strong name verification for an assembly

In this case the message is unrelated because the error was a missing native dependency. Looks like strong name validation is bypassed by default

image

Removed strong name and public key token and built my own nuget packages, getting above error. Package explorer view of the generated package.

image

@Mizux
Copy link
Collaborator

Mizux commented Nov 18, 2019

My current investigation on Archlinux

Get the published package

I downloaded the Google.OrTools official package at:
https://www.nuget.org/api/v2/package/Google.OrTools/7.4.7247
and extract it (ed a .nupkg is "just" an archive, so i used file-roller)

Check key

Using mono (extra/mono 6.0.0.334-1) to get /usr/bin/sn

pacman -Qo sn
/usr/bin/sn is owned by mono 6.0.0.334-1

I've got:

sn -v lib/netstandard2.0/Google.OrTools.dll 
Mono StrongName - version 6.0.0.0
StrongName utility for signing assemblies
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Assembly lib/netstandard2.0/Google.OrTools.dll is delay-signed but not strongnamed

sn -v lib/netstandard2.0/Google.OrTools.dll
Mono StrongName - version 6.0.0.0
StrongName utility for signing assemblies
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Assembly lib/netstandard2.0/Google.OrTools.dll is delay-signed but not strongnamed

to sign we use:

or-tools/ortools/dotnet/Google.OrTools/Google.OrTools.csproj.in

Lines 15 to 18 in 4617300

<!-- Signing -->
<AssemblyOriginatorKeyFile>../../../bin/or-tools.snk</AssemblyOriginatorKeyFile>
<SignAssembly>true</SignAssembly>
<PublicSign Condition="'$(OS)' != 'Windows_NT'">true</PublicSign>

like specified in the doc...
ref: https://docs.microsoft.com/en-us/dotnet/core/tools/project-json-to-csproj#keyfile

Maybe related: to dotnet/msbuild#2503

Trying to disable delay sign on pet project

Protocol

mkdir tmp && cd tmp
dotnet new console
dotnet build

Verify the dll is not signed

sn -v bin/Debug/netcoreapp2.2/tmp.dll
Mono StrongName - version 6.0.0.0
StrongName utility for signing assemblies
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

bin/Debug/netcoreapp2.2/tmp.dll is not a strongly named assembly.

Then I add to tmp.csproj

<AssemblyOriginatorKeyFile>sgKey.snk</AssemblyOriginatorKeyFile>
<SignAssembly>True</SignAssembly>
<PublicSign>True</PublicSign>

ref: https://docs.microsoft.com/en-us/dotnet/core/tools/project-json-to-csproj#keyfile

then again

dotnet build
Microsoft (R) Build Engine version 15.9.20.63311 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 47.69 ms for /home/mizux/work/debug/tmp/tmp.csproj.
CSC : error CS7027: Error signing output with public key from file 'tmp/sgKey.snk'
 -- Could not find file 'tmp/sgKey.snk'. [tmp/tmp.csproj]
CSC : error CS8102: Public signing was specified and requires a public key, but no public key was specified. [tmp/tmp.csproj]

Build FAILED.

CSC : error CS7027: Error signing output with public key from file 'tmp/sgKey.snk'
 -- Could not find file 'tmp/sgKey.snk'. [tmp/tmp.csproj]
CSC : error CS8102: Public signing was specified and requires a public key, but no public key was specified. [tmp/tmp.csproj]
    0 Warning(s)
    2 Error(s)

Time Elapsed 00:00:01.85

then I create a key using

sn -k sgKey.snk
dotnet build
...
 Restore completed in 47.09 ms for tmp/tmp.csproj.
  tmp -> bin/Debug/netcoreapp2.2/tmp.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:01.58

and when verifying:

sn -v bin/Debug/netcoreapp2.2/tmp.dll 
Mono StrongName - version 6.0.0.0
StrongName utility for signing assemblies
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Assembly bin/Debug/netcoreapp2.2/tmp.dll is delay-signed but not strongnamed

I've tried to add

<DelaySign>False</DelaySign>

... without any success...

EDIT:
Potential fix !, still on my pet project, if I use

<!-- Signing -->
<AssemblyOriginatorKeyFile>sgKey.snk</AssemblyOriginatorKeyFile>
<SignAssembly>True</SignAssembly>
<PublicSign>False</PublicSign>
<DelaySign>False</DelaySign>

note: <DelaySign>False</DelaySign> seems optional
I've got:

sn -v bin/Debug/netcoreapp2.2/tmp.dll
Mono StrongName - version 6.0.0.0
StrongName utility for signing assemblies
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Assembly bin/Debug/netcoreapp2.2/tmp.dll is strongnamed.

-> it seems that <PublicSign>True</PublicSign> force the delay sign...

I'll continue my investigation

note: if PublicSign and DelaySign are both True you'll have

dotnet build                          
Microsoft (R) Build Engine version 15.9.20.63311 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 46.94 ms for /home/mizux/work/debug/plop/plop.csproj.
CSC : error CS7102: Compilation options 'PublicSign' and 'DelaySign' can't both be specified at the same time. [/home/mizux/work/debug/plop/plop.csproj]

Build FAILED.

@Mizux
Copy link
Collaborator

Mizux commented Nov 18, 2019

Few references on Public/Delay sign:

https://docs.microsoft.com/fr-fr/dotnet/csharp/language-reference/compiler-options/publicsign-compiler-option

https://docs.microsoft.com/fr-fr/dotnet/csharp/language-reference/compiler-options/delaysign-compiler-option

Seems that not "really" signing an assembly with the private key is the norm in the OSS...

Since almost no consumers actually need to check if the assembly is fully signed, these publicly built assemblies are useable in almost every scenario where the fully signed one would be used.

@Mizux
Copy link
Collaborator

Mizux commented Nov 18, 2019

just found f66e52c#diff-60ecbbead3dbf52f65983bc6a00dc84c didn't contains a patch for the meta package Google.OrTools

@Mizux Mizux closed this as completed in d001017 Nov 19, 2019
@ranjithota
Copy link

just found f66e52c#diff-60ecbbead3dbf52f65983bc6a00dc84c didn't contains a patch for the meta package Google.OrTools

I did the same thing and compiled my code locally to generate the nuget packages and used them instead from nuget server.

Works like a charm.

@lperron
Copy link
Collaborator

lperron commented Nov 19, 2019 via email

@m0ddixx
Copy link

m0ddixx commented Jan 16, 2020

When is the fix going to show up in the nuget repository?
As far as I interpret the tree correctly, the stable branch still don't contain the commit thus the current nuget packages remains unusable. while dating back to summer 2019.

@Mizux
Copy link
Collaborator

Mizux commented Jan 16, 2020 •
edited

once release v7.5 is out ETA around mid/end of January

stable (default) branch is our release release branch and should fast forward from one release tag to an other, currently the last release is v7.4.
The patch has been done on our "devel branch" named master after this last release...

@Mizux Mizux added this to the v7.5 milestone Jan 21, 2020
@Mizux Mizux self-assigned this Jan 21, 2020
@GuyBenhaim
Copy link

Hello,
Was this resolved for 7.4 or to be resolved for 7.5? (For .AspNet WebAPI projects)
Or, do we need to dive into the NuGet process and hopefully solve it somehow ...

@lperron
Copy link
Collaborator

lperron commented Jan 26, 2020 via email

@GuyBenhaim
Copy link

GuyBenhaim commented Jan 26, 2020 •
edited

Great.
For me, even a pre-released version should be useful, if accessible via NuGet protocol.

@lperron
Copy link
Collaborator

lperron commented Jan 26, 2020 via email

@tzishi1991
Copy link

Hi Laurent Perron/Mizux,
Thank you for the update v7.5
I am able to run a console app using your libraries, and it works perfectly.
I am still having issues with running a web app using your library, I keep getting the following exception "Could not load file or assembly 'Google.OrTools, Version=7.5.7466.0, Culture=neutral, PublicKeyToken=53dbb1ea090cbef7'." Please you help me understand the necessary steps to resolve this.
I've tried to follow some of the above advice but I just can't get it to work.
Your help is greatly appreciated!
Many Thanks

Tino

@Mizux
Copy link
Collaborator

Mizux commented Feb 7, 2020

@tzishi1991 maybe be related to #1862

@m0ddixx
Copy link

m0ddixx commented Feb 7, 2020

@tzishi1991 You might wan't to check if you have the Visual C++ Redistributable 2019 installed on your machine. download found here

@tzishi1991
Copy link

@tzishi1991 maybe be related to #1862

Thanks for the quick reply, I will check that issue#

@tzishi1991
Copy link

@tzishi1991 You might wan't to check if you have the Visual C++ Redistributable 2019 installed on your machine. download found here

Hi @m0ddixx , i tried that, but still getting the same error message. Thanks though. I am thinking there might be a dependency conflict with the other libraries in my web app

@m0ddixx
Copy link

m0ddixx commented Feb 7, 2020

@tzishi1991 You might wan't to check if you have the Visual C++ Redistributable 2019 installed on your machine. download found here

Hi @m0ddixx , i tried that, but still getting the same error message. Thanks though. I am thinking there might be a dependency conflict with the other libraries in my web app

If you look into #1862 there are differences within the same exception. @Mizux stated that a certain HRESULT code might be related to a COM permission setting within IIS and this is not solved so far.

@GuyBenhaim
Copy link

GuyBenhaim commented Feb 9, 2020 •
edited

Hello,
Many comments .... was there a solution for solving the issue?
I saw this comment by ranjithota, on Nov 19, 2019

just found f66e52c#diff-60ecbbead3dbf52f65983bc6a00dc84c didn't contains a patch for the meta package Google.OrTools
I did the same thing and compiled my code locally to generate the nuget packages and used them instead from nuget server. Works like a charm.

What is this "same thing" ? Was that with a WebAPI project?

@Mizux Mizux mentioned this issue Feb 10, 2020
Closed
@nicolasmohamed nicolasmohamed mentioned this issue May 23, 2020
Closed
@ooo1234567
Copy link

Same issue for me. Works like a charm with .net core so many troubles with .net framework.

Since I am using a very old Ms server I have to use .net framework. Please if you have some guidance let me know.

@Mizux
Copy link
Collaborator

Mizux commented Feb 11, 2021

@ozizi1 did you try with a more recent version of Google.OrTools ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Mizux Mizux

Labels
Build: Makefile Makefile based build issue Lang: .NET .Net wrapper issue
Projects
None yet
Milestone
v7.5
Development

No branches or pull requests