• You are here:  
  • Home
  • Q&A
  • Q&A
  • Beta Testing
  • Issue during the migration to a solution (PB2025 BETA)

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Issue during the migration to a solution (PB2025 BETA)

  1. New
  2. Issue
0
Votes
Undo
  1. Christophe Feyte
    Christophe Feyte
  2. Beta Testing
  3. Friday, 18 October 2024 12:15 PM UTC

Hello,

We succesfully test a migration of our biggest application from PB2022 Build 1892 to PB2025 Beta Build 3398 (41 PBLS and 4300+ objects).


Snce we are interested in the faster compilation of the code with the new compiler we tried to convert the workspace into a solution but we got the following error for a lot of objects => Fatal C0246: Exception occurred while generating syntax tree.
We don't know what that means.


If we try to do the incremental build or full build or powerscript build of the solution, the errors are still the same but on different objects.

 

Any ideas ?

  1. Migration
PB 2025 PBNative source control (unsupported?)
Use of PBD files in Solution mode
Accepted Answer
Peter Pang @Appeon
Peter Pang @Appeon Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 01:34 AM UTC
  2. Beta Testing
  3. # Permalink

Hi Christophe,


Thank you for your time in trying the PB 2025 beta!
This is a known issue, please refer to: https://docs.appeon.com/pb/release_bulletin_for_pb/Build-3398-Known-Issues.html#gsc.tab=0

The installation for the new version of Visual Studio (Version 17.11.x) may cause the Solution's Full Build to fail, with the error message C0246: "Exception occurred while generating syntax tree." To workaround this issue, rename the following file: C:\ProgramData\Microsoft\VisualStudio\Setup\x86\Microsoft.VisualStudio.Setup.Configurât ion.Native.dll.


Best Regards,
Peter

Comment
Christophe Feyte
  1. Christophe Feyte
  2. Monday, 21 October 2024 13:19 PM UTC
Hi, I did this and it worked.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 21 October 2024 19:19 PM UTC
Thanks for confirming!
  1. Helpful
There are no comments made yet.
Responses (4)
Arthur Hefti
Arthur Hefti Accepted Answer Pending Moderation
  1. Sunday, 20 October 2024 04:08 AM UTC
  2. Beta Testing
  3. # 1

Hi

I had the same problem. Check out if this helps: 

https://docs.appeon.com/pb/release_bulletin_for_pb/Build-3398-Known-Issues.html#gsc.tab=0

Regards
Arthur
Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 18 October 2024 20:14 PM UTC
  2. Beta Testing
  3. # 2

I submitted a bug on this same issue.

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 18 October 2024 17:58 PM UTC
  2. Beta Testing
  3. # 3

Hi Christophe;

  I have converted some Apps in the 2-3K object range to a solution but did not encounter any such issues. Make sure that you ...

  • Migrate your App into a 2025 Workspace first
  • Make sure that there are no protected folders or files in the WS area.
  • Perform a full WS build and also ensure that there are no App errors or warnings.
  • Copy the PB 2025 WS folder "as is" over to a new folder for the solution testing
  • Make sure that there are no protected folders of files in the Solution area.
  • Start the PB 2025 IDE and then open the Solution folder's WorkSpace
  • Now perform the WS => Solution conversion.

The above process is what I have been doing with no direct migration issues thus far.  HTH

Regards .. Chris

 

Comment
Christophe Feyte
  1. Christophe Feyte
  2. Monday, 21 October 2024 12:24 PM UTC
Hello, I tried this and it didn't work unfortunately.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 21 October 2024 13:30 PM UTC
Hi Christophe;

In that case, please open a Support ticket for this issue so that Engineering can try to see what any underlying issues are with your app that might be causing this.

Regards ... Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.