This will most likely be the last version of Carbon tested and supported on PowerShell 2. We’ll be moving the build server to PowerShell 3 sometime around August 15th, which means that’s the version of PowerShell the automated tests will use. We encourage everyone to upgrade to PowerShell 3 as soon as possible.
- Created Install-Junction function for creating new and/or updating existing junctions. This is a more idempotent way of creating junctions, as opposed to New-Junction and Remove-Junction which report errors if a junction already exists or doesn’t exist, respectively.
- Objects returned by Get-IisWebsite now have a dynamic
PhysicalPathscript property, so you don’t have to traverse down into the default application’s default virtual directory object to get it.
- Install-IisApplication, Install-IisWebsite, and Install-IisVirtualDirectory now canonicalize physical paths, i.e. they convert any path with a relative part (e.g. ‘..’) to a full path. It turns out IIS doesn’t like paths with relative parts.
- Created Get-IisApplication function to get
Microsoft.Web.Administration.Applicationobjects for all or specific applications under a website.
- Install-IisApplication now uses the
Microsoft.Web.AdministrationAPI instead of
ExecutionPolicyparameter to Invoke-PowerShell to allow setting a custom exeuction policy when using Invoke-PowerShell to run a script.
- Install-IisApplication not updating/changing physical path on existing application.