Windows 10: PowerShellGet 3.0 Preview 1 now available

Brink · Mar 31, 2020

We are excited to announce that our first preview release of PowerShellGet 3.0 is now available on the PowerShell Gallery. This is a major update to PowerShellâs experience for discovering, installing, updating and publishing PowerShell resources like modules, DSC resources, role capabilities and scripts. This was first proposed in RFC PR #185 and superseded by RFC PR #237. Thanks for all the community feedback! For a detailed view of the update to PowerShellGet please refer to the RFC.

This early preview release of the module is not feature complete and has breaking changes intended to improve the user experience. For this reason, the preview release will work side-by-side with your existing PowerShellGet v2 module.

The purpose of this release to begin gathering the critical user feedback to improve the module through subsequent preview releases before we finalize the design for General Availability later this year.

How to Install PowerShellGet 3.0 Preview 1

Prerequisites

Please ensure that you have the latest (non-prerelease) version of PowerShellGet and PackageManagement installed.

To check the version you currently have installed run the command:

Get-InstalledModule PowerShellGet, PackageManagement

The latest version of PowerShellGet is 2.2.3, and the latest version of PackageManagement is 1.4.6.

To install the latest versions of these modules run the following at the start of a fresh PowerShell session:

Install-Module PowerShellGet -Force -AllowClobber

Installing the Preview side by side

To install this preview release side-by-side with your existing PowerShellGet version, open any PowerShell console and run:

Install-Module PowerShellGet -Force -AllowPrerelease

To register the PSGallery run the command:

Register-PSResourceRepository -PSGallery

If you run the command Get-Command -Module PowerShellGet you will get a good picture of the side-by-side cmdlet interfaces.

High-Level Goals of PowerShellGet 3.0

PowerShellGet 3.0 is a complete re-write of PowerShellGet with the following goals:

Improve maintainability of the codebase: This goal is addressed by removing the provider model that PowerShellGet was originally built on. This means that PowerShellGet 3.0 does not take a dependency on OneGet, NuGet or any other package provider. Further, this version is written in C# instead of PowerShell script which has allowed us to simplify the code base. By using the lessons learned from previous versions of the module we hope that a cleaner implementation and interface will allow us to more quickly address bugs as they arise and iterate on our vNext issues more efficiently.

Address top customer issues. Many of the top customer issues in previous versions of the module have been challenging to resolve because of architecture decisions made early on in the development of PowerShellGet. Below we enumerate many of these issues we hope to resolve, to view a full enumeration of these issues view this GitHub query.

Features of this Release

A new set of cmdlets which abstract all PSResource types (Module, Script, DSCResource, RoleCapability, Command) to a single set of cmdlets which use the noun âPSResourceâ. Many of these cmdlets use a -Type parameter for the user to specify the PSResource type if they would like.

Code:

Find-PSResource
Get-PSResource
Get-PSResourceRepository
Install-PSResource
Register-PSResourceRepository
Set-PSResourceRepository
Uninstall-PSResource
Unregister-PSResourceRepository
Update-PSResource
SYNTAX
Find-PSResource [[-Name] <string[]>] [-Type {Module | Script | DscResource | RoleCapability | Command}] [-Version <string>] [-Prerelease] [-ModuleName <string>] [-Tags <string[]>] [-Repository <string[]>] [-Credential <pscredential>] [-IncludeDependencies] [-WhatIf] [-Confirm] [<CommonParameters>] EXAMPLE Find-PSResource -Name PowerShellGet -Type Module -Prerelease
Click to expand...

For the cmdlets Register-PSRepository and Set-PSRepository a -Priority parameter allows setting the search order of repositories with a lower value indicating a higher priority. If not specified, the default value is 50. The PSGallery, which is registered by default, has an editable value of 50. If two PSRepositories have the same priority the âTrustedâ one will be chosen, if they also have the same level of trust the first one alphabetically will be selected.

For Find-PSResource the -Repository parameter supports wildcard search. If no repository is specified, the cmdlet will return the latest version found from the repository with the highest priority.

