Did you sing this little ditty when you were a wee laddie?  (In case you don't know the song, you can find the words and tune here (http://www.songsforteaching.com/folk/theresaholeinthebucket.htm). These words came to my mind after discovering a small hole in the migration process.  Let me describe it to you.

In the Classic PowerBuilder IDE, when you have classes in an inheritance relationship, the painter shows ancestor public and protected instance variable on the General tab of the descendent class.  Figure 1 shows what you might see when a Boolean ib_flag is declared in an ancestor.

If you go ahead and change the default value in the painter, the code is written into a special Type declaration section.  This code section is not directly developer accessible via a script editor.  In classic this is not an issue.  Figure 2 shows the source code

However, the script painter in the Visual Studio 12.x IDE, no longer shows you these inherited instance variables.  After migration to .NET 3.5 WPF the code remains in the Type declaration section, but there is not a painter interface to edit it.  Figure 3 shows the Type declaration section after migration.

A bit more concerning is the red herring that turns up when searching for the identifier.  Figure 4 shows you that the identifier if found.  However, double clicking it brings up the wrong location in the code.  The only way to edit the identifier is to Edit With à Source Code Editor.

I reported this issue to engineering.  Hopefully a later build will address this shortcoming.  Meanwhile as the song goes "With what should I fix it, dear Liza, with what?  With a straw, dear Henry, dear Henry, dear Henry"

Long Live PowerBuilder