Visual Studio Code – Solution Explorer .Net Core

July 31, 2018

If you don’t want to run all the command line command of DotNet Core like here.

You can start using the Visual Studio Code for .NET Core with the VSCode Solution Explorer

image

https://marketplace.visualstudio.com/items?itemName=fernandoescolar.vscode-solution-explorer

image

 

Install and Reload

image

 

image

Go to menu VIEW => EXPLORER

image

Create a new Project file from the START page

image

You can see the command it ran, in the Debug window.

image

 

Next it it ask you to open up a TEMPLATE file in the bottom right corner

image

Click YES

It will open the TEMPLATE Window to choose from :

image

It that did not open the Template window you can trigger it manually here.

Right click on the Solution file => Add New Project

image

Follow the questions asked and it will create a new Project from the Template and Programming Language chosen.

Again the commands show up in the Debug Window

image

As you can see it created nicely the new .Net Core Project

image

 

Benefit of this extension is that you don’t need to run all the command manually.

And you don’t need to install a ton of software like Visual Studio on your machine …. Smile

image

You can also add .NET Core Test Explorer Extension to VS Code for Unit testing

image

More extensive info you can find over here

Enjoy !

Advertisements

PowerShell Core – Installation on Windows 10 – Ubuntu WSL

July 4, 2018

Here you can find the correct installation instructions for Ubuntu 16 (and many more like Raspbian, …)

https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-linux?view=powershell-6

1. Open Bash on Windows 10

image

2. Install PowerShell Core

These are the commands needed to get it installed.

# Import the public repository GPG keys
curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -

# Register the Microsoft Ubuntu repository
sudo curl -o /etc/apt/sources.list.d/microsoft.list https://packages.microsoft.com/config/ubuntu/16.04/prod.list

# Update the list of products
sudo apt-get update

# Install PowerShell
sudo apt-get install -y powershell

# Start PowerShell
pwsh

3. Installation process

It looks like this on Windows 10 – Bash

image

4. Test PowerShell

image

5. Let’s connect to O365 – Exchange Online

image

Get-Mailbox

image

Other Commands

Make sense work fine … Get-Service doesn’t work because it is a Windows Command Winking smile

image

All seems OK Smile

Enjoy !


PowerShell Core – How to install the Windows Compatibility Pack

July 3, 2018

First find the correct PowerShell Core Module

Find-Module -Name PSCoreWindowsCompat | ft -a 

 

As you can see it only runs on Windows x64 bit !

clip_image002

Keep in mind that this Windows Compatibility Pack is a Temporary solution from MS, and will not stay forever :

http://lunarfrog.com/blog/windows-compatibility-pack-net-core

Windows Compatibility Pack for .NET Core is not a permanent solution which will stay in codebase forever. Intention of the pack is to build a temporary bridge, allowing adoption of .NET Core to a greater extend. However, in the long term the goal stays the same – replace outdated APIs and features of .NET with newer .NET Standard-compatible alternatives.

You can download it before installing using this command

Save-Module -Name PSCoreWindowsCompat -Repository PSGallery -Path C:\Temp\ -Force 

 

Or install it directly

Install-Module -Name PSCoreWindowsCompat -Repository PSGallery -Verbose -Force 

 

As you can see it needs Administrator Privileges

clip_image004

 

Import the Module PSCoreWindowsCompat

Import-Module -Name PSCoreWindowsCompat 

 

You have to use the DotNet Classes instead of Cmdlets.

For instance the Compatibility pack contains the System.DirectoryServices so you can script against AD.

Like this :

$dom = [System.DirectoryServices.ActiveDirectory.Domain]::GetCurrentDomain()

$root = $dom.GetDirectoryEntry()

$search = [System.DirectoryServices.DirectorySearcher]$root

$search.Filter = "(&(objectclass=user)(objectcategory=user))"

$search.SizeLimit = 3000

$result = $search.FindAll()

foreach ($user in $result){

$user.Properties.distinguishedname 

} 

Compared to Windows PowerShell

Get-ADUser -Filter * | select DistinguishedName 

 

But it works perfectly … Smile

image

 

For .Net Core Applications see here :

https://www.nuget.org/packages/Microsoft.Windows.Compatibility

Run this command :

dotnet add package Microsoft.Windows.Compatibility –version 2.0.0

Enjoy !


PowerShell Core – Running on Windows IoT using a RPI3

July 2, 2018

As mentioned on this post

I was planning to test PowerShell Core on Windows IoT running on an ARM platform using RPI3….

PS Core Version 6.x claims to be a cross platform Smile

