You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps: select all files and save all into solution
note: it'll take much time until assert.
This issue is a bit complicated...
if you select just one assembly (that is present in exception trace - it decompiles OK!
but if you so it in a bunch - issue is raised...)
I guess, it means that there is some correlation between assemblies, which is not good IMHO
Please also pay attention that is can't resolve a generic assembly from .net fw.
Failed to decompile the assembly 'C:\---onizer.dll':
Could not resolve known assembly 'PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'!
in assembly "C:\-----onizer.dll"
---> System.Exception: Could not resolve known assembly 'PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'!
at ILSpy.BamlDecompiler.Baml.KnownThings.ResolveAssembly(String name) in offset 78
at ILSpy.BamlDecompiler.Baml.KnownThings.InitAssemblies() in offset 73
at ILSpy.BamlDecompiler.Baml.KnownThings..ctor(IDecompilerTypeSystem typeSystem) in offset 77
-- continuing with outer exception (ICSharpCode.Decompiler.DecompilerException) --
at ILSpy.BamlDecompiler.Baml.KnownThings..ctor(IDecompilerTypeSystem typeSystem) in offset 134
at ILSpy.BamlDecompiler.Baml.BamlContext..ctor(IDecompilerTypeSystem typeSystem) in offset 33
at ILSpy.BamlDecompiler.Baml.BamlContext.ConstructContext(IDecompilerTypeSystem typeSystem, BamlDocument document, CancellationToken token) in offset 7
at ILSpy.BamlDecompiler.XamlContext.Construct(IDecompilerTypeSystem typeSystem, BamlDocument document, CancellationToken token, BamlDecompilerOptions bamlDecompilerOptions) in offset 33
at ILSpy.BamlDecompiler.XamlDecompiler.Decompile(IDecompilerTypeSystem typeSystem, BamlDocument document, CancellationToken token, BamlDecompilerOptions bamlDecompilerOptions, List`1 assemblyReferences) in offset 1
at ILSpy.BamlDecompiler.BamlResourceEntryNode.LoadIntoDocument(PEFile module, IAssemblyResolver assemblyResolver, Stream stream, CancellationToken cancellationToken) in offset 36
at ILSpy.BamlDecompiler.BamlResourceFileHandler.WriteResourceToFile(LoadedAssembly assembly, String fileName, Stream stream, DecompilationOptions options) in offset 21
at ICSharpCode.ILSpy.CSharpLanguage.ILSpyWholeProjectDecompiler.WriteResourceToFile(String fileName, String resourceName, Stream entryStream) in offset 69
at ICSharpCode.Decompiler.CSharp.WholeProjectDecompiler.<WriteResourceFilesInProject>d__35.MoveNext() in offset 520
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection) in offset 234
at ICSharpCode.Decompiler.CSharp.WholeProjectDecompiler.DecompileProject(PEFile moduleDefinition, String targetDirectory, TextWriter projectFileWriter, CancellationToken cancellationToken) in offset 70
at ICSharpCode.ILSpy.CSharpLanguage.DecompileAssembly(LoadedAssembly assembly, ITextOutput output, DecompilationOptions options) in offset 61
at ICSharpCode.ILSpy.SolutionWriter.WriteProject(LoadedAssembly loadedAssembly, Language language, String targetDirectory, CancellationToken ct) in offset 151
ILSpy version 5.0.0.5078-preview4
Steps: select all files and save all into solution
note: it'll take much time until assert.
This issue is a bit complicated...
if you select just one assembly (that is present in exception trace - it decompiles OK!
but if you so it in a bunch - issue is raised...)
I guess, it means that there is some correlation between assemblies, which is not good IMHO
Please also pay attention that is can't resolve a generic assembly from .net fw.
this is a full set of zoo :)
https://www.sendspace.com/file/e03331
The text was updated successfully, but these errors were encountered: