The fork is an effort to bring a package to NuGet. We have a legacy project relying on the latest commit of Nothing-Works/inertia-aspnetcore. My main goal is automating the release of the package to create a foundation for supporting the solution. If someone wants to improve a few things I am open to contribution tough.
Visit inertiajs.com to learn more.
One of the following options:
- Package Manager:
PM> Install-Package INERTIAJS.ASPNETCORE.ADAPTER
- .NET CLI:
dotnet add package INERTIAJS.ASPNETCORE.ADAPTER
- SETUP
Startup.cs
public void ConfigureServices(IServiceCollection services)
{
services.AddInertia();
}
public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
//...
app.UseInertia();
//...
}
- Controller
public IActionResult Index()
{
//your js component file name.
var componentName = "Welcome";
//return whatever you want.
var data = new { Id = 1 };
//return Inertia Result.
return Inertia.Render(componentName, data);
}
- View
App.cshtml
@using InertiaAdapter
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Inertia</title>
</head>
<body>
@Inertia.Html(Model)
<!-- reference your js file. -->
<script src="/js/app.js"></script>
</body>
</html>
- Compile your assets. This is really your choice, choose whatever option you are comfortable with. (maybe I should add sample project for Vue).