zed
zed
CC#
Created by zed on 6/20/2023 in #help
✅ Modify embedded resources at runtime
Is there a way to modify an assembly's own embedded resources? I'm not looking into physically changing the file, but (ideally) just virtually change what it produces, when an embedded resource is requested. The context here being that I'm interfacing with a third party component which reads data only from an embedded resource, but I want to feed it data that is generated at runtime - it has no other way (that I know of) to interface with my project, other than through reading of embedded resources. While the "third" party component is technically developed in-house, it's from a closed off development team, and they said they have no resources to devote to changing this behavior. So I'm not sure what else I could do. Unfortunately, this is .NET Framework 4.8, so I don't have some newer features available to me. Any ideas?
9 replies
CC#
Created by zed on 6/15/2023 in #help
✅ Resolving an ambiguous assembly reference
We recently upgraded an included NuGet package from version 2.0.1 to 3.0.1 (Spring.NET, in case it matters). Now we get this exception:
Could not load file or assembly 'Spring.Services, Version=2.0.1.45000, Culture=neutral, PublicKeyToken=65e474d141e25e07' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Could not load file or assembly 'Spring.Services, Version=2.0.1.45000, Culture=neutral, PublicKeyToken=65e474d141e25e07' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
This indicates, that we missed upgrading one of our components, but we cannot find out which one. We're also including some third party components, which have (ostensibly) also been updated to use Spring.NET 3.0.1. But the provider assures us, that all projects in their solution were upgraded to use version 3.0.1. Now we're at a loss. Is there a way to get more detailed information on which of our assemblies or components tries to reference the older version? A plain text search across all our .csproj and .config files revealed no reference to 2.0.1, and we're not sure what else to do.
50 replies