This is followed by the main function to display a fixed number of user messages (the value retrieved from the administrative settings table):

<% Sub Show NumPerPage=INT(objRec2("NumPerPage")) If Request.QueryString("page") = "" Then iPageCurrent = 1 Else iPageCurrent = CInt(Request.QueryString("page")) End If Set objRec = Server.CreateObject ("ADODB.Recordset") StrSql = "SELECT * FROM Messages ORDER BY ID DESC;" objRec.PageSize = NumPerPage objRec.CacheSize = NumPerPage objRec.Open StrSql,objConn,3,1,&H0001 iPages = objRec.PageCount TotalRows = objRec.RecordCount If iPageCurrent >iPages Then iPageCurrent = iPages If iPageCurrent< 1 Then iPageCurrent = 1 If iPages = 0 Then Response.Write "Не найденно записей!" Else ObjRec.AbsolutePage = iPageCurrent %>

"color="<%=objRec2("PageFontColor")%>"size="<%=objRec2("PageFontSize")%>"> Total in the book <%=TotalRows%> entries on <%=iPages%> page(s)

"> "color="<%=objRec2("InfoFontColor")%>"size="<%=objRec2("InfoFontSize")%>"><%=ObjRec("DateID") %>		"> "color="<%=objRec2("InfoFontColor")%>"size="<%=objRec2("InfoFontSize")%>">Site rating: .gif" height="14" width="65">
"> "color="<%=objRec2("MessageFontColor")%>"size="<%=objRec2("MessageFontSize")%>"><%=FormatStr(ObjRec("Message"))%>
"> "color="<%=objRec2("InfoFontColor")%>"size="<%=objRec2("InfoFontSize")%>"> <% If IsEmpty(Email) or Email=" " then Response.Write Name Else Response.Write "" & Name End If %>	"> "color="<%=objRec2("InfoFontColor")%>"size="<%=objRec2("InfoFontSize")%>"><%=FormatStr(ObjRec("Country")) %> IP:<%= ObjRec("IP") %>	"> "color="<%=objRec2("InfoFontColor")%>"size="<%=objRec2("InfoFontSize")%>"> <%=Link%>

"color="<%=objRec2("PageFontColor")%>"size="<%=objRec2("PageFontSize")%>"> Pages: <% For I = 1 To iPages If I = iPageCurrent Then Response.Write ""&I&"" Else Response.Write " "&I&"" End If Next Response.Write "" Else Response.Write " " End If End If objRec.Close Set objRec = Nothing End Sub %>

Pay attention to how the link to view the next page with such a “portion” of messages is formed and implemented:

Response.Write" "&I&" "

As you can see, the page number is passed to it as the value of the page parameter, and subsequently, if this value is not equal to 1, the display of messages does not start from the first message, but from the one that will be the first in the account on the page with the corresponding number specified in the parameter:

<% NumPerPage=INT(objRec2("NumPerPage")) If Request.QueryString("page") = "" Then iPageCurrent = 1 Else iPageCurrent = CInt(Request.QueryString("page")) End If %>The source text of the module itself follows, in which the connection to the database is made and records are retrieved (in the described example, this will be the only record) from the Admin administrative settings table:<% Set objConn = Server.CreateObject ("ADODB.Connection") objConn.Open StrConn Set objRec2 = Server.CreateObject ("ADODB.Recordset") ConfigSql = "SELECT * FROM Admin;" objRec2.Open ConfigSql,objConn,0,1,&H0001 %>

Then you can style the title and main tags of the HTML page:

Conclusion

We considered one more functional component of the site, and immediately made it portable. The result of this was a rather complex source code in terms of perception. Although a large number of parameters retrieved from the administrative table made it somewhat more difficult to understand the source code of the module, however, using them once and for all will save you from having to edit the code when they change. The system developed by us is quite acceptable in use, and thanks to the modularity of its implementation and the approach to its implementation in existing sites described in the article, it can be used as a guest book on a site of almost any degree of complexity.

Of course, the Web interface for editing, adding and deleting administrative settings (schemes) should also be considered, but this will take a lot of time, and therefore the author will try to cover it in one of the following parts of this article.

ComputerPress 11 "2001

Registration of controls is carried out by the @Register directive, which allows you to use user controls and server controls in the HTML code of the page using a special syntax (declarative custom server control syntax). Based on the analysis of these directives, the page parser can associate tags with given types and, when creating a page, embed controls already as containers of custom types - branches of the page's control tree.

Directives must precede the first use of the declared tags, more often they are placed at the beginning of the page and in the case of registering several controls, in sites with a modular structure, the number of such declarations can occupy a large number of lines. When you change the location of controls, you have to look for lines that require changes in the code of all pages and user controls on which they are registered, which is rather inconvenient.

The article describes a method that simplifies the registration of controls.

