Search found 180 matches

by Lembasts
Fri Apr 19, 2019 5:04 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 927

Re: 161 compile no longer working

Thanks heaps!
by Lembasts
Wed Apr 17, 2019 5:31 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 927

Re: 161 compile no longer working

So I went through and changed all my files to UTF-8 using Version 161.
I opened a project in Version 160 and its saying the encoding is Windows-1252 , not UTF-8????
At this point I would really, really like some advice as to what exactly I should be doing with this encoding business please.
by Lembasts
Wed Apr 17, 2019 5:04 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 927

Re: 161 compile no longer working

So Im going through and manually changing dozens of psf file encoding from UTF-8-BOM back to UTF-8. I have some common files used in various projects. What I noticed was that when I changed one of the common files to UTF-8, and then opened that same file in another project, the encoding said Windows...
by Lembasts
Wed Apr 17, 2019 4:31 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 927

Re: 161 compile no longer working

And I also noticed that a few fancy fonts that I was using, like old english, no longer displayed.
I'm thinking that the fact it appeared to change UTF-8 to UTF-8-BOM automatically after installing 161 was a bad move.
by Lembasts
Tue Apr 16, 2019 8:59 pm
Forum: PowerShell Studio
Topic: 161 compile no longer working
Replies: 23
Views: 927

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: 927

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: 927

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: 927

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: 927

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: 927

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.