Morph MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

0 0 1 C#
Normal View History Raw
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
// Copyright © 2020 The CefSharp Authors. All rights reserved.
//
// Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.
//NOTE:Classes in the CefSharp.Core namespace have been hidden from intellisnse so users don't use them directly
Core - PublicApi remove references to CefSharp.Core.Runtime - Add an UnWrap method to the interfaces (should be hidden from IntelliSense) - For .Net 4.5.2 projects they're not a decorator class which an inner instance of the CefSharp.Core.Runtime Type - For Net Core we have a ref assembly which allows us to reference the CefSharp.Core.Runtime without issues We can potentially remove the ref assembly now and forgo any direct reference.
2021-01-13 14:56:27 +10:00
using System;
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
namespace CefSharp
{
/// <inheritdoc/>
Core - PublicApi remove references to CefSharp.Core.Runtime - Add an UnWrap method to the interfaces (should be hidden from IntelliSense) - For .Net 4.5.2 projects they're not a decorator class which an inner instance of the CefSharp.Core.Runtime Type - For Net Core we have a ref assembly which allows us to reference the CefSharp.Core.Runtime without issues We can potentially remove the ref assembly now and forgo any direct reference.
2021-01-13 14:56:27 +10:00
public class UrlRequest : IUrlRequest
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
{
Core - PublicApi remove references to CefSharp.Core.Runtime - Add an UnWrap method to the interfaces (should be hidden from IntelliSense) - For .Net 4.5.2 projects they're not a decorator class which an inner instance of the CefSharp.Core.Runtime Type - For Net Core we have a ref assembly which allows us to reference the CefSharp.Core.Runtime without issues We can potentially remove the ref assembly now and forgo any direct reference.
2021-01-13 14:56:27 +10:00
private CefSharp.Core.UrlRequest urlRequest;
/// <summary>
/// Create a new URL request that is not associated with a specific browser or frame.
/// Use <see cref="IFrame.CreateUrlRequest(IRequest, IUrlRequestClient)"/> instead if you want the
/// request to have this association, in which case it may be handled differently.
/// For requests originating from the browser process: It may be intercepted by the client via <see cref="IResourceRequestHandler"/> or <see cref="ISchemeHandlerFactory"/>.
/// POST data may only contain only a single element of type PDE_TYPE_FILE or PDE_TYPE_BYTES.
/// Uses the Global RequestContext
/// </summary>
/// <param name="request">request</param>
/// <param name="urlRequestClient">url request client</param>
public UrlRequest(IRequest request, IUrlRequestClient urlRequestClient) : this(request, urlRequestClient, null)
{
}
/// <summary>
/// Create a new URL request that is not associated with a specific browser or frame.
/// Use <see cref="IFrame.CreateUrlRequest(IRequest, IUrlRequestClient)"/> instead if you want the
/// request to have this association, in which case it may be handled differently.
/// For requests originating from the browser process: It may be intercepted by the client via <see cref="IResourceRequestHandler"/> or <see cref="ISchemeHandlerFactory"/>.
/// POST data may only contain only a single element of type PDE_TYPE_FILE or PDE_TYPE_BYTES.
/// </summary>
/// <param name="request">request</param>
/// <param name="urlRequestClient">url request client</param>
/// <param name="requestContext">request context associated with this requets.</param>
public UrlRequest(IRequest request, IUrlRequestClient urlRequestClient, IRequestContext requestContext)
{
if (request == null)
{
throw new ArgumentNullException(nameof(request));
}
if (urlRequestClient == null)
{
throw new ArgumentNullException(nameof(urlRequestClient));
}
urlRequest = new CefSharp.Core.UrlRequest(request.UnWrap(), urlRequestClient, requestContext?.UnWrap());
}
/// <inheritdoc/>
public bool ResponseWasCached
{
get { return urlRequest.ResponseWasCached; }
}
/// <inheritdoc/>
public IResponse Response
{
get { return urlRequest.Response; }
}
/// <inheritdoc/>
public UrlRequestStatus RequestStatus
{
get { return urlRequest.RequestStatus; }
}
/// <inheritdoc/>
public void Dispose()
{
urlRequest.Dispose();
}
/// <summary>
/// Create a new URL request that is not associated with a specific browser or frame.
/// Use <see cref="IFrame.CreateUrlRequest(IRequest, IUrlRequestClient)"/> instead if you want the
/// request to have this association, in which case it may be handled differently.
/// For requests originating from the browser process: It may be intercepted by the client via <see cref="IResourceRequestHandler"/> or <see cref="ISchemeHandlerFactory"/>.
/// POST data may only contain only a single element of type PDE_TYPE_FILE or PDE_TYPE_BYTES.
/// Uses the Global RequestContext
/// </summary>
/// <param name="request">request</param>
/// <param name="urlRequestClient">url request client</param>
public IUrlRequest Create(IRequest request, IUrlRequestClient urlRequestClient)
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
{
Core - PublicApi remove references to CefSharp.Core.Runtime - Add an UnWrap method to the interfaces (should be hidden from IntelliSense) - For .Net 4.5.2 projects they're not a decorator class which an inner instance of the CefSharp.Core.Runtime Type - For Net Core we have a ref assembly which allows us to reference the CefSharp.Core.Runtime without issues We can potentially remove the ref assembly now and forgo any direct reference.
2021-01-13 14:56:27 +10:00
return new CefSharp.Core.UrlRequest(request, urlRequestClient);
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
}
Core - PublicApi remove references to CefSharp.Core.Runtime - Add an UnWrap method to the interfaces (should be hidden from IntelliSense) - For .Net 4.5.2 projects they're not a decorator class which an inner instance of the CefSharp.Core.Runtime Type - For Net Core we have a ref assembly which allows us to reference the CefSharp.Core.Runtime without issues We can potentially remove the ref assembly now and forgo any direct reference.
2021-01-13 14:56:27 +10:00
/// <summary>
/// Create a new URL request that is not associated with a specific browser or frame.
/// Use <see cref="IFrame.CreateUrlRequest(IRequest, IUrlRequestClient)"/> instead if you want the
/// request to have this association, in which case it may be handled differently.
/// For requests originating from the browser process: It may be intercepted by the client via <see cref="IResourceRequestHandler"/> or <see cref="ISchemeHandlerFactory"/>.
/// POST data may only contain only a single element of type PDE_TYPE_FILE or PDE_TYPE_BYTES.
/// </summary>
/// <param name="request">request</param>
/// <param name="urlRequestClient">url request client</param>
/// <param name="requestContext">request context associated with this requets.</param>
public IUrlRequest Create(IRequest request, IUrlRequestClient urlRequestClient, IRequestContext requestContext)
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
{
Core - PublicApi remove references to CefSharp.Core.Runtime - Add an UnWrap method to the interfaces (should be hidden from IntelliSense) - For .Net 4.5.2 projects they're not a decorator class which an inner instance of the CefSharp.Core.Runtime Type - For Net Core we have a ref assembly which allows us to reference the CefSharp.Core.Runtime without issues We can potentially remove the ref assembly now and forgo any direct reference.
2021-01-13 14:56:27 +10:00
return new CefSharp.Core.UrlRequest(request, urlRequestClient, requestContext);
Core - Split PublicApi.cs out into separate classes Issue #3319
2021-01-11 10:45:32 +10:00
}
}
}
Reference in New Issue Copy Permalink