Worked fine for me just having a Microsoft/Live account. -- Espi
On Mon, Jul 28, 2014 at 6:45 AM, Nash Pherson <[email protected]> wrote: > You have to be signed into Connect to vote. If you haven't already, you > may also need to 'Join' the 'Windows PowerShell' and then must join the > product from the Directory. > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Carol Fee > *Sent:* Monday, July 28, 2014 8:38 AM > > *To:* '[email protected]' > *Subject:* [NTSysADM] RE: A PowerShell Favor Please > > > > Sorry - voting is closed > > > > *CFee* > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Webster > *Sent:* Friday, July 25, 2014 9:47 AM > *To:* [email protected]; [email protected] > *Subject:* [NTSysADM] A PowerShell Favor Please > > > > I found a bug in PowerShell and Michael got a PS MVP to report it. It is > now a public bug and can be voted on. I would appreciate you voting it UP. > > > > > https://connect.microsoft.com/PowerShell/feedback/details/928085/parameterset-names-should-not-be-case-sensitive > > > > This bug really cost me some time in getting the next update out to all 12 > of my documentation scripts. > > > > Thanks > > > > > > Webster > > >