It is still experimental as mentioned here :

https://docs.microsoft.com/en-us/powershell/scripting/setup/powershell-core-on-arm?view=powershell-6

So let’s take a look :

1. Download the correct ZIP

https://github.com/PowerShell/PowerShell/releases

Windows IoT running on RPI3 is a 32bit version (if you are using the free version)

image

2. Open the ZIP

This contains all the modules needed to run on your RPI3

image

Extract and copy all files over to your destination RPI3 folder.

 

image

For example c:\pscore

 

3. Setup Remoting on RPI3

Run this command and see PS notes :

You’ll get an error message and will be disconnected from the device because it has to restart WinRM

 

image

 

# Be sure to use the -PowerShellHome parameter otherwise it'll try to create a new
# endpoint with Windows PowerShell 5.1
.\Install-PowerShellRemoting.ps1 -PowerShellHome .
# You'll get an error message and will be disconnected from the device because it has to restart WinRM

 

4. Connect to the PS Core on your RPI3

# Be sure to use the -Configuration parameter.  If you omit it, you will connect to Windows PowerShell 5.1
Enter-PSSession -ComputerName <deviceIp> -Credential Administrator -Configuration powershell.6.0.2

image

 

5. How to run Windows PowerShell modules in PowerShell Core

Run these 2 commands to get access to the Windows PS modules

 

Install-Module WindowsPSModulePath -Force -Scope CurrentUser 

Add-WindowsPSModulePath

 

image

Or this way for a custom module

Import-Module "C:\Program Files (x86)\AutoIt3\AutoItX\AutoItX.psd1"
Get-Command *au3*

 

image

image

6. Test PS Core on your RPI3

image

All runs as expected Smile

 

But keep in mind that not all functions are supported (yet)

image

 

Even if it says so see help Sad smile

image

 

Running PowerShell Core on Linux or Mac see here to get started :

https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-linux?view=powershell-6

https://docs.microsoft.com/en-us/powershell/scripting/setup/installing-powershell-core-on-macos?view=powershell-6

Enjoy !


PowerShell Core – Installing and Testing

July 2, 2018

PowerShell Core has reached version 6.1xxx at this moment …

 

Why do you need PS Core v6.1.x

https://blogs.msdn.microsoft.com/powershell/2018/01/10/powershell-core-6-0-generally-available-ga-and-supported/

https://docs.microsoft.com/en-us/powershell/scripting/whats-new/what-s-new-in-powershell-core-60?view=powershell-6

https://blogs.msdn.microsoft.com/powershell/2018/01/24/powershell-core-6-1-roadmap/

 

How to install

Since PS Core is a cross platform distribution, just pick the one you need Smile

https://github.com/PowerShell/PowerShell/releases

 

Download and run for a Windows 10 SxS installation

 

image

 

Select Open PS Core

or start is manually

image

Testing

In order to run PS Core you need to use the pwsh.exe commandline and not powershell.exe !

Check the PS Core version :

run pswh.exe –v

image

Or the famous command

$psversiontable

 

image

PowerShell core does not have all the modules of the full blown version available.

But it has already a lot… run

get.command 

it will list about 425 commands

image

 

If you need more :

Windows PowerShell Compatibility Pack

With the announcement of the Windows Compatibility Pack for .NET Core for .NET Core, PowerShell Core will regain some APIs that had been dropped in the transition to .NET Core.  This means we can re-enable some cmdlets that weren’t part of the PowerShell Core 6.0 release: WMI, EventLog, and PerfCounters.  In addition, some highly requested APIs will be available which means that some existing Windows PowerShell modules might just work in PowerShell Core 6.0.  This module will replace the WindowsPSModulePath module to add the Windows PowerShell $env:PSModulePath to PowerShell Core 6.0.  Finally, we can use this module to optionally add back some aliases that we removed from PowerShell Core 6.0 that exist in Windows PowerShell.

Example it allows you to run encrypted commands as well out of the box… Smile

image

 

For a full list of command line options run pwsh.exe /? (or –h or –help or …. Winking smile )

Most relevant are :

pwsh -NoExit -Command Get-Date

image

 

Some of the commands you need to run using Administrator privileges or you get this error :

image

pwsh -Command {Get-WinEvent -LogName security} or pwsh -command “& {Get-WinEvent -LogName security}”

image

 

You can run Windows PowerShell modules in PowerShell Core on Windows

 

Install-Module WindowsPSModulePath -Force -Scope CurrentUser 

Add-WindowsPSModulePath

 

Next episode I will test it the PS Core on an RPI3 running Windows IoT, see here

