Canvas Pad Rectangles (simple shapes) HTML Canvas 2D Context specification: Section 8 Simple shapes (rectangles) context.clearRect(x, y, w, h) Clears all pixels on the canvas in the given rectangle to transparent black. context.fillRect(x, y, w, h) Paints the given rectangle onto the canvas, using the current fill style. context.strokeRect(x, y, w, h)) Paints the box that outlines the given rectangle onto the canvas, using the current stroke style. // Draw black rect ctx.fillRect(50, 20, 145, 145); // Draw blue rect ctx.fillStyle = "rgb(0, 162, 232)"; ctx.fillRect(135, 85, 125, 125); // Increase line width ctx.lineWidth = 5; // Draw black rect outline ctx.strokeStyle = "rgb(0, 0, 0)"; ctx.strokeRect(50, 335, 145, 145); // Draw blue rect outline ctx.strokeStyle = "rgb(0, 162, 232)"; ctx.strokeRect(135, 275, 125, 125); // Draw transparent yellow rect ctx.fillStyle = "rgba(255, 255, 0, 0.75)"; ctx.fillRect(210, 180, 125, 125); context.arc(x, y, radius, startAngle, endAngle, anticlockwise) context.clip()
Beginning with PowerShell and Word | Learn Powershell | Achieve More This first article will dip our toes into creating the Word Com object, looking at sending text to Word and adjusting some of the various fonts and styles to give you a stepping stone on what you can do. I will be using Word 2013 in this article, so your mileage may vary if using older versions. Creating the Word Object Like any COM object, we must use New-Object with the –ComObject parameter to tell PowerShell that we are loading up a Com object. Now I have created my object as shown in the image below. One thing that you might note is that we can’t see Word opened up, even though the process is actually active. To make Word visible, we have to set the Visibility of the object to $True. Now you should see that Word is visible. Writing to Word Writing to word is as simple as calling TypeText() and supplying a parameter which is text. Ok, nothing really mind blowing here, but this is how we can write in word using PowerShell. We work around this by calling TypeParagraph(). Working with Styles
Blogotec, VMWare, Hyper-v, NetApp Open source PowerShell on Windows, Linux, and OS X! This article was co-authored by Bartek Bielawski and Ben Gelens. Windows PowerShell is a powerful tool, but it always had one very serious limitation: it was possible to run it only on Windows. There had been several attempts to change that, including projects like Pash. However, without support from PowerShell Team these projects had very little chance of catching up with a platform that was growing with each release of PowerShell on Windows. Almost two years ago in November 2014 when it was announced that .NET Core will become open source project available for multiple platforms including Linux. PowerShell on Linux As you can see this announcement is huge – not only you can freely read and change the code of the PowerShell itself, you can build it and run it almost anywhere. sudo yum install powershell-6.0.0_alpha.9-1.el7.centos.x86_64.rpm PS /home/bielawb> rpm -qR powershell libunwind libicu rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Summary Like this:
Blog de Mathieu Chateau » Architecture / Microsoft / Réseau / Sécurité Windows PowerShell Tip: The String’s the Thing Here’s a quick tip on working with Windows PowerShell. These are published every week for as long as we can come up with new tips. If you have a tip you’d like us to share or a question about how to do something, let us know. The String’s the Thing One thing that separates Windows PowerShell from other shells (in particular the typical Unix shell) is this: while most operating system shells are text-based, Windows PowerShell is object-based. So does that mean that you never have to do text and string manipulation in Windows PowerShell? $a = "Scripting Guys" $b = "scripting guys" Comparing Two String Values So what kind of things do you need to do with string values? As you can see, we’re simply taking $a and calling the CompareTo method, passing the second string ($b) as the sole method parameter. When we run this command and echo back the value of $d we get the following: Which means that the two strings are different. What’s that? $d = [string]::Compare($a, $b, $True) Changing Text Case
Comment “cuisiner” une application Windows 8 avec HTML 5, CSS3 et JavaScript en une semaine–Jour 5 - Eternal Coding La Release Preview (RP) de Windows 8 vient de sortir et vous pouvez la télécharger ici: Du coup, il fallait bien que je porte mon petit UrzaGatherer vers la Release Preview avec comme objectif de le mettre sur le store au plus vite (afin de satisfaire les milliards de passionnés de Magic qui attendent la bave aux lèvres pour gérer leur collection de cartes !). Je vais également en profiter pour parler de quelques améliorations que j’ai apporté comme le support du binding par exemple. La version complète est donc disponible ici: L’intégralité de la série est disponible ici: Il existe un document permettant de porter vers la RP que vous pourrez trouver ici: Pour ma part, je reviendrai sur les sujets marquants de ma migration. Le nouveau navigator.js Le premier point que j’ai eu à modifier est le navigateur dans lequel j'ai ajouté quelques fioritures.
An interview with PowerShell expert Bruce Payette During the PowerShell Deep Dive at The Experts Conference (TEC) Europe 2011 in Frankfurt, Germany, Aleksandar Nikolic, one of the editors of the PowerShell Magazine, conducted a series of short video interviews with PowerShell experts. All of them were asked the same three questions: What is your favourite feature in PowerShell v3? As you can see, he’s cheated a little, and asked them four questions. We hope you will enjoy the interviews as much as we have enjoyed being at the first European PowerShell Deep Dive conference. The PowerShell Experts video series continues with the interview with Bruce Payette, Principal Developer with the PowerShell product team and the man behind the most famous PowerShell book — Windows PowerShell in Action! Like this: Like Loading...
Active Directory : guide de dépannage Sur cette page Active Directory : guide de dépannage Les outils utilisés Pour les tests hardware L'observateur d'événements (Event Viewer) Les outils inclus à l'OS Les "Supported tools" Network Connectivity tester : NetDiag Les Informations générales DCDIAG : Permet de tester les fonctions d'un DC Autres outils supportés Network Monitor Séquence de troubleshooting Tests généraux Test Hardware Vérification de la configuration IP Tests d'accessibilité Le réseau fonctionne-t-il ? Test des bindings Test de la couche NDIS Test de la couche NDIS Test de la configuration des modems pour les liaisons RAS Test de l'interface socket Affichage des informations de netstat Vérification de la configuration du redirecteur Tracer les échanges avec Network Monitor La résolution de nom fonctionne-t-elle ? Test des noms netbios Test des noms DNS Tests des noms DNS – Spécificités des DC Recherche du PDC Emulator : Tests des noms DNS – Vérification du serveur DNS LDAP fonctionne-t-il ? Test de LDAP avec LDP Test de binding Dans ce cas:
Create PowerShell Top-Down ETL Process III | Max Trinidad – The PowerShell Front On previous blog we have collect some data and built our .NET PowerShell object which is going to be loaded into our SQL Server. In this final section we are completing the process of loading the data into SQL Server. We need to make sure we got our Database and table previously created and ready to receive our data. For this process we’ll need to create 3 functions: 1. ConnectTo-SQLServer 2. Load-LogRecord 3. Of course we could do everything in one long script file. In order to connect to SQL Server, we’ll be using straight SMO classes to load the data. I’m keeping the functions in a basic level hardcoding some the PSObject variables instead of using parameter names. Function – ConnectTo-SQLServer Using SMO with a few lines of code we connect to a SQL Server engine. You will notice the use the of “$global:variablename” with some of the variable objects created. Function – Load-logRecord Function – Process-PSObjectToSQL This is the heart of loading the data. Executing the process
never stop exploring… » Blog Archive » The trust relationship between this workstation and the primary domain failed. Ever see that message before? How about on a machine that was previously working just perfectly? It’s anything but [OK]. So what is the fix when you encounter this problem? And most likely, you are probably right. To date, with over 12 years playing around with Active Directory and 16 years of playing with Windows Domains total I have yet to positively determine a case where AD broke and caused this issue. Certainly part of the issue is troubleshooting. Sidebar: So what is actually wrong? Then recently a friend of mine and former Microsoft Directory Services MVP (which is how I met him years and years ago) who will go nameless to protect the guilty was complaining about some issues he was seeing in an environment he works in around machines that were failing their trusts. So I dug into the my source code and saw where I got stuck and spent some nights walking through the Microsoft source code and completely failed to determine how to get nice clean clear text passwords out. joe
Microsoft SQL PowerShell Continnium | Max Trinidad – The PowerShell Front Yes! By now you all heard the news. SQL Server 2016 July update will include 25 new cmdlets for SQL PowerShell under the new module named SQLServer. Now, you need to know that this only with the installation of the “Microsoft Sql Server Management Studio” (MSSMS) available as an option on the SQL Server 2016 installation disk. Its a separate download. This link will take you to the following web page: Interesting to know that the SQLPS module hasn’t been renamed (just changed), as its still loaded on the “C:\Program Files (x86)\Microsoft SQL Server\130\Tools\PowerShell\Modules\SQLPS” folder. But, don’t worry about having SQLPS conflicts with the SqlServer cmdlets. Now, during my SQLServer 2016 new instance installation (No MSSMS) on a new image, I notice that SQLPS module get installed. You can verify all the modules you have installed on your machine by typing this simple oneliner: get-module -ListAvailable | Select name,path | sort name or
Reader (1000+)