13 packages tagged with “horror”
The core module for Pixel Horror Studios. This package contains events and models for network payloads for Client or Server connections. This package is used as a base module for many different applications including but not limited to: Allie.Chat, TheMonitaur, Tcp.NET, Udp.NET, WebsocketsSimple, and NTier.NET.
The core networking module for Pixel Horror Studios. This package contains events and models for network payloads for Client or Server connections. A server module is also available under PHS.Networking.Server. This package is used as a base module for many different applications including but not limited to: Allie.Chat, TheMonitaur, Tcp.NET, Udp.NET, WebsocketsSimple, and NTier.NET.
The server core networking module for Pixel Horror Studios. This package contains events and models for network payloads for Server connections. This package is used as a base module for many different applications requiring server-side networking including but not limited to: Allie.Chat, TheMonitaur, Tcp.NET, Udp.NET, WebsocketsSimple, and NTier.NET.
This is the public library for https://www.TheMonitaur.com, a free and simple single-source web application for monitoring all your application layers using Tcp, Websocket, and/or WebAPI / Http.
This is the Tcp .NET plugin for logging with https://www.TheMonitaur.com, a free and simple single-source web application for monitoring all your application layers using Tcp, Websocket, and/or WebAPI / Http.
This is the WebAPI Client .NET plugin for logging with https://www.TheMonitaur.com, a free and simple single-source web application for monitoring all your application layers using Tcp, Websocket, and/or WebAPI / Http.
This is the Websocket Client .NET plugin for logging with https://www.TheMonitaur.com, a free and simple single-source web application for monitoring all your application layers using Tcp, Websocket, and/or WebAPI / Http.
This packages contains the public plugins for interacting with https://www.TheMonitaur.com, a free and simple single-source web application for monitoring all your application layers using Tcp, Websocket, and/or WebAPI / Http.
JWTs is a simple library for generating and validating JWT tokens and Refresh Tokens. Refresh Tokens are dependent on a database / memory cache and an interface for a simple DAL for storing refresh tokens is included. JWTs can be generated with custom claims, and a DAL is only required when issuing Refresh Tokens. This library is independent of any overarching entities such as Application User and Client. This library is used in OAuthServer.NET.
OAuthServer.NET is a simple yet scalable OAuth 2.0 provider for the 4 standard types of OAuth 2.0 as well as custom grants. OAuthServer.NET supports implicit, authorization code, resource owner password, and client credentials as well as 3rd party logins. OAuthServer.NET is integrated with the Asp.NET Identity system and includes the ability for full managemant of accounts. OAuthServer.NET includes a UI (created in Angular) for easily setting up and configuring clients. OAuthServer.NET is easily deployed through Docker, NuGet, or can be modified directly from the source https://github.com/liveordevtrying/oauthserver.net. OAuthServer.NET is dependent on SQL server, Entity Framework, and the Asp.NET Identity System.
Jogo de Cartas de Aventura e Terror Gótico na Época Victoriana
A simple middleware built on reflection designed to support your Search Engine Optimized (SEO) app by dynamically creating a Sitemap.xml and Robots.txt. This package is designed to be very simple for simple use cases but allows for custom disallowed routes, user agents, and custom node endpoints by supplying optional parameters to the middleware extension methods. Sitemaps.xml asks if you would like to parse the controllers - you can add the [NoSiteMap] attribute to any class or method you would not like included in the Sitemap.xml and the [Priority] attribute to set custom priorities per route. You can provide detail routing information for a dynamic sitemap.xml of items, e.g. a link for each product in the products database. The Robots middleware will allow you to add any number of RobotRules for defining your User-Agent and Disallowed routes. This middleware parses the existing controller structure and automatically includes all get endpoints in the dynamic Sitemap.xml while ignoring any Posts, Puts, or Deletes.