The Print Shop has come a long way from the days when heavily pixelated banners printed out on perforated computer paper. Broderbund's The Print Shop Essentials is a next-generation production. The Print Shop 5, the newest version of America’s favorite desktop publishing software, is the most intuitive and user-friendly version to date! With a host of new features including a new and improved tool set and more images and templates than ever before, The Print Shop 5. https://naeerliafrat.tistory.com/1.
-->By Steve Smith and Rick Anderson
ASP.NET Core supports the Open Web Interface for .NET (OWIN). OWIN allows web apps to be decoupled from web servers. It defines a standard way for middleware to be used in a pipeline to handle requests and associated responses. ASP.NET Core applications and middleware can interoperate with OWIN-based applications, servers, and middleware.
Is contained within a class library, make sure that the executable consuming the library also includes the reference to Microsoft.Owin.Host.HttpListener.dll, or else it would not get deployed with your program, as there are no explicit references to it from the class library. These products are developed by the ASP.NET team at Microsoft in collaboration with a community of open source developers. See the list of Packages for information about individual components. Documentation is available in the Wiki and overview of OWIN and Katana.
OWIN provides a decoupling layer that allows two frameworks with disparate object models to be used together. The Microsoft.AspNetCore.Owin
package provides two adapter implementations:
This allows ASP.NET Core to be hosted on top of an OWIN compatible server/host or for other OWIN compatible components to be run on top of ASP.NET Core.
Note
Using these adapters comes with a performance cost. Apps using only ASP.NET Core components shouldn't use the Microsoft.AspNetCore.Owin
package or adapters.
This command work when I manually type in cmd. The code worked. Java execute external program. Or dir for testing it worked too.However I was trying to input a command ( business sentitive, I cannot postup). I also try to type: cd.
View or download sample code (how to download)
ASP.NET Core's OWIN support is deployed as part of the Microsoft.AspNetCore.Owin
package. You can import OWIN support into your project by installing this package.
OWIN middleware conforms to the OWIN specification, which requires a Func<IDictionary<string, object>, Task>
interface, and specific keys be set (such as owin.ResponseBody
). The following simple OWIN middleware displays 'Hello World':
The sample signature returns a Task
and accepts an IDictionary<string, object>
as required by OWIN.
The following code shows how to add the OwinHello
middleware (shown above) to the ASP.NET Core pipeline with the UseOwin
extension method.
You can configure other actions to take place within the OWIN pipeline. Xap app store.
Note
Response headers should only be modified prior to the first write to the response stream.
Note
Multiple calls to UseOwin
is discouraged for performance reasons. OWIN components will operate best if grouped together.
OWIN-based servers can host ASP.NET Core apps. One such server is Nowin, a .NET OWIN web server. In the sample for this article, I've included a project that references Nowin and uses it to create an IServer
capable of self-hosting ASP.NET Core.
IServer
is an interface that requires a Features
property and a Start
method.
Start
is responsible for configuring and starting the server, which in this case is done through a series of fluent API calls that set addresses parsed from the IServerAddressesFeature. Note that the fluent configuration of the _builder
variable specifies that requests will be handled by the appFunc
defined earlier in the method. This Func
is called on each request to process incoming requests.
We'll also add an IWebHostBuilder
extension to make it easy to add and configure the Nowin server.
With this in place, invoke the extension in Program.cs to run an ASP.NET Core app using this custom server:
Learn more about ASP.NET Core Servers.
Another example of how OWIN-based servers' features can be leveraged by ASP.NET Core is access to features like WebSockets. The .NET OWIN web server used in the previous example has support for Web Sockets built in, which can be leveraged by an ASP.NET Core application. The example below shows a simple web app that supports Web Sockets and echoes back everything sent to the server through WebSockets.
This sample is configured using the same NowinServer
as the previous one - the only difference is in how the application is configured in its Configure
method. A test using a simple websocket client demonstrates the application:
You can construct an OWIN environment using the HttpContext
.
OWIN depends on an IDictionary<string,object>
object to communicate information throughout an HTTP Request/Response exchange. ASP.NET Core implements the keys listed below. See the primary specification, extensions, and OWIN Key Guidelines and Common Keys.
Key | Value (type) | Description |
---|---|---|
owin.RequestScheme | String | |
owin.RequestMethod | String | |
owin.RequestPathBase | String | |
owin.RequestPath | String | |
owin.RequestQueryString | String | |
owin.RequestProtocol | String | |
owin.RequestHeaders | IDictionary<string,string[]> | |
owin.RequestBody | Stream |
Key | Value (type) | Description |
---|---|---|
owin.RequestId | String | Optional |
Key | Value (type) | Description |
---|---|---|
owin.ResponseStatusCode | int | Optional |
owin.ResponseReasonPhrase | String | Optional |
owin.ResponseHeaders | IDictionary<string,string[]> | |
owin.ResponseBody | Stream |
Key | Value (type) | Description |
---|---|---|
owin.CallCancelled | CancellationToken | |
owin.Version | String |
Key | Value (type) | Description |
---|---|---|
ssl.ClientCertificate | X509Certificate | |
ssl.LoadClientCertAsync | Func<Task> | |
server.RemoteIpAddress | String | |
server.RemotePort | String | |
server.LocalIpAddress | String | |
server.LocalPort | String | |
server.IsLocal | bool | |
server.OnSendingHeaders | Action<Action<object>,object> |
Key | Value (type) | Description |
---|---|---|
sendfile.SendAsync | See delegate signature | Per Request |
Key | Value (type) | Description |
---|---|---|
opaque.Version | String | |
opaque.Upgrade | OpaqueUpgrade | See delegate signature |
opaque.Stream | Stream | |
opaque.CallCancelled | CancellationToken |
Key | Value (type) | Description |
---|---|---|
websocket.Version | String | |
websocket.Accept | WebSocketAccept | See delegate signature |
websocket.AcceptAlt | Non-spec | |
websocket.SubProtocol | String | See RFC6455 Section 4.2.2 Step 5.5 |
websocket.SendAsync | WebSocketSendAsync | See delegate signature |
websocket.ReceiveAsync | WebSocketReceiveAsync | See delegate signature |
websocket.CloseAsync | WebSocketCloseAsync | See delegate signature |
websocket.CallCancelled | CancellationToken | |
websocket.ClientCloseStatus | int | Optional |
websocket.ClientCloseDescription | String | Optional |