WebEssentials.AspNetCore.ServiceWorker | Progressive Web App is a set of technologies | Web Framework library

by madskristensen C# Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | WebEssentials.AspNetCore.ServiceWorker Summary

WebEssentials.AspNetCore.ServiceWorker is a C# library typically used in Server, Web Framework, Angular, React, Webpack applications. WebEssentials.AspNetCore.ServiceWorker has no bugs, it has no vulnerabilities and it has low support. However WebEssentials.AspNetCore.ServiceWorker has a Non-SPDX License. You can download it from GitHub.

A Progressive Web App (PWA) is a set of technologies that can be applied to any type of website and web application, and it consist of 3 components:. This components makes Web App Manifest a natural and integrated part of any ASP.NET Core web application and it comes with pre-built service workers so you don't have to write your own.

Support

Quality

Security

License

Reuse

Support

WebEssentials.AspNetCore.ServiceWorker has a low active ecosystem.

It has 323 star(s) with 55 fork(s). There are 30 watchers for this library.

It had no major release in the last 6 months.

There are 55 open issues and 18 have been closed. On average issues are closed in 101 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of WebEssentials.AspNetCore.ServiceWorker is current.

Quality

WebEssentials.AspNetCore.ServiceWorker has 0 bugs and 0 code smells.

Security

WebEssentials.AspNetCore.ServiceWorker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

WebEssentials.AspNetCore.ServiceWorker code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

WebEssentials.AspNetCore.ServiceWorker has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

WebEssentials.AspNetCore.ServiceWorker releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

WebEssentials.AspNetCore.ServiceWorker saves you 22 person hours of effort in developing the same functionality from scratch.

It has 60 lines of code, 0 functions and 24 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of WebEssentials.AspNetCore.ServiceWorker

Get all kandi verified functions for this library.

WebEssentials.AspNetCore.ServiceWorker Key Features

No Key Features are available at this moment for WebEssentials.AspNetCore.ServiceWorker.

WebEssentials.AspNetCore.ServiceWorker Examples and Code Snippets

No Code Snippets are available at this moment for WebEssentials.AspNetCore.ServiceWorker.

Community Discussions

Trending Discussions on WebEssentials.AspNetCore.ServiceWorker

ASP.Net Core PWA Cache Query

QUESTION

ASP.Net Core PWA Cache Query

Asked 2019-Feb-05 at 16:00

Asp.Net Core 2.2. MVC App which I am trying to turn into a Progressive Web App (PWA) using Mads Kristensen's WebEssentials.AspNetCore.PWA Package https://github.com/madskristensen/WebEssentials.AspNetCore.ServiceWorker and I am having some issues ensuring certain pages work offline.

The main functionality of the app involves a series of questions being presented to the user with the responses saved to a database. This view is populated by a ViewModel which queries the database in order to display the correct information.

My question is, as the database content will rarely change, am I able to cache the query result so the entire app can work offline? And if so, what is the best practice to do so?

My default map route is controller/action/id so when trying to utilize routesToPreCache in appsettings.json I am unable to include the id for the newly created 'incident' so it doesn't work - am I missing a simple trick or is the solution much more complex?

My controller for the view is as follows:

...

ANSWER

Answered 2019-Feb-05 at 16:00

What you want to do can certainly be done. However, it will require a moderate amount of 'heavy lifting'

Mads PWA utility works great, but it does shield you somewhat from the service worker and manifest files.

You'll need to set the manifest to cache the 'questions' page. This will tell the PWA to go ahead and cache the page automatically on the user's device without the user ever having visited it. That way when they are offline, it will appear when they eventually browse to that page.

However, if the user is offline, submitting data by the user involves two things: storing the response values to local storage (not too difficult), and then syncing up the user's browser local storage by triggering an event when the device is online and then sending that data to the remote (your) database (rather involved, hence difficult).

Hope that helps.

Source https://stackoverflow.com/questions/54537543

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install WebEssentials.AspNetCore.ServiceWorker

To add the PWA service to your ASP.NET Core 2.0 application, simply add the NuGet package WebEssentials.AspNetCore.PWA.
You need to do a few things to turn your website into a PWA:.
Add two image icons to your project (192x192 and 512x512)
Add a manifest.json file in the root of the wwwroot folder
Register a service in Startup.cs
Make sure it works

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: