MSDN

Facebook Twitter
Powershell Research - OpenFlags Enumeration (System.Security.Cryptography.X509Certificates) Specifies the way to open the X.509 certificate store. [FlagsAttribute] public enum OpenFlags The following code example opens an X.509 certificate store, adds and deletes certificates, and then closes the store. Powershell Research - OpenFlags Enumeration (System.Security.Cryptography.X509Certificates)
Represents an X.509 store, which is a physical store where certificates are persisted and managed. This class cannot be inherited. System.ObjectSystem.Security.Cryptography.X509Certificates.X509Store Powershell Research - X509Store Class (System.Security.Cryptography.X509Certificates) Powershell Research - X509Store Class (System.Security.Cryptography.X509Certificates)
Specifies the name of the X.509 certificate store to open. This enumeration specifies the X.509 store name, which also includes the type of certificates included. For example, My includes personal certificates, whereas Disallowed includes only revoked certificates. Powershell Research - StoreName Enumeration (System.Security.Cryptography.X509Certificates) Powershell Research - StoreName Enumeration (System.Security.Cryptography.X509Certificates)
Adding Custom Cmdlet Help for Providers - Windows PowerShell Blog Adding Custom Cmdlet Help for Providers - Windows PowerShell Blog A new feature of Windows PowerShell 2.0 lets you write custom cmdlet help for Windows PowerShell providers. This blog explains how to do it. (The topic will also be covered in excruciating detail in MSDN, but we don't want you to wait.) What's a Provider? A Windows PowerShell provider is a C# program that exposes a data store to Windows PowerShell through a Windows PowerShell drive (PSDrive).
Merry Christmas From PowerShell: The CodeDownloader Module - Windows PowerShell Blog Twas the night before Christmas, and all through the net PowerShell lovers were wondering exactly what they might get Their readers were ready, their minds were aware That more joy of CTP3 would soon be there A cmdlet, a function? What has the PowerShell team done? How about a whole module, to share scripts with everyone? Merry Christmas From PowerShell: The CodeDownloader Module - Windows PowerShell Blog
Get-CommandPlugin - Windows PowerShell Blog Get-CommandPlugin - Windows PowerShell Blog One of the nifty new CTP3 features is command and parameter meta data on functions. In V1, you had to parse a function yourself to extract the parameters. In CTP2, you could use the tokenizer API to parse the function, but extracting parameters this was is error prone. In CTP3, and in V2, you can actually get a dictionary of parameters on the FunctionInfo object. Check it out: Get-Command -type Function | Foreach-Object { $_.Parameters }
Examples of Host Application Code In This Section This section includes the following topics. This example shows how to write a host application that invokes a command synchronously on the local computer. This example shows how to add cmdlets and their parameters to the command pipeline of a host application. After the command pipeline is complete, the host application invokes the pipeline synchronously on the local computer. This example shows how to add a custom host to a host application. Examples of Host Application Code
Writing a Windows PowerShell Cmdlet
Adding Parameters that Process Command-Line Input The following sections are in this topic: Defining the Cmdlet Class [Cmdlet(VerbsCommon.Get, "proc")] public class GetProcCommand: Cmdlet Adding Parameters that Process Command-Line Input
The topics in this section provide development guidelines that you can use to produce well-formed cmdlets. By leveraging the common functionality provided by the Windows PowerShell runtime and by following these guidelines, you can develop robust cmdlets with minimal effort and provide the user with a consistent experience. Additionally, you will reduce the test burden because common functionality does not require retesting. In This Section See Also Cmdlet Development Guidelines Cmdlet Development Guidelines
What is LightSwitch?
LightSwitch Tutorials | Learn Lightswitch on MSDN
"How Do I?" Videos for Visual C#
Writing a Windows PowerShell Host Application
Using PowerShell to read xml-files - Little more than out of the box development Using PowerShell to read xml-files - Little more than out of the box development A couple of months ago a colleague and I decided to try to build a demo-environment for SharePoint. We wanted to be able to take a new fresh installed Windows 2003 (or 2008) server, and just run a PowerShell script and then the environment should be up and running. The environment should of course include sample data, sites, and last but not least a number of users.In order to do this we first had to learn PowerShell. Always fun to learn new things! This post is about how we use PowerShell to read the userdata from the xml-file. Step 1: Download PowerShell from here: PowerShell Download Step 2: install it.
Cmdlets can perform their action internally or as a Windows PowerShell background job. When a cmdlet runs as a background job, the work is done asynchronously in its own thread separate from the pipeline thread that the cmdlet is using. From the user perspective, when a cmdlet runs as a background job, the command prompt returns immediately even if the job takes an extended amount of time to complete, and the user can continue without interruption while the job runs. Background Jobs
Cmdlet Help Editor V2.0 with Module Support - Windows PowerShell Blog Hi, I have updated the Cmdlet Help Editor tool to support Modules. The V1.0 version of this tool only supported PsSnapins. The original post can be found here
Designing useable cmdlets is part engineering and part art. It’s not an easy task to define the conceptual boundaries of a cmdlet (where does one cmdlet end and the next begin) or to provide great feature control without inundating the user with parameters. However, you can improve the usability of your cmdlets by avoiding two common parameter set design flaws. A parameter set with no mandatory parameters in a cmdlet that requires parameters Mandatory parameters with position numbers that are higher than the position numbers of optional parameters Parameter sets with no mandatory parameters Improving Parameter Set Design - Windows PowerShell Blog
Improving Parameter Set Design - Windows PowerShell Blog
Designing Cmdlets That Have Lots of Parameters - Windows PowerShell Blog We often get the question of what to do about a cmdlet that has lots of parameters. Do you break it up into multiple commands or just have a single cmdlet with lots of parameters. Here is the way I think about it: If you have to enter 100 things to get a job done, it doesn’t really matter whether you enter those 100 things via 1 cmdlet with 100 parameters or 10 cmdlets with 10 parameters each.
PowerShell PowerBook