RockWallaby

Here's another example. I get this error message whenever I click the expand toggle.

Thank you for the suggestion. I did search for "DotNetForm" but nothing was found. If I create a new project with no components the error still persists, so it seems to me to be something wrong with the IDE itself rather than a dproj file. I would have thought reinstalling RAD Studio would fix the problem but unfortunately it didn't. They only thing I can think of is to have it remove all registry entries on the uninstall, but I'm hesitant to do that as reinstalling all of the components will be a big job and I might still end up with the same problem.

Yeah that didn't work either.

Thanks. I'll give that a try.

Thanks. I'll investigate further. I contacted Ray about CodeSite and he thought that the RAD Studio installation may have become corrupted. So I completely uninstalled it and then reinstalled it, but it made no difference.

I'd like to know too! It suddenly started happening and no matter what I do, I can't seem to resolve it. Surely we're not the only two in the world to be experiencing this.

Thanks for the suggestions. I uninstalled GExperts, EurekaLog and CNPack. No difference. = Steve

Hi, I have suddenly started having strange issues with RAD Studio 10.2.3 after years of it working fine. For example, if I select Tools/CodeSite/CodeSite Method Tracer it works fine the first time. But if I do it a second or more times, the following error is displayed: "A component named MethodTracerForm already exists." Some other options in RAD Studio act in a similar way, displaying messages like: "A component named DotNetForm already exists". I then have to restart the IDE before I can access these options, which then act the same way again. It looks like the IDE may not be releasing the forms. This is what I have done to try to resolve the issue: Uninstalled and reinstalled RAD Studio (several times). Repaired the Windows registry. Scanned the system files for errors or corrupted files. Ran complete hardware tests (eg. hard drives, memory, etc.). Repair .Net files. Has anyone come across anything like this before? Thanks. = Steve