I have a handful of ASP.NET Webforms I need to start converting to ASP.NET Core Razor pages.
Below I have an example on how one of these pages currently operates to give an idea of what I am working with, but I am unsure on where to even begin with converting this all to Razor pages. I am open to other solutions
HTML
<input type="search" class="form-control" placeholder="Enter Device Name or Number" id="searchval" />
<div class="input-group-append">
<button class="btn btn-primary" type="button" onclick="search()"></button>
<span id="number"></span>
<span id="name"></span>
<span id="model"></span>
JavaScript
function search() {
var device = $('searchval').val();
$.ajax({
url: "postback.aspx",
data: {
ftn: 1,
val: device
},
success: function (data) {
var splitdata = data.split(";");
var number = $.trim(splitdata[0]);
var name = $.trim(splitdata[1]);
var model = $.trim(splitdata[2]);
$("#number").text(number);
$("#name").text(name);
$("#model").text(model);
}
});
}
postback.aspx.cs
C#
protected void Page_Load(object sender, EventArgs e)
{
String Function = Request.QueryString["ftn"];
switch (Function)
{
case "1":
Search();
break;
default:
break;
}
}
public void Search()
{
string value = Request.QueryString["val"];
string sqlstring = /*connection string here*/;
SqlConnection con = new SqlConnection(sqlstring);
con.Open();
string qry = /*stored procedure using value*/
SqlCommand cmd = new SqlCommand(qry, con);
using (SqlDataReader sdr = cmd.ExecuteReader())
{
while (sdr.Read())
{
string number = sdr.["devnumber"].ToString();
string name = sdr.["devname"].ToString();
string model = sdr.["devmodel"].ToString();
Response.Write(number);
Response.Write(";");
Response.Write(name);
Response.Write(";");
Response.Write(model);
}
}
con.Close();
}
I’m pretty new to ASP.NET Core Razor pages and have done the documented tutorial from Microsoft, but I am just struggling on how to apply that to converting this current app I am working with.
J. Rent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3