For the registration directives, we will use a plain text file in which we will collect all the @ Register directives. Since virtual paths can be used to declare user controls, and only namespaces are specified for server controls, we can collect all the links we need in this file, and the links to the ascx files will be correct for any folder in the project. Here is what this file looks like in one of the projects:

Let's name the file register.inc and place it in the /inc folder of our web project.

This file will contain all the links we need, we will add or change the registration of a user or server control in it.

Now the created file needs to be somehow included in the page code. We do this with the SSI (server side includes) #include directive. This directive allows you to include static and dynamic files in the page code, processing them based on IIS mapping, i.e. specifying an asp or aspx file as the source will cause the file to be processed by the appropriate process and copy the results of this processing to the output page. In ASP, the #include directive was very widely used and allowed for the modularization of the site. With the advent of ASP.NET, it has become more convenient to do this in other ways, for example, using user controls. Future versions of ASP.NET will implement modularity using master pages. In general, the #include directive lost its meaning and was kept mainly for backward compatibility and to simplify the migration of ASP projects to .Net.

Since we have a simple text file, no processing will be done, and before any dynamic content is executed, the entire contents of the file will be copied into the page code. Those. adding our register.inc file to the top of the page, for example, is almost the same as writing all the @Register directives there.

In order not to depend on the physical location of the file, we again use the virtual path syntax and add the following line to the aspx file code:

Make sure everything works, if not, correct the wrong paths.

It remains to carry out one more operation. Now, if you try to get the /inc/register.inc file from the link in your browser, you can easily do it. IIS puts it in your hands, as well as in the hands of an attacker, completely free, although it contains the paths of the physical structure of your site.

To prevent this from happening, we use the capabilities of the synchronous HttpForbiddenHandler handler, which allows us to protect files of a certain type from being issued at the request of the user. This approach is convenient and is often used, for example, to protect MS Access database files used in a project. In order for files with the *.inc extension to be protected using this handler, you need to tell IIS that these files will be processed by the ASP.NET process, in other words, configure IIS to map to files of this type.

For a detailed description of the configuration process for IIS, see HOW TO: Use ASP.NET to Protect File Types (http://support.microsoft.com/kb/815152/EN-US/). We need to create a mapping only for *.inc files. After completing the steps described there, all requests for files with this extension will be processed by the ASP.NET process, and you will have to edit the web.config file as follows:

That's it, now when trying to get the /inc/register.inc file via a direct link, the user will receive error B.

In order not to register aspnet_isapi.dll, for example, your provider does not want to do this, you can use the SSI ability to specify files of any type and cheat by using an extension of one of the types already mapped in IIS by default for a file with @Register directives. *.cs or *.vb extensions will be convenient for this. These files contain source code and are usually not copied to the server. If you suddenly made a mistake and copied, you won’t be able to get them at the request from the browser - when you try to do this, the user will receive an error B. This happens because mapping in IIS is configured by default for files of this type and the corresponding extension is already registered in the section machine.config file. In Visual Studio, in order for the compiler not to give you an error message, put an extension that the compiler is not interested in: in C# projects it is *.vb, in VB projects it is *.cs.
Conclusion

The described method allows you to register controls in one place for the entire project. Subsequent modification of this file requires less effort than if you had to do it in the usual way. Try using SSI #include inside the files you insert - this allows you to organize a kind of hierarchy and inheritance, which can be convenient for large projects

Directives in AngularJS play an important role. Directives can be used to teach new tricks to HTML, and you can even create your own HTML tags or attributes. Directives also help in keeping the mark-up more fluent and defines a nice way of separating code and mark-up from each other.

View is an HTML template. View is nothing but the information you want to render to the end user's browser. A view in AngularJS is also called as compiled DOM. View makes use of directives to render the data with HTML template.

This article is Part IV of the Project Tracking Website built in AngularJS and ASP.NET Web API. So far, we have , created a , and have .

Thanks to to review this Angular series and fix the bugs.

We have already seen the $scope object which provides a Model to the View. Model code is not intermixed with the HTML code we write into our views. Rather, data is moved from the model to views by using data binding expressions. This way developers can achieve Separation of Concerns (SoC). Since Models are independent of Views, they can be bound to any View. This binding of model is done with the help of AngularJS Directives.

We have already seen some Angular directives in our like ng-app which bootstraps AngularJS, as well as ng-controller that makes the controller available to HTML. From the controller, we can bind the data to the views using Angular ((expression)).

In this article, we will look at a couple of additional AngularJS directives which come out-of-the-box with Angular. One of them is ng-repeat. Let's try using ng-repeat directive into our EmployeeDetails.html page that can be found in the accompanying this article. Modify the service URL in our EmployeesController.js file. The service URL is as follows:

http://localhost:2464/api/ptemployees

Now we will modify the EmployeeDetails.html page as shown in following code -

((emp.employeeID)) ((emp.employeeName)) ((emp. designation)) ((emp.contactNo)) ((emp.eMailID)) ((emp.skillSets))

Replace the of EmployeeDetails.html page with above code. The output of the above code is shown here:

In this code, we have used the ng-repeat directive of AngularJS. It is similar to the for or foreach loop in .NET. Here we are getting an IEnumerable collection using ASP.NET Web API. We are using this collection as a model in our Angular Controller. Using this model, we are iterating the objects of employees, into our view. This is a very helpful directive which repeats through the objects in the collection to display the data on the view.

Now let's try adding a filter to search a particular Employee from the collection and display the employee based on given Employee Name or Employee Name character. Till now, we have fetched the model and used it in our Views. It also works the other way. We can make our views talk back to our models which are there in our controllers.

To add a search filter based on Employee Name, we will modify the EmployeeDetails.html page by adding HTML input elements as shown below -

Add the above code just after the

tag. In the above code, we are using the ng-model directive which enables us to send the data back to the model. Based on this data, we will make a search for an employee using the EmployeeName property. Make sure that EmployeeName property is declared in our model, which we will do in the following steps. Also notice that we are using ng-submit directive which will give a call to SearchEmployee function from our controller.

Now let's modify the EmployeesController.js file so that we can search the employee based on EmployeeName property as a searching criteria. The code is shown below -

(function () ( var EmployeesController = function ($scope,$http) ( var employees = function (serviceResp) ( $scope.Employees = serviceResp.data; ); $scope.SearchEmployees = function (EmployeeName) ( $http.get ("http://localhost:2464/api/ptemployees/" + EmployeeName) .then(employees, errorDetails); ); var errorDetails = function (serviceResp) ( $scope.Error="Something went wrong ??"; ) ;$http.get("http://localhost:2464/api/ptemployees") .then(employees,errorDetails); $scope.Title = "(!LANG:Employee Details Page"; $scope.EmployeeName = null; }; app.controller("EmployeesController", EmployeesController); }()); !}