Find-PSResource Az.Sql -Repository *Name Version Repository Description
â- ââââââ ââââ
Az.Sql 2.5.0 PSGallery Microsoft Azure PowerShell â SQL service cmdlets for Azure Resourceâ¦
Az.Sql 2.5.0 PoshTestGallery Microsoft Azure PowerShell â SQL service cmdlets for Azure Resourceâ¦Find-PSResource Az.SqlName Version Repository Description
â- âââ âââ- ââââ
Az.Sql 2.5.0 PSGallery Microsoft Azure PowerShell â SQL service cmdlets for Azure Resourceâ¦

For Find-PSResource and Install-PSResource the -Version parameter will accept strings (with wildcard support) based on the Nuget version range syntax

Code:

Find-PSResource Microsoft.PowerShell.GraphicalTools -Version *

Name Version Repository Description
---- ------- ---------- -----------
Microsoft.PowerShell.GraphicalTools 0.2.0 PSGallery Cross-platform GUI Tools for Pow.
Microsoft.PowerShell.GraphicalTools 0.1.0 PSGallery Cross-platform GUI Tools for Pow.

Find-PSResource Microsoft.PowerShell.GraphicalTools -Version "(0.0,1.0)"

Name Version Repository Description
---- ------- ---------- -----------
Microsoft.PowerShell.GraphicalTools 0.2.0 PSGallery Cross-platform GUI Tools for Pow.

Find-PSResource Microsoft.PowerShell.GraphicalTools -Version "0.1.1"

Name Version Repository Description
---- ------- ---------- -----------
Microsoft.PowerShell.GraphicalTools 0.1.0 PSGallery Cross-platform GUI Tools for Pow.
Click to expand...

Install-PSResource has a -DestinationPath parameter which allows the user to specify the target directory instead of the default one. Note that in this release âx86â paths, and Linux paths are not yet supported. Expect to see this support in future releases.

Update-PSResource has an -UpdateTo parameter with values MinorVersion (the default), MajorVersion and, PatchVersion.

There is support for NuGet v2 and v3 endpoints for PSRepositories.

If any of the features on this list are not behaving how you would expect them to, or would prefer them to be sure to open an issue in our GitHub repository.

Table of Implemented Parameters in this Release

Cmdlet Implemented parameters Not implemented Install-PSResource -Name-Version
-Prerelease
-Repository
-Credential
-Scope
-Reinstall -InputObject-DestinationPath [partially implemented]
-NoClobber
-IgnoreDifferentPublisher
-TrustRepository
-Force [there hasnât been a need for force yet since the things you would force arenât implemented]
-Quiet
-AcceptLicense
-PassThru Update-PSResource -Name-Version
-Prerelease
-Credential
-Repository [Update should be discovering the repository from the xml metadata instead of from user input, this will be fixed in future releases] -InputObject-UpdateTo
-Force
-Quiet
-AcceptLicense
-PassThru Find-PSResource -Name-Type
-Version
â Prerelease
-ModuleName
-Tags
-Repository
-Credential
-IncludeDependencies [Nothing] Uninstall-PSResource -Name-Version
-PrereleaseOnly [Nothing] Save-PSResource -Name-Version
-Prerelease
-Repository
-Credential
-AsNupkg
-Path -AcceptLicense Get-PSResource -Name-Version -Prerelease Register-PSResourceRepository -Name-URL
-PSGallery
-Credential
-Trusted
-Priority -Repositories-Proxy[for any proxies other than the default proxy]
-ProxyCredential[see above regarding -Proxy] Unregister-PSResourceRepository -Name [Nothing] Get-PSResourceRepository -Name-URL
-Credential
-Trusted
-Priority -Repositories-Proxy [for any proxies other than the default proxy]
-ProxyCredential [see above regarding -Proxy]
Whatâs Coming Next

Features to Expect in Coming Preview Releases

This module is not feature complete, meaning many issues/bugs in this release may just be features we have not finished implementing.

Below is a list of features that we are still in the process of implementing which you can expect to see in future preview releases.

