VS 2022 uses a new designer so many older controls don't work with it. In your case what you're seeing is that the designer doesn't recognize the older control is displayable so it puts it at the bottom as a component. You can still right-click and access the properties of the control as you would normally but it doesn't render on the form.
This is a known issue. Part of the issue could be your reliance on the Corrected
Nuget package which is not from MS. If you don't need this package then remove it. Additionally if you are building a .NET 6+ app or if you are building .NET Framework 4.x app with a packages.config
file then you may run into issues. The Toolbox may not properly add the correct component.
One recommendation to work around this, and it only works for .NET Framework with packages.config
is to Choose Items
in the Toolbox, browser to where the Nuget package is (it'll be under the packages
folder of your solution) and then add it to the Toolbox again. This seems to solve the issue for some people.
Alternatively, or if that doesn't work then drag and drop a panel onto your form where you want the report to go. This will give you the location and size information you need. You can then edit the properties of the report control (from the component drawer) to render in that location at runtime. It isn't ideal but it works.
As for hooking up your RDLC to the report viewer you need to set the LocalReport property. Since you are building a local report you generally do the actual assignment at runtime but you could also set the nested properties (specifically the report path) in the designer if you wanted to.