Enjoy!


Windows Core IoT – ASP DotNet Core Razor Pages & SQLite & Web Service on a Raspberry PI3

May 28, 2018

Building a Web Server App using ASP .Net Core using a SQLite Database and a Web Service starts here using this example.

https://docs.microsoft.com/en-us/aspnet/core/data/ef-rp/intro?view=aspnetcore-2.1

I gave it a little twist in order to get it to use an SQLite Database and add a Web Service to it.

This means you need to follow page 1 of 8 from this Tutorial to get the full deal. I only did page 1 & 2.

But make the necessary change mentioned below.

Keep in mind that the we will only use the command line options, and no bulk load of software needed to install Smile

Requirements are that you have Dotnet Core installed.

And have the DB using EF Tools installed from NuGet

Creating the  .Net Razor App

1. Create a new blank RAZOR project

Create a new folder in your PC and run the command to create a new RAZOR project

image

Command : dotnet New Razor

This will create a new blank Razor project

2. Install the DB using EF Tools

Go to Nuget and look for this package

image

I used the version 2.1.0-rc1-final

Run this command :

dotnet add package Microsoft.EntityFrameworkCore.Tools –version 2.1.0-rc1-final

After installation you can test is using this command :

dotnet ef

image

3. Add more packages needed

dotnet add package Microsoft.EntityFrameworkCore.Tools.DotNet –version 2.1.0-preview1-final

dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Design –Version 2.0.0

dotnet add package Microsoft.VisualStudio.Web.CodeGeneration.Utils –Version 2.0.0

4. Add missing other packages

Correct the project .Json package references, by adding the missing packages from the Nuget Site :

image

<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.6" />
    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Design" Version="2.0.2" />
    <PackageReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Utils" Version="2.1.0-preview2-final" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.1.0-preview1-final" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0" />
    <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="2.8.0" />
    <PackageReference Include="SQLitePCLRaw.bundle_green" Version="1.1.10" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="2.0.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite.Core" Version="2.0.2" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.4" />
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="2.0.0" />
  </ItemGroup>
</Project>

Next run this command :

dotnet add xxxxx form the .NET CLI command.

image

It downloads and installed the package selected on the NuGet site

Check you .Json Project file again afterward and continue with the rest of the missing packages

When finished run command :

dotnet Restore

5. Add the missing code to generate the DB

(Or generate the code based on an existing DB using Scaffolding)

Example : Create a Models folder. In the Models folder, create a class file named Student.cs

Content see example Microsoft site :

https://docs.microsoft.com/en-us/aspnet/core/data/ef-rp/intro?view=aspnetcore-2.1

clip_image002[1]

6. Create the xxxxContext DB context

xxx = School in my case


image

In the Data folder create SchoolContext.cs

image

This is where I modified the code to use SQLite instead of a Local DB

optionsBuilder.UseSqlite(@"Datasource=C:\CoreIoT\ASPnetRazorSQLiteWsAPI\Data\School.db");

In Startup.cs add the missing references (Using xxx) add the DB Context reference :

image

Add the DB Context reference :

services.AddEntityFrameworkSqlite().AddDbContext<SchoolContext>(); // Added

In the Data folder, create a new class file named DbInitializer.cs see MS Example Site

image

Which gets called by program.cs

image

This will create the Database Tables, Fields and Records using the Entity Framework Tools.

Opposite, you can create View Pages from an existing Database using Scaffolding with the Entity Framework Tools too… Winking smile

Use a command like this to generate an EF Model from and existing Database

dotnet ef dbcontext scaffold “Datasource=C:\CoreIoT\ASPSQLite\Nwind.db” Microsoft.EntityFrameworkCore.Sqlite -o Models -c “DatabaseContext” –f

7. Generate the View pages based on the model you created before :

Courses : dotnet aspnet-codegenerator razorpage -m Course -dc SchoolContext -udl -outDir Pages\Courses –referenceScriptLibraries

Instructor : dotnet aspnet-codegenerator razorpage -m Instructor -dc SchoolContext -udl -outDir Pages\Instructors –referenceScriptLibraries

8. Correct the ERRORS, if needed…

When running the command in step 6 you can get ERRORS.

image

Globally change _context.Student to _context.Students (add an “s” to Student)

image

Quote from MS Site :

There are 7 occurrences found and updated. This is a bug and the hope to fix this bug in the next release.


=> TEST THE APP to see all errors are gone :

image

cd to your project folder, next use this command :

Dotnet Run

9. BEFORE publishing add the following string in the program.cs and republish again.

