Comments on: The Active Directory PowerPack, the Quest AD cmdlets, and what can happen when you change public object interfaces or cmdlet parameter attributes in PowerShell http://poshoholic.com/2009/05/01/the-active-directory-powerpack-the-quest-ad-cmdlets-and-what-can-happen-when-you-change-public-object-interfaces-or-cmdlet-parameter-attributes-in-powershell/ Totally addicted to PowerShell Thu, 09 Feb 2012 00:54:13 +0000 hourly 1 http://wordpress.com/ By: What’s new in AD cmdlets 1.2.2 « Dmitry’s PowerBlog: PowerShell and beyond http://poshoholic.com/2009/05/01/the-active-directory-powerpack-the-quest-ad-cmdlets-and-what-can-happen-when-you-change-public-object-interfaces-or-cmdlet-parameter-attributes-in-powershell/#comment-1191 Tue, 16 Jun 2009 18:05:00 +0000 http://kirkmunro.wordpress.com/2009/05/01/the-active-directory-powerpack-the-quest-ad-cmdlets-and-what-can-happen-when-you-change-public-object-interfaces-or-cmdlet-parameter-attributes-in-powershell/#comment-1191 [...] Fixed the Connection property and other incompatibility issues which affected Kirk’s AD PowerPack. [...]

]]> By: Jason Archer http://poshoholic.com/2009/05/01/the-active-directory-powerpack-the-quest-ad-cmdlets-and-what-can-happen-when-you-change-public-object-interfaces-or-cmdlet-parameter-attributes-in-powershell/#comment-1028 Mon, 04 May 2009 23:29:31 +0000 http://kirkmunro.wordpress.com/2009/05/01/the-active-directory-powerpack-the-quest-ad-cmdlets-and-what-can-happen-when-you-change-public-object-interfaces-or-cmdlet-parameter-attributes-in-powershell/#comment-1028 Generally it is agreed that you can introduce breaking changes for a major release (but not minor releases) as long as you make sure that users/customers are aware of the change(s). But you should seriously think about them.

]]>