In the above code, we have added the SearchEmployee() method to our $scope object as a model. This method will search for Employees based on employee name or the character of an employee name. We have also declared EmployeeName property in our controller at the end of this code. The SearchEmployees method fetches the Web API method. I have modified the GET method as shown here:

Public HttpResponseMessage Get(string name) ( var employees = EmployeesRepository.SearchEmployeesByName(name); HttpResponseMessage response = Request.CreateResponse(HttpStatusCode.OK, employees); return response; )

The Employee Repository code is as shown here:

public static list SearchEmployeesByName(string employeeName) ( ProjectTrackingDBEntities dataContext = new ProjectTrackingDBEntities(); var query = from employee in dataContext.Employees where employee.EmployeeName.Contains(employeeName) select employee; return query.ToList(); )

After all these changes, now run the EmployeeDetails.html page and see the output.

In the above output, we are searching for employees whose name contains the 'J' character in it.

AngularJS Filters extend the behavior of binding expressions or directives. Filters are used with binding expressions to format the data being bound. When they are used with directives, they add some additional actions to the directives. Out-of-the-box, AngularJS provides a number of filters which we can use to format the values ​​of an expression and display the values/data into our views. You can make use of filters in Views, Controllers and Services. The syntax of using filters into views is (( expression | filter1 | filter2 | ...)).

We will now try a filter which will sort the data using employee name. To sort the data, let's add a filter in our ng-repeat using a | operator as shown here:

In the above code, we are adding filter in our ng-repeat directive. The orderBy:'employeeName' will sort the data using Employee name in an ascending order. You can observe the output here:

To display the data in descending order, you can change the filter as shown here:

In the above code, to sort the employee names in descending order, we have used (-) minus sign. Likewise, you can make use of (+) sign to sort it in ascending.

You can also make use limitTo filter to limit the number of records. For example, let us say at a time you want to display 5 employees. To display the restricted number of records in our EmployeeDetails.html page, let's modify the ng-repeat directive as shown here-

The output is shown here:

Now if you run the ProjectDetails.html page, the date is getting displayed with time. You can apply the date filter as shown in the following code -

((proj.projectID)) ((proj.projectName)) ((proj.startDate|date:"short")) ((proj.endDate|date:"short")) ((proj.clientName))

The output of this page is as follows:

You can make use of different date formats like - fulldate, longdate, mediumdate, shortdate etc. Now let's open EmployeeDetails.html page and run it. I am using the ‘Z’ character to display employees whose employee name contains Z.

If you observe, the output displays an Employee table heading without data. We can make the heading invisible using the ng-show directive when the filter doesn't produce any result. Apply ng-show directive in our table tag as shown in the below code and try running the application with Z character. Now you will not see the table columns when Employees model is null. The ng-show attribute will evaluate the Employees model and accordingly it will either display the table or hide the table.

Likewise, there are a number of directives which you can use in AngularJS. You can also design a Custom Directive which we will see later in this series. Apply the search on various views as per your requirement in our views. In our next article, we will take a look at

RELATED ARTICLES

• Feedback
• site `s map
• About the site