Powerbuider11 c/s to B/S

I. Development Environment Installation
11 first install Windows iis5.0 or above
12. then install Asp.net Framework 2.0.
13 download (http://www.asp.net/iewebcontrols/download.aspx), install ie web control,
Decompress the package and run c: \ Program Files \ IE Web controls \ build. bat
Create c: \ Program Files \ IE Web controls \ build
Copy all files in c: \ Program Files \ IE Web controls \ build \ Runtime \ *. * to the IIS working directory.
The default value is C :\\ Inetpub \ wwwroot.
The copied doscommand is as follows:
Xcopy/S/I. \ build \ Runtime c: \ Inetpub \ wwwroot \ webctrl_client \ release 0/y
(Note: The webctrl_client \ Users 0 directory can also be manually copied)

1. Install iis5.0 or above for Windows
2. Install Asp.net Framework 2.0 again.
3. Download (http://www.asp.net/iewebcontrols/download.aspx), install ie web control,
Decompress the package and run c: \ Program Files \ IE Web controls \ build. bat.
Create c: \ Program Files \ IE Web controls \ build
Copy all files in c: \ Program Files \ IE Web controls \ build \ Runtime \ *. * to the IIS working directory.
The default value is c: \ Inetpub \ wwwroot.
The copied doscommand is as follows:
Xcopy/S/I. \ build \ Runtime c: \ Inetpub \ wwwroot \ webctrl_client \ defaults 0/y
(Note: You can also manually create and copy the webctrl_client \ 1_0 directory)
4. Download pb11(powerbuilder110.zip,commoninstaller.zip) and install pb11
After Uncompressing the file, use setup.exe in the commoninstallerfolder to install the file. When the installation is completed,
Select the folder to which powerbuilder110.zip is extracted to install the package correctly.
Ii. Convert the Pb of C/S Program B/S Program
1. First Port your program to pb11 and use pb11 to open the workspace and target. pb11 is automatically transplanted and debugging can run normally under C/SX.
2. The conversion starts. Choose File> new in the menu operation. Open [new] and select [target]-. NET web forms application.
Follow the wizard,
Step 1 Introduction to the wizard
Step 2 select use an existing library and Application Object
Step 3. Find your application object
Step 4 Add the PBL file you are using
Step 5 name the PBT file name. You can also go directly to the next step [next>].
Step 6 name the project object, or directly go to [next>]
Step 7 enter your virtual directory in IIS, or directly go to [next>]
Step 8 Add the resource file you are using
Step 9 if you use a third-party dynamic library DLL, add it here. If not, [next>]
Step 10 if you want to use JavaScript, add it here. I don't have it.
Step 11: The Web server you want to publish
Step 12 summarize your selection, [finish>]. The Great. NET web forms is created.
Release Step 13, deploy project. You just need to click a button. You just need to smoke, pour tea, and wait.
The release process is as follows:
Check whether your IIS service is available.
Generate the. NET Assembly File
Generate a PBD File
Copy files to the IIS server
Release completed.
Step 14 use IE to open your program (depending on your specific IP address and virtual directory) on another machine. After a long wait, the first time Asp.net runs, you need to compile it first and then hurry up next time.
Note: the final step is to put the files under c: \ Program Files \ Sybase \ PowerBuilder 11.0 \ DOTNET \ bin \
(1) Sybase. PowerBuilder. Ado. dll
(2) Sybase. PowerBuilder. Common. dll
(3) Sybase. PowerBuilder. Core. dll
(4) Sybase. PowerBuilder. datawindow. InterOP. dll
(5) Sybase. PowerBuilder. datawindow. Web. dll
(6) Sybase. PowerBuilder. datawindow. Win. dll
(7) Sybase. PowerBuilder. DB. dll
(8) Sybase. PowerBuilder. dbext. dll
(9) Sybase. PowerBuilder. editmask. InterOP. dll
(10) Sybase. PowerBuilder. editmask. Win. dll
(11) Sybase. PowerBuilder. graph. Core. dll
(12) Sybase. PowerBuilder. graph. InterOP. dll
(13) Sybase. PowerBuilder. graph. Web. dll
(14) Sybase. PowerBuilder. graph. Web. dll
(15) Sybase. PowerBuilder. InterOP. dll
(16) Sybase. PowerBuilder. RTC. InterOP. dll
(17) Sybase. PowerBuilder. RTC. Win. dll
(18) Sybase. PowerBuilder. Web. dll
(19) Sybase. PowerBuilder. WebService. runtime. dll
(20) Sybase. PowerBuilder. WebService. runtimeremoteloader. dll
(21) Sybase. PowerBuilder. WebService. WSDL. dll
(22) Sybase. PowerBuilder. WebService. wsdlremoteloader. dll
(23) Sybase. PowerBuilder. Win. dll

Copy these files to the bin directory under the B/S program directory you are converting. (After successful conversion, the main file directory is c: \ Inetpub \ wwwroot \ baoming \ bin)

Error:
1. generate C # syntax failure error when compiling generated C # code:
Download and install aspajaxextsetup. MSI
2. The name must start with an invalid character. An error occurred while processing the resource 'HTTP: // localhost. Row 1st, Location: 2
Solution:
1. In the XP system:
Open "start-Run" and enter (in blue) in the command line ):
C: \ winnt \ Microsoft. NET \ framework \ v2.0.50727 \ aspnet_regiis.exe-I
2. In the 2000 system:
Open "start-Run" and enter (in blue) in the command line ):
C: \ windows \ Microsoft. NET \ framework \ v2.0.50727 \ aspnet_regiis.exe-I
3. [Microsoft] [ODBC driver manager] No data source name found and default driver not specified
In "ODBC data source Manager", there are three DSN types used to connect to the database: User DSN, system DSN, and file DSN.
Because the Tomcat service started by monitor Tomcat runs as a system-level NT Service Routine (IIS should be the same), the "user data source" created by "User DSN" cannot be accessed ".
Change the data source to "system DSN"

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/mmmm90/archive/2009/08/12/4437605.aspx