ASP.NET/Perl.NET 数据库访问例子_Asp.Net开发
日期：2009-12-13 浏览次数：20546 次
ASP.NET/Perl.NET Database Access Example
One of the features of the .NET framework is its ability to handle multiple languages. Third party compiler vendors can create and implement a compiler targeted for the .NET runtime. In fact, over the course of the next year, you can expect to see some 28 languages ported to the .NET runtime. This will allow companies with a huge codebase in a "non-Microsoft language" to continue building onto their investment.
NOTE: All of the software required to create and run ASP.NET pages built using PERL.NET can be downloaded here.
Here is the code for the whole page (we will dissect and explain each bit of the code throughout the rest of the article):
<%@ Page
Language="Perl" %>
<script runat="server">
use namespace "System::Data";
use namespace "System::Data::SqlClient";
=for interface
protected override void OnLoad(System.EventArgs e);
=cut
sub OnLoad {
my($this, $e) = @_;
my $myConnection = SqlConnection->new("Data Source=(local); Trusted_Connection=Yes; Initial
Catalog=pubs");
my $myCommand = SqlCommand->new("Select * From Publishers", $myConnection);
$myConnection->Open();
$this->{myDataGrid}{DataSource} = $myCommand->ExecuteReader(PerlNET::enum
("CommandBehavior.CloseConnection"));
$this->{myDataGrid}->DataBind;
}
</script>
<html>
<body>
<form runat="server">
<asp:DataGrid id="myDataGrid" runat="server" />
</form>
</body>
</html>
We need to set the Language attribute (in our declaration) equal to 'Perl'. We do this so it is clear to the .NET runtime exactly which compiler it must invoke. The following code accomplishes this task:
<%@ Page
Language="Perl" %>
Now, we need place all of our PERL.NET code inside <script runat="server"</script> blocks just as we would if we were using VB.NET or C#. Here is where you will notice one (there are more) difference between VB.NET/C#/JScript.NET and PERL.NET pages. In PERL.NET, rather than using Import declarations outside of the <script> blocks the code that imports the required namespaces is placed inside the <script> blocks. This code uses the following syntax:
use
namespace "System::Data";
use namespace "System::Data::SqlClient";
We want code to execute each time the page is loaded so we must explicitly define our OnLoad event in order for the page to recognize it. The following code accomplishes this task:
=for interface
protected override void OnLoad(System.EventArgs e);
=cut
Note: All events in the page must be declared using code similar to that above. Also, all interface declarations must be flush left on the page (ie '=for interface' must start in the left most column on the page).
Next, we declare our OnLoad event. The following code declares the OnLoad event and places any arguments into the scalar variables $this and $e:
sub OnLoad {
my($this, $e) = @_;
So, we have declared our OnLoad event and now we need to write the code to be executed in the event. The code in our example connects to a SQL Server database and retrieves information in the form of a DataReader. First, we will examine the code that connects to SQL Server and selects the desired information.
my $myConnection = SqlConnection->new("Data
Source=(local); Trusted_Connection=Yes; Initial Catalog=pubs");
my $myCommand = SqlCommand->new("Select * From Publishers", $myConnection);
$myConnection->Open();
'my' declares variables to be local to the enclosing block - in our case the OnLoad event. In PERL.NET, we call an object's methods using this syntax: Object->MethodName.
Ok, we have created the necessary objects and opened our connection to SQL Server. The variable $this contains a r
One of the features of the .NET framework is its ability to handle multiple languages. Third party compiler vendors can create and implement a compiler targeted for the .NET runtime. In fact, over the course of the next year, you can expect to see some 28 languages ported to the .NET runtime. This will allow companies with a huge codebase in a "non-Microsoft language" to continue building onto their investment.
NOTE: All of the software required to create and run ASP.NET pages built using PERL.NET can be downloaded here.
Here is the code for the whole page (we will dissect and explain each bit of the code throughout the rest of the article):
<%@ Page
Language="Perl" %>
<script runat="server">
use namespace "System::Data";
use namespace "System::Data::SqlClient";
=for interface
protected override void OnLoad(System.EventArgs e);
=cut
sub OnLoad {
my($this, $e) = @_;
my $myConnection = SqlConnection->new("Data Source=(local); Trusted_Connection=Yes; Initial
Catalog=pubs");
my $myCommand = SqlCommand->new("Select * From Publishers", $myConnection);
$myConnection->Open();
$this->{myDataGrid}{DataSource} = $myCommand->ExecuteReader(PerlNET::enum
("CommandBehavior.CloseConnection"));
$this->{myDataGrid}->DataBind;
}
</script>
<html>
<body>
<form runat="server">
<asp:DataGrid id="myDataGrid" runat="server" />
</form>
</body>
</html>
We need to set the Language attribute (in our declaration) equal to 'Perl'. We do this so it is clear to the .NET runtime exactly which compiler it must invoke. The following code accomplishes this task:
<%@ Page
Language="Perl" %>
Now, we need place all of our PERL.NET code inside <script runat="server"</script> blocks just as we would if we were using VB.NET or C#. Here is where you will notice one (there are more) difference between VB.NET/C#/JScript.NET and PERL.NET pages. In PERL.NET, rather than using Import declarations outside of the <script> blocks the code that imports the required namespaces is placed inside the <script> blocks. This code uses the following syntax:
use
namespace "System::Data";
use namespace "System::Data::SqlClient";
We want code to execute each time the page is loaded so we must explicitly define our OnLoad event in order for the page to recognize it. The following code accomplishes this task:
=for interface
protected override void OnLoad(System.EventArgs e);
=cut
Note: All events in the page must be declared using code similar to that above. Also, all interface declarations must be flush left on the page (ie '=for interface' must start in the left most column on the page).
Next, we declare our OnLoad event. The following code declares the OnLoad event and places any arguments into the scalar variables $this and $e:
sub OnLoad {
my($this, $e) = @_;
So, we have declared our OnLoad event and now we need to write the code to be executed in the event. The code in our example connects to a SQL Server database and retrieves information in the form of a DataReader. First, we will examine the code that connects to SQL Server and selects the desired information.
my $myConnection = SqlConnection->new("Data
Source=(local); Trusted_Connection=Yes; Initial Catalog=pubs");
my $myCommand = SqlCommand->new("Select * From Publishers", $myConnection);
$myConnection->Open();
'my' declares variables to be local to the enclosing block - in our case the OnLoad event. In PERL.NET, we call an object's methods using this syntax: Object->MethodName.
Ok, we have created the necessary objects and opened our connection to SQL Server. The variable $this contains a r
免责声明： 本文仅代表作者个人观点，与爱易网无关。其原创性以及文中陈述文字和内容未经本站证实，对本文以及其中全部或者部分内容、文字的真实性、完整性、及时性本站不作任何保证或承诺，请读者仅作参考，并请自行核实相关内容。
