shlomo abuisak personally, I'd remove everything that I don't use, my old Delphi dev env is super light on third party, I think only UniDAC, Virtual String Tree and delphi web script
It says it's loading PowerPDF when the exception is thrown. This looks like a problem with the design-time installation package. Run-time stuff usually has good backwards compatibility, but IDE design-time stuff can be rather brittle. Just a small change to the RTTI methods or how the IDE accesses stuff can cause things to break.
Динар Шарифуллин Actually it's likely a Delphi Seattle package if the developer is following the same covention suggested by the documentation. Look at the far right column in the table.
does it always happen when AlphaControls is loaded?
ReplyDeleteI guess . I thought to take off bpl alpha control. Am i correct ?
ReplyDeleteI think you need to check PowerPDF rather than Alpha unless it is part of Alpha controls.
ReplyDeleteshlomo abuisak personally, I'd remove everything that I don't use, my old Delphi dev env is super light on third party, I think only UniDAC, Virtual String Tree and delphi web script
ReplyDeleteJohn Kouraklis It was the PowerPDF that did it but why ?
ReplyDeleteshlomo abuisak Is PowerPDF part of Alpha Controls?
ReplyDeleteJohn Kouraklis NO
ReplyDeleteLooks like the PowerPDF file is for XE2.
ReplyDeletejeff weir you mite be right
ReplyDeleteIt says it's loading PowerPDF when the exception is thrown. This looks like a problem with the design-time installation package. Run-time stuff usually has good backwards compatibility, but IDE design-time stuff can be rather brittle. Just a small change to the RTTI methods or how the IDE accesses stuff can cause things to break.
ReplyDeletejeff weir, most likely right. Delphi Conditional version for XE package should have the suffix 220.bpl. http://docwiki.embarcadero.com/RADStudio/Berlin/en/Compiler_Versions In this case, there is an attempt PowerPDFD230.bpl download.
ReplyDeletedocwiki.embarcadero.com - Compiler Versions - RAD Studio
Динар Шарифуллин Actually it's likely a Delphi Seattle package if the developer is following the same covention suggested by the documentation. Look at the far right column in the table.
ReplyDeleteIf we are talking about Delphi XE, then the package suffix must be 150, not 220 or 230.
ReplyDelete