I taught a full day .NET seminar to an ISUG group in Minneapolis today. 19 developers attended. During the migration unit I demo'd and showed how mapped custom events, not on the control supported list, are migrated BUT, during compile, do not generate a warning. Even worse at runtime they are never invoked. The implication is that important GUI code is migrated but will never be invoked! I pointed out to the seminar attendees, that this is a potentially big hole in the migration/build process. I also mentioned that the only way I know of to detect non-functioning mapped events was through thorough your code testing. Of course, those who read the documentation before migrating will have a heads up. The online book "PowerBuilder .NET Features Guide", chapter titled "Scripts and Code Fundamentals", section titled "Supported Custom Events" documents has a table listing PowerBuilder event IDs for custom events supported in PowerBuilder. Even so, you need a way of detecting these custom mapped events in your code

One of the developers in the room suggested searching the target for pbm_. After all, event IDs would not be in the source code unless they were explicitly mapped onto.

Figure 1 shows what I did:

Figure 2 shows the result:

Figure 3 shows the same result in the .NET IDE:

What’s left to be done is to compare the results list against the supported event list in the PowerBuilder documentation and address only the no longer supported events, discovering the import of not having them and finding XAML equivalents.

• SANpulse VIP Executive Roundtable Reveals Trends in Storage Migration and Infrastructure Consolidation
• RoundTable Healthcare Partners Raises $500 Million for Second Private Equity Fund
• Wheels, Inc. Joins Panel Discussion at IARA Remarketing Roundtable