SeppPenner

Contributing to Transcriptase

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

• Reporting a bug
• Discussing the current state of the code
• Submitting a fix
• Proposing new features
• Becoming a maintainer

We Develop with Github

SeppPenner

$destinationDirectory = "C:\LocalNuGetTest\"
$webClient = New-Object System.Net.WebClient
$webClient.Credentials = New-Object System.Net.NetworkCredential("USERNAME", "PASSWORD")
$feed =[xml]$webClient.DownloadString("https://hostednugetfeed.com/custom-feed/nuget/v2/Packages")

$records = $feed | select -ExpandProperty feed | select -ExpandProperty entry #| select -ExpandProperty content

for ($i=0; $i -lt $records.Length; $i++) {
    $content = $records[$i] | select -ExpandProperty content
    $properties = $records[$i] | select -ExpandProperty properties

SeppPenner

$indexClient = new-object system.net.webclient 
$jsonIndex=$indexClient.DownloadString("https://api.nuget.org/v3/catalog0/index.json") | ConvertFrom-Json 
for ($h=0; $h -lt $jsonIndex.items.Length; $h++) { 
    $web_client = new-object system.net.webclient 
    $jsonObj=$web_client.DownloadString($jsonIndex.items[$h].'@id') | ConvertFrom-Json
    for ($i=0; $i -lt $jsonObj.items.Length; $i++) { 
        $package = $jsonObj.items[$i]."nuget:id" + "/" + $jsonObj.items[$i]."nuget:version" 
        $web_client.DownloadFile("https://www.nuget.org/api/v2/package/" + $package, ("C:\Nuget\" + $jsonObj.items[$i]."nuget:id" + "." + $jsonObj.items[$i]."nuget:version" + ".nupkg")) 
        "Processing: " + ($h + 1) + " of " + $jsonIndex.count + " ---- " + ($i + 1) + " of " + $jsonObj.count + " - " + $jsonObj.items[$i]."nuget:id" + "." + $jsonObj.items[$i]."nuget:version" 
    }

SeppPenner

Authentication and Authorization

Authentication means determining who a particular user is. Authorization means applying rules about what they can do. Blazor contains features for handling both aspects of this.

It worth remembering how the overall goals differ between server-side Blazor and client-side Blazor:

• Server-side Blazor applications run on the server. As such, correctly-implemented authorization checks are both how you determine which UI options to show (e.g., which menu entries are available to a certain user) and where you actually enforce access rules.
• Client-side Blazor applications run on the client. As such, authorization is only used as a way of determining what UI options to show (e.g., which menu entries). The actual enforcement of authorization rules must be implemented on whatever backend server your application operates on, since any client-side checks can be modified or bypassed.

Authentication-enabled templates for Server-Side Blazor

SeppPenner

DEL %userprofile%\AppData\Local\Microsoft\VisualStudio\10.0\ComponentModelCache
DEL %userprofile%\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
DEL %userprofile%\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache

SeppPenner

Markdown Lizenz-Buttons

Sammlung von Lizenz-Schildern (Badges) für die README-Datei deines Projekts. Diese Liste enthält die meist verbreiteten Open Source und Open Data Lizenzen. Kopieren und fügen Sie den Code unter den Badges einfach in Ihre Markdown-Dateien ein.

Notes

• Die Schildchen sind mit Shields.io gemacht.
• Diese Badges ersetzen nicht vollständig die Lizenzinformationen dein Projekt, sie sind nur Embleme für das README, so dass der Nutzer die Lizenz auf den ersten Blick sehen kann.
• 🇺🇸🇬🇧 This list in english
• 🇫🇷 Cette liste en français