image

UseURLs(“http://*:5000)

10. Publish for RPI3 – ARM

Run this command : dotnet publish -r win8-arm

11. Copy from Publish to your RPI3

Copy the Files from the PUBLISH folder to your RPI3.

ASPRazor -> C:\CoreIoT\ASPnetRazorSQLiteWsAPI\bin\Debug\netcoreapp2.0\win8-arm\publish\

image

Next MAKE SURE your FOLDER STRUCTURE on the RPI3, is exactly the same as it was on your PC before Publishing.

image

Or you run into this error : ‘Unable to open database file’

Next COPY the SQLite Database to your RPI3. Because this is NOT included when publishing using DotNet Core to win8Arm

12. Test the .Net Razor App on your RPI3

Login using PowerShell WSMAN to your RPI and start the app.

image

Go to the URL (it can take a while before all is loaded ….)

image

Let access the database ?

clip_image002

Let’s add some data ?

clip_image004

clip_image006

Haleluja, this is fully functional and cross platform !!

Adding a Web Service to the .Net Razor App

Next I will add it to the site to see we can access the data using a Web Service API.

Again instead of using the full blown Visual Studio we will only use the command line options.

Because we don’t want to install an elephant weight of software !

image

Actually Visual Studio uses all these commands in the background too … Winking smile

Run this command :

dotnet aspnet-codegenerator controller -api -name StudentAPIController -m Student -dc SchoolContext -udl -outDir Models\API –referenceScriptLibraries -f

image

see the result

image

You also have the option to generate XML instead of JSON

image

Check the result !!

image

This is how you you select ID 5

ID = 5

clip_image002[5]

It contains GET / POST / PUT / DELETE methods !

Accessing the Web Service using PowerShell

image

CLS

$URL = "http://localhost:5000/api/StudentAPI"

$APIService = Invoke-RestMethod -Uri $URL

$APIService | select ID, lastName, firstMidName 

After copying to your RPI3 you can change the URL to http://rpi3:5000/api/StudentAPI

And test it …

clip_image002[3]

As you can see all runs fine, no Visual Studio needed …. Smile

So now you have a Web Service running on your RPI3, who could have imagined this … ?

Use Case :

Since you now have an SQLite DB running your can feed it with your RPI3 SENSOR data and read it out using the Web Smile

or even as a Web Service as demonstrated above …

Enjoy !


Windows Core IoT – ASP DotNet Core Razor Pages on a Raspberry PI3

April 20, 2018

Continuing on based on my prior posts

.Net Core on RPI3

SQLite on RPI3

I am going to explain how to use Windows IoT and ASP .Net Core on a RPI3.

As of version 2.0 we now can create ASP Razor webpages in .NET Core.

Remember that in the past I made some post about Web Matrix

That is in fact the predecessor of ASP .Net Core. Read more here

How to use Razor Pages in ASP.NET Core 2.0

Start with installing the DotNet Core Template to begin with

Run command :

dotnet new Razor -n ASPnetCoreRazor -o C:\CoreIoT\ASPnetCoreRazor

image

Next Run the Template Application on your Windows PC.

Use command :

cd C:\CoreIoT\ASPnetCoreRazor

dotnet Run

image

Voila as simple as that Smile

image

Next Publish it for Windows IoT on a RPI3 Architecture

Run command :

dotnet publish -r win8-arm


image

Copy the files to your RPI3 from C:\CoreIoT\ASPnetCoreRazor\bin\Debug\netcoreapp2.0\win8-arm\publish

image


Connect to RPI3 using PowerShell remote session and start the ASPNetCoreRazor.exe Application

image

No connection … ? Sad smile

image

SOLUTION :

1. You need to open the Firewall Port 5000 on your RPI3 first.

Run command :

netsh advfirewall firewall add rule name=” ASPnetCoreRazor ” dir=in action=allow protocol=TCP localport=5000


image

2. Modify the Template Program.cs script

And add this line : .UseUrls(http://*:5000)


image

Publish again :

dotnet publish -r win8-arm

image

Copy the files back over to your RPI3 :

C:\CoreIoT\ASPnetCoreRazor\bin\Debug\netcoreapp2.0\win8-arm\publish\


Next connect to RPI3 using PowerShell and start the app ….

.\ASPnetCoreRazor.exe


image

Open the browser and go to : http://rpi3:5000

image

It runs as expected !! Smile

So now we know how to create RAZOR pages, the door is open to start experimenting with the RAZOR syntax.

As well as integrating SQLite database using the ASP .NetCore Razor Front End….

Enjoy !