dotnet6-openapi
Paket
dotnet6-openapi | Paket | |
---|---|---|
4 | 9 | |
38 | 1,987 | |
- | 0.3% | |
0.0 | 8.0 | |
over 2 years ago | about 1 month ago | |
TypeScript | F# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotnet6-openapi
-
Is it a bad idea to build a marketplace app using .Net core?
.NET Web API has great tooling for generating OpenAPI on build. Once you have this, you can easily generate TypeScript bindings for your front-end. See also: https://github.com/CharlieDigital/dotnet6-openapi
-
The Case for C# and .NET
This will scaffold a project which is more or less the exact same as Flask, Express, or any other "easy" framework.
OpenAPI output is built-in, but tooling for development does require a bit of knowledge (agree that Microsoft would benefit from making this work out of the box).
A small repo here showing how to connect OpenAPI and front-end TypeScript client generation: https://github.com/CharlieDigital/dotnet6-openapi
-
Im confused by different types of ASP.NET design patterns.
I have one example that shows how to do this with Vue and Svelte: https://github.com/CharlieDigital/dotnet6-openapi
-
Learn to make a web app with ASP NET Core and Vue?
A lot of the work I've done is closed source, but I do have a simple template here that is a typical starting point: https://github.com/CharlieDigital/dotnet6-openapi
Paket
-
The Case for C# and .NET
I'm not sure if it will help in your scenario, but faced with a similar problem (~80 project solution, mixed c#/f#, with varying dependencies), I found success with Paket (https://github.com/fsprojects/Paket)
It is much more prevalent in the f# community (at this point `dotnet restore` is a perfectly fine default until you hit trouble), but isn't limited to just being applied there.
-
Introduction to Paket for F#
You can find the official docs here: https://fsprojects.github.io/Paket/
-
The located assembly's manifest definition does not match the assembly reference - The bane of my existence
Another thing that might be worth considering for you is Paket. This is an alternative to using nuget, directly, and will take a little bit of setting up (follow their instructions), but once you have it, it will make sure that all dependencies and transitive dependencies for all your projects are the same. Not 100% sure if this would solve the issue for you, and it might be tricky if the realApplication has unknown shared dependencies with the other projects, but you can give it a try.
-
Scala at Scale at Databricks
Check out https://fsprojects.github.io/Paket/ and https://fake.build/ and https://docs.microsoft.com/en-us/dotnet/fsharp/get-started/get-started-vscode for playing with F#.
-
WebSharper: Getting Started Easily
So I am stuck again when I want to create a web app. Don't laugh. Once again, I come from *NIX environment and the way everything is started in WebSharper is quite confusing at first. I tried to go installation documentation but I don't use Visual Studio nor MonoDevelop. Using paket also doesn't solve my problem since they also seem to use Visual Studio or MonoDevelop.
-
Can't get paket to work for the simplest case
a bit of follow up: this is because the init command you ran defaulted to those frameworks. it could be smarter, or it could default to something more recent. I opened this PR to update this default.
-
What do you think ASP.NET Core is missing or could do better?
If this would be true, there would be no reason for something like Paket to exist.
-
A Brief F# Exploration
I agree with the author about the slow inner loop experience. Recompiling the whole app to see browser changes gets tiring. The .NET team is planning a series of updates to address this in .NET 6. https://github.com/dotnet/core/issues/5510
I also dislike the default workflow for dealing with Nuget forks. I switched to Paket for dependency management which makes this much simpler. https://fsprojects.github.io/Paket/
-
Is it possible to use Paket, with dotnetcore, with packages from github?
Also, I stumbled on this ticket https://github.com/fsprojects/Paket/issues/3064 which seems to confirm my fear that Paket is limited to importing files from Github, not entire packages, but I'm still hoping.
What are some alternatives?
Fable.Remoting - Type-safe communication layer (RPC-style) for F# featuring Fable and .NET Apps
NuGet - NuGet Gallery is a package repository that powers https://www.nuget.org. Use this repo for reporting NuGet.org issues.
dn6-mongo-react-valtio - A fully featured sample .NET 6 Web API with MongoDB, React, and Valtio. Set up for Google Cloud Run for the back-end with a Dockerfile.
BaGet - A lightweight NuGet and symbol server
Sleet - A static nuget feed generator for Azure Storage, AWS S3, and more.
aws-lambda-runtimes-p
Dotnet CLI - The .NET Core command-line (CLI) tools, used for building .NET Core apps and libraries through your development flow (compiling, NuGet package management, running, testing, ...).
aws-lambda-runtimes-performance - AWS Lambda Performance comparison
Femto - Femto is a CLI tool that automatically resolves npm packages used by Fable bindings
docs - This repository contains .NET Documentation.
fbrary - Create, manage and edit your audio book library from the command line.