MXTires.Microdata 1.0.4.5

dotnet add package MXTires.Microdata --version 1.0.4.5
NuGet\Install-Package MXTires.Microdata -Version 1.0.4.5
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="MXTires.Microdata" Version="1.0.4.5" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add MXTires.Microdata --version 1.0.4.5
#r "nuget: MXTires.Microdata, 1.0.4.5"
#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 MXTires.Microdata as a Cake Addin
#addin nuget:?package=MXTires.Microdata&version=1.0.4.5

// Install MXTires.Microdata as a Cake Tool
#tool nuget:?package=MXTires.Microdata&version=1.0.4.5

1010TIRES Store

Get sourece code from https://github.com/321baktrak/1010TIRES.

Initial Setup

Before you start make sure your development environment includes Node.js® and an npm package manager.

Angular requires a current, active LTS, or maintenance LTS version of Node.js. See the engines key for the specific version requirements in our package.json. To check your version, run node -v in a terminal/console window. To get Node.js, go to nodejs.org. See: https://angular.io/guide/setup-local

Running guide

It's easier to run application with angular-cli. You can use cli from dev dependencies, but you can also install it globally on your system with npm install -g @angular/cli command. ng serve command is used to start dev server on 4200th port.

Development Guide

To simplify developing user screens, try to use ng-cli to generate modules, components, etc.

Here's little cli cheatsheet with most used commands and main options.

Generating Modules

ng generate module {PATH}/{NAME} {OPTIONS}

Options:

  • {NAME} module name without "module" suffix.
  • {PATH} module path relative to app dir (for inner modules).
  • --routing=true automatically create routing module with base code and import it.
  • --spec=false

Generating Components

ng generate component {PATH}/{NAME} {OPTIONS}

Options:

  • {NAME} component name without "component" suffix.
  • {PATH} component path relative to app dir.
  • --flat=true -- don't create component folder.
  • --selector=cmp-name component selector.
  • --prefix=mdl component selector prefix.
  • --inline-template do not generate external html file.
  • --inline-style do not generate external css file.
  • --module=module-name module name (can be omitted in case of setting {PATH}).

store-checkout example

Step-by-step guide

"Screen" is a component (optionally containing other components) representing app page.

"Section" is a module containing components representing similar "screens".

To create store-checkout section, you have to create:

  1. Create new module.
  2. Create base component.
  3. Add screen components.
  4. Set up routing.

Commands example

Use -d for dryRun

  1. ng generate module store-checkout --routing=true --spec=false
  2. ng generate component store-checkout/store-checkout --spec=false --flat=true --selector=store-checkout --inline-style=true
  3. ng generate component store-checkout/store-checkout-editor --spec=false --selector=store-checkout-editor
  4. Set up routing:
  • Use forChild instead of forRoot
  • Use children property

To Run the application under the IIS

Use npm run bl command It will put an aplication into dist folder Configure IIS to use dist if it has not been done before Make sure you have URL Rewrite module installed for IIS

Producttion build

npm run prod or ng build --output-path=dist/ --baseHref /shop/ --configuration=production

Product Compatible and additional computed target framework versions.
.NET net5.0 is compatible.  net5.0-windows was computed.  net6.0 is compatible.  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 netcoreapp3.1 is compatible. 
.NET Framework net461 is compatible.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 is compatible.  net48 is compatible.  net481 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.4.5 1,221 5/28/2023
1.0.4.4 380 3/17/2023
1.0.4.3 627 2/8/2023
1.0.4.2 740 12/12/2022
1.0.4.1 2,185 12/28/2021
1.0.4 12,824 11/18/2020
1.0.3.9 35,152 11/12/2020
1.0.3.8 8,612 6/9/2020
1.0.3.7 544 6/3/2020
1.0.3.4 934 1/31/2020
1.0.3.3 31,572 10/15/2018
1.0.3.2 37,355 3/17/2017
1.0.3 7,158 1/4/2017
1.0.2.9 8,902 8/24/2016
1.0.2.8 2,631 5/31/2016
1.0.2.7 1,054 5/23/2016
1.0.2.6 1,409 5/20/2016
1.0.2.5 1,479 3/4/2016
1.0.2.4 1,464 2/11/2016
1.0.2.3 1,438 2/7/2016
1.0.2.2 1,374 1/21/2016
1.0.2.1 1,387 12/8/2015
1.0.2 1,173 9/9/2015
1.0.1.2 1,120 6/18/2015
1.0.1.1 1,053 5/26/2015
1.0.1 1,056 5/14/2015
1.0.0.11 1,325 4/28/2015
1.0.0.10 1,363 4/16/2015
1.0.0.9 1,083 4/7/2015
1.0.0.8 1,070 3/27/2015
1.0.0.7 1,046 3/25/2015
1.0.0.6 1,075 3/23/2015
1.0.0.5 1,044 3/20/2015
1.0.0.4 1,322 3/16/2015
1.0.0.3 1,225 3/13/2015
1.0.0.2 1,215 3/13/2015
1.0.0.1 1,232 3/5/2015
1.0.0 1,095 3/5/2015

Updated https://schema.org/GovernmentService properties. Updated VideoGame properties.