Big program upgrading from v16 to v17

Big program upgrading from v16 to v17

Posted by: mpeterson on 2 April 2023, 8:14 am EST

• 

  mpeterson

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 2 April 2023, 8:14 am EST

  I have a class library - .NET Standard 2.0 - that contains all my section-based reports. I have a .NET Framework 4.7.2 project as a companion project that I use to edit the report files using the visual designer as needed via linked files (per a recommendation posted here). The report library is accessed by .NET core projects and thus has to remain a .NET Standard library.

  I installed ActiveReports v17 and used the menu option ‘Convert to ActiveReports 17’. Big mistake. The conversion tool switched the my project type from .NET Standard 2.0 to .NET framework 4.6.2. I don’t even have that version of the framework installed. I closed the project and manually edited the project file to switch it back to .NET Standard 2.0. However, now when I open the project and try to compile, I get 3600+ errors.

  I can obviously revert back to AR 16 - but how the heck am I supposed to upgrade all these reports to AR 17 without things breaking?

• 

  mpeterson

  • Post Options:
  • Link
    Copy

  Posted 2 April 2023, 8:29 am EST

  Disregard. For some reason, the ARConverterBackup folder was added to the project, so it was seeing all sorts of duplicate references. Once I excluded it from the project, everything compiled correctly.

• 

  akshay.rajput

  

  • Post Options:
  • Link
    Copy

  Posted 2 April 2023, 7:45 pm EST

  Hi Mark,

  Apologies for the inconvenience. Glad to know that the issue is resolved. And thanks for sharing your solution with us as will help other doing something similar.

  As for the .Net version switch from .Net 2.0 to .Net 4.6.2 issue, I wasn’t able to reproduce it. I created a project using .Net Class Library .NET 2.0 and added an ActiveReports Section Reports 16 WinForms Project(using ActiveReports Project Templates).
  
  Then, I used the Upgrade tool and the .Net 2.0 version of the Class Library project stayed the same.

  However, for future I would recommend you to only load the project you want to use the Upgrade Tool on by Loading the .csproj or the .vbproj file in Visual Studio instead of loading the whole solution(.sln) To avoid using the convert tool on all the projects unintentionally.