Publish functionality (in the meantime the publish functionality of PowerShellGet2.x works nicely side-by-side)

Error handling, warnings, -Verbose, and -Debug parameters (for the full list of missing parameter see the table above).

Local cacheâthis important feature significantly improves the performance of Find/Install operations. Look forward to it in future releases.

Dependency management. In future releases, Install-PSResource will accept a path to a psd1 or json file (using -RequiredResourceFile), or a hash table or json (using -RequiredResource) where the key is the module name and the value is either the required version specified using Nuget version range syntax or a hash table where repository is set to the URL of the repository and version contains the Nuget version range syntax.

Install-PSResource -RequiredResource @{ "Configuration" = "[1.3.1,2.0)" "Pester" = @{ version = "[4.4.2,4.7.0]" repository = "https://www.powershellgallery.com" credential = $cred allowPrerelease = $true } }

In this case the modules named âConfigurationâ, and âPesterâ will be installed.

The JSON format will be the same as if this hashtable is passed to ConvertTo-Json:

{ "Configuration": "[1.3.1,2.0)", "Pester": { "version": "[4.4.2,4.7.0]", "credential": null, "repository": "https://www.powershellgallery.com", "allowPrerelease": true } }

We will introduce a New-RequiredResourceFile cmdlet which will create a template file.
If the switch -AsPSD1 is used it will create a psd1 file, otherwise it will default to JSON.

Save-PSResource -Type Library will download nupkgs that have a lib folder. The dependent native library in runtimes matching the current system runtime will be copied to the root of the destination specified. A -IncludeAllRuntimes can be used to explicitly retain the runtimes directory hierarchy within the nupkg to the root of the destination.

Native credential management/credential persistence for registered PSRepositories

Improvements we are Considering Post-GA

One important goal of PowerShellGet 3.0 is to improve the supportability of the module. As a result, once this work is complete,we hope to iterate more quickly, and tackle other top customer issues. This list represents issues we are considering tackling but have not committed to yet.

We will explore automatic updating of the cache in which on any operation that reaches out to a repository, a REST API will be called to see if the hash of the cache matches the current cache and if not, a new one is downloaded. This system may also take into consideration how recently the cache has been updated to avoid constant updates.

We will explore an Enable-PowerShellGetAlias cmdlet that will allow users to use known cmdlets like Install-Module from the PowerShellGet 3.0 implementation.

We will explore uninstalling orphaned dependencies automatically.

To track the full list of issues we are considering we are using the label vNext in our GitHub Repository.

How to Track the Development of this Module

GitHub is the best place to track the bugs/feature requests related to this module. We have used a combination of projects and labels on our GitHub repo to track issues for this upcoming release. We are using the label Resolved-3.0 to label issues that we plan to release at some point in before we release the module as GA (generally available). To track issues/features to particular preview and GA releases we are using GitHub projects which are titled to reflect the release.

Please note that PowerShell/PowerShellGet now represents the codebase for PowerShellGet 3.0. If you are looking for the source code, or issues related to previous versions of PowerShellGet, use PowerShell/PowerShellGetV2.

Timeline/Roadmap

Expect to see preview releases as new functionality is added/changes are made at approximately a monthly cadence until the module is feature-complete. Through this process we will also be adapting the module based on user feedback. Once we feel we have reached a sufficient quality and completeness, we will release a âRelease Candidateâ version of the module. Assuming this release does not require any high impact changes, we will then release that version of the module as âGenerally Availableâ. Since these milestones are quality, rather than date, driven we can not offer an exact timeline at this point, but hope to release the module later this year.

How to Give feedback and Get Support

We cannot overstate how critical user feedback is at this stage in the development of the module. Feedback from preview releases help inform design decisions without incurring a breaking change once generally available and used in production. In order to help us to make key decisions around the behavior of the module please give us feedback by opening issues in our GitHub repository.

Sydney Smith
PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...3-0-preview-1/

:)

Krishna Prasobh V · Mar 31, 2020

Preview pane is not available while viewing the pictures

Hi,

Thank you for posting your query on Microsoft Community.

