...
Version | Supported |
|---|---|
| Web API 2 |  |
| ASP.NET Core Web API | |
| ASHX / ASMX (see below) | |
Files analyzed
| Icons | File | Extension | Note |
|---|---|---|---|
- | C# | *.cs | |
| .NET Razor | *.cshtml | ||
| VB.NET | *.vb | |
- | JSON | *.json, *.jsonld | |
| ASPX | *.aspx | |
- | XML | *.xml | |
| - | Configuration | web.config, appsettings.json | This extension broadcasts an XML parser for others extensions to analyze web.config files. |
...
| Function Points (transactions) | Quality and Sizing |
|---|---|
| |
...
CAST AIP release | Supported | Languages |
|---|---|---|
| 8.3.x | | C# |
| 8.2.x | | C# |
Supported DBMS servers
This extension is compatible with the following DBMS servers:
DBMS | Supported |
|---|---|
| CSS/PostgreSQL | |
| Oracle |  |
| Microsoft SQL Server | |
Prerequisites
| An installation of any compatible release of CAST AIP Core (see table above) |
Download and installation instructions
A specific version of the ASP.NET Web API Framework extension is shipped with AIP Core. However, this release may not be the release you want to use, therefore you should check before beginning the analysis (i.e. by performing an Advanced onboarding) that the correct extension release is being used. You can see the list of shipped extensions for each release of AIP Core here: Technology coverage changes in CAST AIP 8.3.x.
If you need to change the release use the Included interface in AIP Console:
There is nothing further to do. Follow the instructions below to run a new analysis/snapshot to generate new results:
- Advanced onboarding - run and validate the initial analysis
- Advanced onboarding - snapshot generation and validation
CAST Transaction Configuration Center (TCC) configuration
...
| Icon | Description |
|---|---|
| DotNet Get Operation |
| DotNet Delete Operation |
| DotNet Post Operation |
| DotNet Put Operation |
| DotNet Patch Operation |
| DotNet Any Operation |
| DotNet Controller Action |
Links
...
...
...
...
...
A DotNet Controller Action is created for each controller method, and a call ling is created from this action to the method:
These controller actions may be directly called from clients through HTML5 Razor method calls present in cshtml files:
| Code Block |
|---|
<td>
@Html.ActionLink("Details", "Details", new { id = item.DepartmentID })
</td>
|
One or more DotNet operations are created for one DotNet Controller Action, because the DotNet Server may be called by other clients than Razor clients. From HTML files or sections of HTML in .cshtml files:
| Code Block |
|---|
<div href="Department/Details"> |
Controller actions are therefore always present in transactions, but operations are present only for purely HTMLclients (not clients using razor). As the same controller action may be called for several types of HTML5 resource services, and even several types of URLs (e.g: department/details, department/details/{}, ...), operations which are not called from a client are deleted at the end of analysis. In many cases clients are written in razor, as such it would not be a ideal to keep all operations as it would produce false transactions.
Anchor ashxasmx ashxasmx
ASHX/ASMX support
| ashxasmx | |
| ashxasmx |
...
| Code Block |
|---|
<%@ WebHandler Language="vb" CodeBehind="IISHandler1.vbC#" class="WebApplication1PREFIX.IISHandler1TaxServerInfo" %> |
In IISHandler1.vb:
| Code Block |
|---|
Imports System.Web
Public Class IISHandler1
Implements IHttpHandler
Public Sub ProcessRequest(ByVal context As HttpContext) Implements IHttpHandler.ProcessRequest
' Write your handler implementation here.
End Sub
End Class |
...
Will create an operation for each WebMethod annotated methods:
Rules
Limitations
- Urls URLs present in annotations, which are in a variable, are not supported.