Hello Brian Chavez,
In order to help you in the best possible way we need some more information regarding the issues you have experienced.
The 1st issue most probably occurs when Visual Studio fails to load the designer for a given component - in your case Telerik.Reporting.Report. The reasons may vary. If you have upgraded to a later version of Telerik Reporting your project may still reference the older assemblies. You have mentioned that you are building Telerik Reporting on your own - this can lead to incorrect versions of the needed assemblies as well.
To fix the issue, please, verify that you have installed the latest version
of Telerik Reporting correctly, and make sure you are using the right assemblies. For more information, please read Deploying Telerik Reporting on a Server
Regarding the 2nd issue - from the information you have provided we cannot say what the exact reason for the NullReferenceException is. Please, send us the exception's stack trace and your report so we can examine the filter that causes this trouble.
In order to build and debug the Telerik Reporting engine you have to sign all assemblies with your own key and replace all references to point to the new assemblies. This is the only way .NET runtime loads your assemblies. The same applies to the RESX files too. Since you replace all assemblies you should change this everywhere.
Regarding the last issue. From the screen shot it is not obvious why this assembly cannot be loaded. Please use the assembly binding log viewer
to examine the actual reason.
the Telerik team