I ran into a language issue the other day when writing a PowerShell script that uses net localgroup and thought it could be useful to others: Depending on the language your Windows device is set to, the local Administrators group will be different, so the typical net localgroup administrators domain\user /add command will fail. Implementing the following will grab the actual name of the group by it's SID first, then use that result. Note that this is written to work in PowerShell, not CMD.exe. # Gets the name of the local Administrators group in appropriate language $localAdminGroupName = (Get-WmiObject win32_group -filter "LocalAccount = $TRUE And SID = 'S-1-5-32-544'" | Select-Object -Expand name) Write-Output "Local Administrators group detected as: [$localAdminGroupName]" # Sets the users as a local admin using appropriate local Administrators group name net localgroup $localAdminGroupName domain\user /add # Gets local Administrators group members net localgroup $localAdminGroupName

@scottalanmiller said in Managing Windows Local Users with Net User: @JasGot said in Managing Windows Local Users with Net User: I'm using backstage more I assume that this is a component of another product? Part of ConnectWiseControl. (or ScreenConnect as we still call it around here.) It's at the bottom of the View tab when attached to a guest. Takes you to a new sessions as a System account with a command prompt and powershell window already open. No limit to what you can accomplish there. many gui apps will run in backstage too.

Worth noting that this was recording some time ago. Now Microsoft's new development platform, Visual Studio Code, has C# and F# support, but support for VB.NET has been dropped in it. This is the first time that MS has actively started to remove VB support from part of its ecosystem. Traditionally it was just kept on the back burner or given as an "extra" example. But now, for the first time, it is actually being left out.

I see what you mean. And also, if you're making the change in the web.config, that should trigger an application restart anyway. Something is preventing the pageSecurity object from being set. You could do a global text search for "pageSecurity" and find the code that sets it. That may be where the failure is happening. Normally I would expect this to be caused by a missing security-related table, like Roles or something. But you said it was a full copy. You might want to double check.

Awesome, this is what we need to get C# and F# into the open source ecosystem.

Apparently some counterpoint has come out... http://techrights.org/2014/11/12/openwashing-lockin/

And of course books. These two look best to me: http://www.amazon.com/Microsoft-Visual-2013-Step-Developer/dp/073568183X/ref=sr_1_3?ie=UTF8&qid=1402673332&sr=8-3&keywords=c%23 http://www.amazon.com/Head-First-C-Jennifer-Greene/dp/1449343503/ref=sr_1_4?ie=UTF8&qid=1402673332&sr=8-4&keywords=c%23