To assist you better, I would like to know the file format of the image that you would like to see in preview pane.

If the preview pane doesn’t appear, I suggest you to follow the steps and check if that helps to resolve the issue.

Open the folder where the images are located.

Click on View option at the top and choose
Preview pane.

Now you will be able to see the images on the Preview pane.

Hope the information helps. Let us know if you need further assistance. We will be happy to help.

Thank you.

Brink · Mar 31, 2020

Support for Pen with Windows Application Driver v1.1 Preview

Windows Application Driver (WinAppDriver) is continuing Microsoft’s investment in UI test automation tools for Windows 10, and now, we’re excited to announce the next release of WinAppDriver—version 1.1!

A preview is available today— bringing support for Pen automation. The full v1.1 release is also on the horizon and will feature support for Multi-Touch in addition to Pen.

pxv8elFZY7g

What is WinAppDriver?

For those of you who aren’t familiar with WinAppDriver or UI automation, WinAppDriver is an open-standards based UI automation service designed to work with all kinds of Windows 10 applications including WPF, WinForms, legacy Win32, and UWP. By complying with an open-standard, WinAppDriver users will be able to leverage the robust UI automation ecosystem already provided by Appium and Selenium.

What’s new in the v1.1 Preview

In v1.1, we’re aligning with the W3C WebDriver standard, and as a result, implementing the Actions API to bring in advanced input device support.

The Preview release of v1.1 includes the following:

WinAppDriver updated for Pen, including support for advanced Pen functionality:

Pressure

Tilt X & Tilt Y

Twist

Barrel button

Eraser support

Appium-Dotnet-Driver NuGet Package

This is a preview Nuget package with updated bindings to enable Pen automation on WinAppDriver.

Samples & Documentation on GitHub

Note that the full release will also include support for Multi-Touch – more details on that below.

Getting Started with Pen

You can download the preview version of WinAppDriver on our GitHub page here: Releases · Microsoft/WinAppDriver · GitHub.

To get started on using Pen, we highly recommend checking out our new Sticky Notes sample here.

Let’s sketch out a quick smile

To demonstrate something a little more complex than a few strokes on a sticky note, we tried drawing out the following smiley face through the following steps–

Step 1 – Using Pen to draw a basic Circle

[table][tr][td]1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25[/td] [td]//Initiate a Pen object using the custom Dotnet Driver Bindings. PointerInputDevice penDevice = new PointerInputDevice(PointerKind.Pen); ActionSequence drawSequence = new ActionSequence(penDevice, 0); //Set starting position of circle by its center point. var centerX = canvasCoordinate.X + canvasSize.Width / 5 + 285; var centerY = canvasCoordinate.Y + canvasSize.Height / 5 + 270; //Radius of circle. var radius = 200; /* This value will dictate the granularity of the number of stokes to complete the strokes. The more steps, the less blocky the circle will be. Note: Sticky Notes will interpolate between the steps anyway, so it will not appear blocky if Pen is not lifted. */ var steps = 50; // These two variables will calculate either the X or Y coordinate around the center of the circle for a given step. int xValue = (int)(centerX + radius * Math.Cos(2 * Math.PI * 0 / steps)); int yValue = (int)(centerY + radius * Math.Sin(2 * Math.PI * 0 / steps)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xValue, yValue, TimeSpan.Zero)); drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenFrontTip)); /* Function to draw circle by calculating coordinates around center point and brushing through them. */ for (var i = 0; i <= steps; i++) { xValue = (int)(centerX + radius * Math.Cos(2 * Math.PI * i / steps)); yValue = (int)(centerY + radius * Math.Sin(2 * Math.PI * i / steps)); drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xValue, yValue, TimeSpan.Zero)); } //Lifting pen up once Circle is drawn. drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenContact)); //Final step would be to execute the sequence. newStickyNoteSession.PerformActions(new List<ActionSequence> { drawSequence });[/td] [/tr] [/table]

Step 2 – Adding in the smile

We’ll have to get a little clever with this part, and modify the original for-loop from step 1 and add supplementary code following it. This will continue the same sequence.

