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 from
PowerBuilder Classic:
- For .NET Web Forms and .NET Web Service targets, install AJAX extensions on development computers and production servers.
You can download and install the Microsoft AJAX Extensions version 1.0 from the Microsoft Web site at http://www.microsoft.com/downloads/details.aspx?FamilyID=ca9d90fa-e8c9-42e3-aa19-08e2c027f5d6.
- 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 PowerBuilder 12.0 runtime files using the Runtime Packager or another tool, as described in the “Checklist for deployment” section of the Deploying Applications and Components to .NET book.
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.