找回密码
 注册
搜索
[新手上路]批处理新手入门导读[视频教程]批处理基础视频教程[视频教程]VBS基础视频教程[批处理精品]批处理版照片整理器
[批处理精品]纯批处理备份&还原驱动[批处理精品]CMD命令50条不能说的秘密[在线下载]第三方命令行工具[在线帮助]VBScript / JScript 在线参考
查看: 13461|回复: 1

[转载代码] [PowerShell每日技巧]确保代码的向后兼容性(20140212)

[复制链接]
发表于 2014-2-19 14:42:16 | 显示全部楼层 |阅读模式
Let's assume you have created this function:
  1. function Test-Function
  2. {
  3.   param
  4.   (
  5.     [Parameter(Mandatory=$true)]
  6.     $ServerPath
  7.   )

  8.   "You selected $ServerPath"
  9. }
复制代码
It works fine, but half a year later in a code review, your boss wants you to use standard parameter names, and rename "ServerPath" to "ComputerName". So you change your function appropriately:
  1. function Test-Function
  2. {
  3.   param
  4.   (
  5.     [Parameter(Mandatory=$true)]
  6.     $ComputerName
  7.   )

  8.   "You selected $ComputerName"
  9. }
复制代码
What you cannot easily control, though, is who else calls your function, and may still use the old parameter. So to ensure backward compatibility, make sure your function can still work with the old parameter name, too:
  1. function Test-Function
  2. {
  3.   param
  4.   (
  5.     [Parameter(Mandatory=$true)]
  6.     [Alias("ServerPath")]
  7.     $ComputerName
  8.   )

  9.   "You selected $ComputerName"
  10. }
复制代码
Old code can now still run, and new code (and code completion) will use the new name:
PS> Test-Function -ComputerName server1
You selected server1

PS> Test-Function -ServerPath server1
You selected server1


http://powershell.com/cs/blogs/tips/archive/2014/02/12/ensuring-backward-compatibility.aspx
 楼主| 发表于 2014-2-19 14:43:02 | 显示全部楼层
如果需要定义两个参数的别名:
  1. [Alias("ServerPath","CN")]
复制代码
您需要登录后才可以回帖 登录 | 注册

本版积分规则

Archiver|手机版|小黑屋|批处理之家 ( 渝ICP备10000708号 )

GMT+8, 2026-3-17 00:27 , Processed in 0.016353 second(s), 8 queries , File On.

Powered by Discuz! X3.5

© 2001-2026 Discuz! Team.

快速回复 返回顶部 返回列表