[table][tr][td]1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27[/td] [td]/* Loop modified to iterate past opening step and closing step of circle. This will create an opening for the smiley ìmouthî. */ for (var i = 0; i < steps; i++) { xValue = (int)(centerX + radius * Math.Cos(2 * Math.PI * i / steps)); yValue = (int)(centerY + radius * Math.Sin(2 * Math.PI * i / steps)); if (i > 1){ drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); } drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xValue, yValue, TimeSpan.Zero)); } drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenContact)); /* The following vars will calculate X & Y coordinates for start and end point of the smile. */ var xSmile = (int)(centerX + radius * Math.Cos(2 * Math.PI * 1 / steps)); var ySmile = (int)(centerY + radius * Math.Sin(2 * Math.PI * 1 / steps)); var xSmile2 = (int)(centerX + radius * Math.Cos(2 * Math.PI * (steps - 1) / steps)); var ySmile2 = (int)(centerY + radius * Math.Sin(2 * Math.PI * (steps - 1) / steps)); /* Continue previous sequence and execute the Pen actions. */ drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xSmile, ySmile, TimeSpan.Zero)); drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, centerX, centerY, TimeSpan.FromMilliseconds(400), new PenInfo { Pressure = .600f })); drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xSmile2, ySmile2, TimeSpan.FromMilliseconds(400))); // Execute sequence. newStickyNoteSession.PerformActions(new List<ActionSequence> { drawSequence });[/td] [/tr] [/table]

The additional pressure applied to the “smile strokes”—this is to add depth to the smile. The sketch should appear as the following:

Step 3 – Eyes

If we wanted to finish up and add eyes, it would look something like the following:

There’s a lot of clever ways you can go on about adding the eyes, so we’ll let you decide which way is best. The full code for our design will be included as part of the Sticky Notes sample on GitHub!

Details on full 1.1

The full release of v1.1 will come with the following additions:

WinAppDriver

Pen—support for Pen will be carried over to full 1.1 release from the Preview.

Multi-Touch—support for Multi-Touch will be added in as well through the Actions API. The following touch modifiers will be supported:

Pressure

Twist

New Samples & Bindings

Samples from the Preview will be further expanded to demonstrate Pen and Multi-Touch functionality. The samples will incorporate a private Appium-Dotnet-Driver Nuget feed that will enable Actions implementation via the new bindings. We’re looking into having these changes be merged into the official Appium .Net Driver, and eventually be rolled-up to the Selenium Namespace in the future.

Release Date

We’re targeting this June for the full release of v1.1—stay tuned to our GitHub board for more info!

Moving Forward

The WinAppDriver team will continue to work on adding new features, resolving bugs, and improving performance. We’ve been looking into popular community requests, and as such, have a couple of cool things in the pipeline for 1.2 and beyond—one in particular being to improve performance with XPath handling.

We’ll also be releasing a new tool for the community – more details on this to follow in the coming weeks. Stay tuned!

How do I provide feedback?

Please provide feedback on our Github issue board – we look forward to hearing about any suggestions, feature requests, or bug reports!

microsoft/WinAppDriver

If you have any cool sketches done through v1.1 that you’d like to share—do so on the GitHub board! It may even be featured in a future blog post!

Stay Informed

To stay up to date with WinAppDriver news follow @mrhassanuz.

Summary

The v1.1 Preview is available now—enabling users to automate Pen scenarios. Full release for v1.1 to follow, and with it will bring support for Multi-Touch as well. Head over to our releases page on GitHub to download the preview, and get a jump-start on Pen automation by reviewing our updated samples.
Click to expand...

Source: Announcing support for Pen with Windows Application Driver v1.1 - Preview available now - Windows Developer Blog

Brink · Mar 31, 2020

Support for Pen with Windows Application Driver v1.1 Preview

Windows Application Driver (WinAppDriver) is continuing Microsoft’s investment in UI test automation tools for Windows 10, and now, we’re excited to announce the next release of WinAppDriver—version 1.1!

