When you migrate older Web Forms applications and .NET Web Service components, you might need to remove or install supporting files on development and deployment computers.
If you deployed .NET projects from earlier versions of PowerBuilder,
verify or complete the following steps before redeploying the migrated .NET projects:
- For .NET Web Forms and .NET Windows Forms projects, select “Full”
for the project rebuild type before you redeploy your applications from PowerBuilder Classic for the first
time.
- For .NET Web Forms and .NET Web Service targets, clear ASP.NET
temporary files for the application or component on development computers and
production servers.
The temporary files are located in the
C:\WINDOWS\Microsoft.NET\Framework\version\Temporary ASP.NET Files\projectName
directory, where version is
typically v2.0.50727, and projectName is
the project’s Web application name or its Web service virtual directory
name.
- For all .NET targets, uninstall earlier versions of PowerBuilder
runtime files (system assemblies and win32 DLLs) on all deployment computers or
servers, then install the runtime files for the current version of PowerBuilder
using the Runtime Packager or another tool, as described in the “Checklist for
deployment” section of the Deploying Applications and
Components to .NET book.
- To migrate a PowerBuilder 12.0 or 12.1 solution, open its
.PBWX file using the File menu. If you double-click or
drag and drop the file into PowerBuilder .NET 12.5, the Visual Studio Conversion
wizard opens, inappropriately. You can use the double-click and drag-and-drop
methods to open PowerBuilder 12.5 solutions.
Note: You can convert .NET Windows Forms targets to WPF targets in
PowerBuilder .NET. Sybase suggests that you migrate older .NET Windows Forms targets to
PowerBuilder Classic before you convert them to WPF targets.
You cannot directly convert .NET Assembly targets in PowerBuilder Classic to .NET Assembly targets in PowerBuilder .NET.