Impossibile caricare il file o il montaggio stdole

Question

Appena installato lato VS2015 a fianco con VS2010 ...

applicazione in questione è stato costruito utilizzando VS2010 (set da utilizzare NET 4.0) (non migrate a VS2015) ha lavorato bene sul mio la macchina, mise sul server e cadde in un mucchio ... stdole era il problema ...

nell'errore registri di Windows> Applicazioni c'era un'eccezione:

Exception information: 
Exception type: ConfigurationErrorsException 
Exception message: Could not load file or assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' 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) 
    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) 
    at System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() 
    at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) 
    at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) 
    at System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies() 
    at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) 
    at System.Web.Compilation.BuildManager.ExecutePreAppStart() 
    at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) 

Could not load file or assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' 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) 
    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) 
    at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) 
    at  System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) 
    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection) 
    at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) 
    at System.Reflection.Assembly.Load(String assemblyString) 
    at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) 

Could not load file or assembly 'stdole' 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) 

Stack trace: at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) 
    at System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() 
    at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) 
    at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) 
    at System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies() 
    at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded) 
    at System.Web.Compilation.BuildManager.ExecutePreAppStart() 
    at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) 

guardò riferimento alla stdole ed era per il GAC e per una versione: 2.0.0.0

La testimonianza di nulla è cambiata.

Da dove viene questo errore?

Answer 1

Solo nel caso qualcuno altro incontra la questione allo stesso modo ho fatto ...

Ecco come ho risolto il problema:

soppresso il riferimento esistente per stdole, poi ha aggiunto un riferimento> estensioni> c'erano quattro voci per stdole! uno con l'icona dell'ufficio, uno con l'icona VS, uno con un ingranaggio (icona di installazione) e un altro senza icona (tutti e quattro erano esattamente gli stessi numeri di versione ecc.) ...

Aggiunto un riferimento a quello con VS icona e distribuito al server ... tutto va bene (tocchiamo ferro)

Answer 2

Si potrebbe voler esplorare il motivo per cui la libreria stdole (o una delle sue dipendenze) è stata manomessa.

Nel frattempo, eseguire il comando sn -Vr * in un prompt dei comandi per disabilitare il controllo di integrità sul computer locale.

Answer 3

Aggiungere un riferimento nel progetto di 'stdole.dll', che si trova in un paio di luoghi diversi

• GAC (C: \ Windows \ assembly)
• C: \ Programmi (x86) \ File comuni \ Microsoft Shared \ MSEnv \ PublicAssembli es

Ricostruire, ridistribuire e tutto dovrebbe essere buono.