Could Not Load File Or Assembly

I'm getting this exception in designer code for one case. The file it can't load is System.XmlSerializers.

This has no impact on anything, and since I don't write Settings.Designer.vb, this is code generated by VS, and they appear to deal pretty well with this exception, and the program runs fine. The code that throws this exception is this:

Code:

---

            Get
                Return CType(Me("FishTips"),Global.System.Collections.Specialized.StringCollection)
            End Get

---

Which is just the getter of a setting.

So, if the program runs, and this exception isn't causing me any trouble, why am I asking, and what am I asking for? Well, this is a nuisance. If I break when exceptions are thrown by the runtime, which is pretty useful, at times, then the program always halts on this exception when it is thrown, because it is thrown every time the program starts. It's a very minor nuisance, but I thought I might ask in here to see whether anybody has a solution.

In the short term, I can turn off breaking when that type of exception is thrown, because that type of exception is very unlikely to be thrown from anything else in the program. However, exceptions tend to take a noticeable amount of time to process. Sure, it's a BARELY noticeable amount of time, but the startup on this program, which has to do a LOT of initialization of graphics and the like, is already pretty slow, so I sure don't need to have more.

Is there a way to avoid having this exception even thrown?

To be honest I never deal with this in VS or at least I can't recall but what I have deal with was lovable Devexpress and Telerik assembly issues mostly old files left to the assembly case. I used Gacutil to remove - add although maybe it could be done simpler if you navigate to the assembly folder(?) not sure, gacutil is fine.
https://docs.microsoft.com/en-us/dot...embly-into-gac .
Having said that and seen how many issues you reported lately with VS, I would have just uninstalled and re-installed the damn thing. Not repair, just remove everything and start fresh. Hope you don't execute me if you decide to go into that much trouble and the issue stay. :eek:

Nope, not doing that for something so insignificant, especially since I don't think it will actually help anything.

Considering how the code is working, I'm not sure that this exception is actually meaningful. VS sometimes does that, where an exception is the way the indicate something reasonable. They appear to be catching the exception and going on to do the right thing, it's just a bit annoying that they are doing it that way.

I know I could change this, because it has to do with the Specialized.StringCollection. If the setting were turned into a string, which it could be with a modest amount of work, the exception would go away.