Another reason to not install the preview updates. However, if an enterprise hasn't mitigated for Printnightmare at this point I guess they really are going for the paperless office.

Great. Thank you again If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.

Well, nothing really needs to be "rebuilt" in this case. I just have a bunch of fully functional VMs sitting on a disk. Their config files aren't that important; what matters is their disks (VHD files). It's really not all that different than taking an existing hard drive and putting it into another machine so it can boot from it. What I needed to do in my case is create new VMs, but at the step where you can either create a new VHD or use an existing file - point it to an existing file on disk. I really don't think DSC could have contributed much here. I could very well be wrong, but that's not my understanding of what DSC tries to do.

Why are you not using the registry API directly rather than going through (antiquated) system() calls? "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles

MSI installer. Something to consider more. Thank you. :thumbsup:

Yes. I've been wanting to write something, might as well be this.

First, we started putting our stuff in the "My Documents" folder, and all was good. Then, applications started dumping their stuff in the "My Documents" folder. (Of 33 folders in mine, I created 5.) So we started putting stuff in our profile folder, and all was good. Then, other applications started dumping their stuff directly in the profile folder. (30 folders, 1 created by me.) I've given up on the profile folder. It's fine for user-specific app settings, but any files I want to manage have to go somewhere else to avoid being hidden in a deluge of crap created by applications which should know better. "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

I'm pretty sure that VS2019 doesn't change the dump setting, so you might try the other two. Unfortunately this may not be something that's documented, unless you find it on a discussion forum. Software Zen: delete this;

why not this? ^[A-z]+\.[A-z]+\d{1,2}$

Article has gone. Member has been here 7 years but no other recorded interaction with the site. I've put them on my watch list

Rage wrote: This smells like malware. Are you using Bing ? Aren't these the same?

1. Stop using VB6. It's been dead for over 20 years now. 2. The path you specify should not start with "\\?\". 3. The folders should not already exist. Trying to create C:\Windows or C:\Windows\System32 will fail as they already exist. 4. The Windows and Windows\System32 folders are protected from being written to by normal users. Any attempt to create folders or files in these folders will fail. 5. If I remember correctly (I haven't touched VB6 in over 20 years!) you don't even need Shell to do it. You can just do MkDir "C:\\MyFolder" Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

Chances are the account your ASP.NET site is running under does not have permissions to run Powershell. Try creating a normal user account and running your site under that account to test. No, that is not a viable solution if it does work. The entire point of having such a restricted account is to prevent security issues if someone gets your code to execute something malicious. Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

That's kinda beyond the point. I want to define rules once, at the source, not my individual clients. So it makes sense to do that when logging on the web site (outlook.com). Once *those* are sorted, it no longer matters what client (if any) I use on any of my machines - they should sync my folders with whatever state the server is in. I have tons of machines, both physical and virtual, and I may want to decide to access my mail from any one of them. I'm not going to install Thunderbird (or worse, the full Outlook client, which requires a license) everywhere I might decide I wanna access my email from.

Somehow, I'm guessing this will make PowerShell even harder to master. Our Forgotten Astronomy | Object Oriented Programming with C++