Component.As.Service 1.0.0

dotnet add package Component.As.Service --version 1.0.0
NuGet\Install-Package Component.As.Service -Version 1.0.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Component.As.Service" Version="1.0.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Component.As.Service --version 1.0.0
#r "nuget: Component.As.Service, 1.0.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Component.As.Service as a Cake Addin
#addin nuget:?package=Component.As.Service&version=1.0.0

// Install Component.As.Service as a Cake Tool
#tool nuget:?package=Component.As.Service&version=1.0.0

Add Component.As.Service to your AspNetCore app in the usual way and behold as your application component is exposed to the world at http://localhost:5000/MyApplicationComponent/MethodName?parameterA=a&parameterB=B

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services
            /*  .AddMvc() here if you required MvcOptions */
            .AddComponentAsService();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app
           /* .UseMvc() here if you require custom Mvc configuration */
           .UseComponentAsService<MyApplicationComponent>();
    }
}

Q&A

  • And form post and json post and complex objects? Yes. Anything that Mvc can normally deliver to an Action by the magic of ModelBinding will be delivered to your component method.

  • What about Route Constraints and REST and things? For sophisticated HTTP-specific concerns, write a traditional MVC Controller which takes your Component as a dependency.

  • Really? Yes really. This is very much a 'Keep it Simple' offer.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.0 927 11/4/2018

ChangeLog
     --------
     1.0.0.0 Component.As.Service