Can't update VS 2017 to FR 2017.3.16.0 without compile err
Working project ... Updated project from VS2015 to VS2017 ... everything was fine. Updated Fast Reports from 2016.4.0.0 to 2017.3.16.0 ... Now on first compile program runs. If I change anything in the designer ( move a control, add a control, rename a control. any control ) I receive an error 'Object reference is not set to an instance of an object' and the project fails to compile. The project contains multiple Preview Controls as well as multiple report controls. The error seems to be caused by a Fast Report version or control mismatch.
The Project Properties References list the NEW FastReport DLL's and the new version controls show in the toolbox as they should. I have tried deleting ALL instances of the old DLL files. I have placed the NEW DLL version files in the project folder and made SURE that the project referenced the new DLL's. I have tried replacing the controls on the forms with the new versions. None of this will rectify the error.
IF I PUT BACK THE 2016.4.0.0 VERSIONS OF THE DLL FILES AND SET THE PROJECT REFERENCES TO THEM THE ERROR GOES AWAY.
I can't figure out how to update my existing project to the new version of FastReports.net.
WHAT IS THE PROCEDURE for updating VS and a project with the new version of Fast Reports to eliminate this problem?
Thanks to anyone who has the answer.
The Project Properties References list the NEW FastReport DLL's and the new version controls show in the toolbox as they should. I have tried deleting ALL instances of the old DLL files. I have placed the NEW DLL version files in the project folder and made SURE that the project referenced the new DLL's. I have tried replacing the controls on the forms with the new versions. None of this will rectify the error.
IF I PUT BACK THE 2016.4.0.0 VERSIONS OF THE DLL FILES AND SET THE PROJECT REFERENCES TO THEM THE ERROR GOES AWAY.
I can't figure out how to update my existing project to the new version of FastReports.net.
WHAT IS THE PROCEDURE for updating VS and a project with the new version of Fast Reports to eliminate this problem?
Thanks to anyone who has the answer.
Comments
Following the guide solved the problem. Specifically, steps 1-7.