A preview is available today— bringing support for Pen automation. The full v1.1 release is also on the horizon and will feature support for Multi-Touch in addition to Pen.

pxv8elFZY7g

What is WinAppDriver?

For those of you who aren’t familiar with WinAppDriver or UI automation, WinAppDriver is an open-standards based UI automation service designed to work with all kinds of Windows 10 applications including WPF, WinForms, legacy Win32, and UWP. By complying with an open-standard, WinAppDriver users will be able to leverage the robust UI automation ecosystem already provided by Appium and Selenium.

What’s new in the v1.1 Preview

In v1.1, we’re aligning with the W3C WebDriver standard, and as a result, implementing the Actions API to bring in advanced input device support.

The Preview release of v1.1 includes the following:

WinAppDriver updated for Pen, including support for advanced Pen functionality:

Pressure

Tilt X & Tilt Y

Twist

Barrel button

Eraser support

Appium-Dotnet-Driver NuGet Package

This is a preview Nuget package with updated bindings to enable Pen automation on WinAppDriver.

Samples & Documentation on GitHub

Note that the full release will also include support for Multi-Touch – more details on that below.

Getting Started with Pen

You can download the preview version of WinAppDriver on our GitHub page here: Releases · Microsoft/WinAppDriver · GitHub.

To get started on using Pen, we highly recommend checking out our new Sticky Notes sample here.

Let’s sketch out a quick smile

To demonstrate something a little more complex than a few strokes on a sticky note, we tried drawing out the following smiley face through the following steps–

Step 1 – Using Pen to draw a basic Circle

[table][tr][td]1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25[/td] [td]//Initiate a Pen object using the custom Dotnet Driver Bindings. PointerInputDevice penDevice = new PointerInputDevice(PointerKind.Pen); ActionSequence drawSequence = new ActionSequence(penDevice, 0); //Set starting position of circle by its center point. var centerX = canvasCoordinate.X + canvasSize.Width / 5 + 285; var centerY = canvasCoordinate.Y + canvasSize.Height / 5 + 270; //Radius of circle. var radius = 200; /* This value will dictate the granularity of the number of stokes to complete the strokes. The more steps, the less blocky the circle will be. Note: Sticky Notes will interpolate between the steps anyway, so it will not appear blocky if Pen is not lifted. */ var steps = 50; // These two variables will calculate either the X or Y coordinate around the center of the circle for a given step. int xValue = (int)(centerX + radius * Math.Cos(2 * Math.PI * 0 / steps)); int yValue = (int)(centerY + radius * Math.Sin(2 * Math.PI * 0 / steps)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xValue, yValue, TimeSpan.Zero)); drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenFrontTip)); /* Function to draw circle by calculating coordinates around center point and brushing through them. */ for (var i = 0; i <= steps; i++) { xValue = (int)(centerX + radius * Math.Cos(2 * Math.PI * i / steps)); yValue = (int)(centerY + radius * Math.Sin(2 * Math.PI * i / steps)); drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xValue, yValue, TimeSpan.Zero)); } //Lifting pen up once Circle is drawn. drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenContact)); //Final step would be to execute the sequence. newStickyNoteSession.PerformActions(new List<ActionSequence> { drawSequence });[/td] [/tr] [/table]

Step 2 – Adding in the smile

We’ll have to get a little clever with this part, and modify the original for-loop from step 1 and add supplementary code following it. This will continue the same sequence.

