Search found 206 matches

by Lembasts
Tue Apr 16, 2019 8:59 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

So I noticed that 160 doesnt have UTF-8-BOM. So I suspect that maybe my encoding prior to 161 was just UTF-8 and when 161 was installed it changed the encoding automatically to UTF-8-BOM which caused it to fail?
by Lembasts
Tue Apr 16, 2019 2:35 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

Very interesting. Obviously got away with it in the past. The encoding is UTF-8-BOM. I replaced the hyphen in front of the Force and Identity and compiled it and it worked fine!' By the way I did a hex dump of the two characters: - 0x2D 45 – 0x2013 8211 The first one is a normal hyphen and the secon...
by Lembasts
Mon Apr 15, 2019 9:46 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

...and if you were wondering - I did a command line compile under 160 and it worked fine - no parsing errors.
by Lembasts
Mon Apr 15, 2019 8:18 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

When I did an export to file, these are lines 10494 to 10504: try { Set-ADAccountPassword –Identity $textboxUser.Tag.objectguid -Reset -NewPassword (ConvertTo-SecureString -AsPlainText "$($textboxpassword.text)" –Force) Set-ADUser -Identity $textboxUser.Tag.objectguid -ChangePasswordAtLogon $true } ...
by Lembasts
Mon Apr 15, 2019 5:28 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

So it appears to be parsing by 161. These are the errors when running the exe as command line: Line 10499: At line:10498 char:3 + { + ~ Missing closing '}' in statement block or type definition. At line:10499 char:158 + ... vertTo-SecureString -AsPlainText "$($textboxpassword.text)" –Force) +...
by Lembasts
Mon Apr 15, 2019 5:13 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

I am not dotsourcing but what do you mean by resolving scripts please?
And where do I find the encoding?
When I get a chance to reinstall 161 I will try the command line host.
by Lembasts
Mon Apr 15, 2019 3:56 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

Sorry - I didnt know exactly what details you wanted. Engine is V5 Host (Windows Forms). 64 bit. Any other settings you need? Why I dont think its code related is because if I compile it under 161, the exe does nothing. If I compile the exact same code with the exact same settings on 160 it works fi...
by Lembasts
Mon Apr 15, 2019 3:17 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

Sorry but we are a defence installation and for security reasons cannot share code.
by Lembasts
Mon Apr 15, 2019 3:00 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

I noticed that someone else posted the same thing so I figure something is up, particularly when it compiles OK with version 160 but not with 161. By does nothing means that when I double click on the exe, nothing happens. Task manager shows nothing running. No error message and nothing in Event Vie...
by Lembasts
Mon Apr 15, 2019 2:33 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 3509

Re: 161 compile no longer working

I have recompiled it with version 160 and it works fine.