zed Comments - Answer Overflow

zed

Posts Comments

CC#

•Created by zed on 4/2/2025 in #help

✅ Stack overflow, but can't change the code

Too late! Both for that, and this reply lol, sorry, but your suggestion worked great 👍

9 replies

CC#

•Created by zed on 4/2/2025 in #help

✅ Stack overflow, but can't change the code

I'll experiment with that

9 replies

CC#

•Created by zed on 4/2/2025 in #help

✅ Stack overflow, but can't change the code

Oh that sounds good, thanks

9 replies

CC#

•Created by zed on 6/20/2023 in #help

✅ Modify embedded resources at runtime

Thanks for helping though :)

9 replies

CC#

•Created by zed on 6/20/2023 in #help

✅ Modify embedded resources at runtime

Either way, I don't think there's a way to do that within the confines of the framework itself

9 replies

CC#

•Created by zed on 6/20/2023 in #help

✅ Modify embedded resources at runtime

Possibly, though if I went that route, I'd prefer IL fiddling

9 replies

CC#

•Created by zed on 6/20/2023 in #help

✅ Modify embedded resources at runtime

For future reference, in case anyone has this problem, I created a new dummy assembly with no code, and just use it as a target to write runtime embedded resources into - coupled with build order settings and one custom build step to assure the file exists and is copied to the output properly, this works for my needs...

9 replies

CC#

•Created by zed on 6/20/2023 in #help

✅ Modify embedded resources at runtime

That said, I found a stupid workaround, so this is kinda closed for me, at least to a point that I can live with it @.@

9 replies

CC#

•Created by zed on 6/20/2023 in #help

✅ Modify embedded resources at runtime

Thanks, but that wouldn't work in my case, because the third party component calls assembly.GetManifestResourceNames directly and uses that, so I would need to adjust it so that this function call includes the runtime data

9 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

Just for future reference, if anyone finds this - turns out it wasn't references anywhere and IIS just cached the files.... Deleting everything in the following two paths resolved the issue:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

Maybe my VS install is missing some workloads...

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

I saw that online, but I can't find that option anywhere

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

Thanks for all your help so far, but if you don't know how to proceed from here, I'm willing to just give up and find some other workaround x.x

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

Which still doesn't help me narrow down how it got there :(

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

So it seems it's part of the assemblies referenced in the current appdomain?

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

But this is the only part of the code that could explain it, and I see this in the debug window Locals

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

Sorry this is taking me so long >< This worked, that is a pretty great feature, thanks for telling me about it. It helped me narrow it down a bit further. I debugged the .NET WCF library in question, and I think it comes down to this code:

                            Assembly[] assemblies = AppDomain.CurrentDomain.GetAssemblies();
                            for (int i = 0; i < assemblies.Length; i++)
                            {
                                compiledType = assemblies[i].GetType(factoryType, false);
                                if (compiledType != null)
                                {
                                    break;
                                }
                            }

                            Assembly[] assemblies = AppDomain.CurrentDomain.GetAssemblies();
                            for (int i = 0; i < assemblies.Length; i++)
                            {
                                compiledType = assemblies[i].GetType(factoryType, false);
                                if (compiledType != null)
                                {
                                    break;
                                }
                            }

Unfortunately I can't be 100% sure, since my source mismatch is pretty wide. Not sure why, I downloaded the 4.8 reference source and tried to debug using that, but the file is nowhere close to the symbol information :\

50 replies

CC#

•Created by zed on 6/15/2023 in #help

✅ Resolving an ambiguous assembly reference

Did not know that was even a thing... I'll try it in a sec

50 replies

Gaming

Programming