[table][tr][td]1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27[/td] [td]/* Loop modified to iterate past opening step and closing step of circle. This will create an opening for the smiley ìmouthî. */ for (var i = 0; i < steps; i++) { xValue = (int)(centerX + radius * Math.Cos(2 * Math.PI * i / steps)); yValue = (int)(centerY + radius * Math.Sin(2 * Math.PI * i / steps)); if (i > 1){ drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); } drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xValue, yValue, TimeSpan.Zero)); } drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenContact)); /* The following vars will calculate X & Y coordinates for start and end point of the smile. */ var xSmile = (int)(centerX + radius * Math.Cos(2 * Math.PI * 1 / steps)); var ySmile = (int)(centerY + radius * Math.Sin(2 * Math.PI * 1 / steps)); var xSmile2 = (int)(centerX + radius * Math.Cos(2 * Math.PI * (steps - 1) / steps)); var ySmile2 = (int)(centerY + radius * Math.Sin(2 * Math.PI * (steps - 1) / steps)); /* Continue previous sequence and execute the Pen actions. */ drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xSmile, ySmile, TimeSpan.Zero)); drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, centerX, centerY, TimeSpan.FromMilliseconds(400), new PenInfo { Pressure = .600f })); drawSequence.AddAction(penDevice.CreatePointerUp(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerDown(PointerButton.PenContact)); drawSequence.AddAction(penDevice.CreatePointerMove(CoordinateOrigin.Viewport, xSmile2, ySmile2, TimeSpan.FromMilliseconds(400))); // Execute sequence. newStickyNoteSession.PerformActions(new List<ActionSequence> { drawSequence });[/td] [/tr] [/table]

The additional pressure applied to the “smile strokes”—this is to add depth to the smile. The sketch should appear as the following:

Step 3 – Eyes

If we wanted to finish up and add eyes, it would look something like the following:

There’s a lot of clever ways you can go on about adding the eyes, so we’ll let you decide which way is best. The full code for our design will be included as part of the Sticky Notes sample on GitHub!

Details on full 1.1

The full release of v1.1 will come with the following additions:

WinAppDriver

Pen—support for Pen will be carried over to full 1.1 release from the Preview.

Multi-Touch—support for Multi-Touch will be added in as well through the Actions API. The following touch modifiers will be supported:

Pressure

Twist

New Samples & Bindings

Samples from the Preview will be further expanded to demonstrate Pen and Multi-Touch functionality. The samples will incorporate a private Appium-Dotnet-Driver Nuget feed that will enable Actions implementation via the new bindings. We’re looking into having these changes be merged into the official Appium .Net Driver, and eventually be rolled-up to the Selenium Namespace in the future.

Release Date

We’re targeting this June for the full release of v1.1—stay tuned to our GitHub board for more info!

Moving Forward

The WinAppDriver team will continue to work on adding new features, resolving bugs, and improving performance. We’ve been looking into popular community requests, and as such, have a couple of cool things in the pipeline for 1.2 and beyond—one in particular being to improve performance with XPath handling.

We’ll also be releasing a new tool for the community – more details on this to follow in the coming weeks. Stay tuned!

How do I provide feedback?

Please provide feedback on our Github issue board – we look forward to hearing about any suggestions, feature requests, or bug reports!

microsoft/WinAppDriver

If you have any cool sketches done through v1.1 that you’d like to share—do so on the GitHub board! It may even be featured in a future blog post!

Stay Informed

To stay up to date with WinAppDriver news follow @mrhassanuz.

Summary

The v1.1 Preview is available now—enabling users to automate Pen scenarios. Full release for v1.1 to follow, and with it will bring support for Multi-Touch as well. Head over to our releases page on GitHub to download the preview, and get a jump-start on Pen automation by reviewing our updated samples.
Click to expand...

Source: Announcing support for Pen with Windows Application Driver v1.1 - Preview available now - Windows Developer Blog

Windows 10: PowerShellGet 3.0 Preview 1 now available

PowerShellGet 3.0 Preview 1 now available

PowerShellGet 3.0 Preview 1 now available

PowerShellGet 3.0 Preview 1 now available

PowerShellGet 3.0 Preview 1 now available - Similar Threads - PowerShellGet Preview available

Visual Studio 2019 v16.9 and v16.10 Preview 1 now available

PowerShellGet 3.0 Preview 10 Release

PowerShellGet 3.0 Preview 6 now available

PowerShellGet 3.0 Preview 3 now available

Announcing .NET 5.0 Preview 3 now available

PowerShell 7.1 Preview 1 now available

Windows 10 SDK Preview Build 18970 available now - September 3

Visual Studio 2019 version 16.1 Preview 3 now available

Windows 10 SDK Preview Build 17704 now available - July 3