Hi,
had to do a manual installation, because of the multiple VS 2017 Instances Issue.
I would appreciate a little powershell skript in the folder which Unblocks the files
Get-ChildItem -r *.* | unblock-file
and starts devenv.exe and wait's for exiting ;)
Best Regards
Albert
Remco NCrunch Developer
#10381
16 May 2017 09:48 UTC
Thanks Albert. I saw your post in the other thread about the bad experience here .. sorry about that.
The powershell script is a good idea. I've had many support requests raised over the years about blocked at O/S level.
Edit: I'd need to test whether the powershell script would need to be unblocked before it could unblock the files. That could be a bit of a problem.
The powershell script is a good idea. I've had many support requests raised over the years about blocked at O/S level.
Edit: I'd need to test whether the powershell script would need to be unblocked before it could unblock the files. That could be a bit of a problem.
Edited 16 May 2017 09:52 UTC
Yes, the PowerShell must probably also unlocked bevor running. also it must run as Administrator (which should be checked in the skript).
But unblocking one file is easy, unblocking dozens is work.
But unblocking one file is easy, unblocking dozens is work.
Edited 16 May 2017 13:29 UTC
Remco NCrunch Developer
#10386
16 May 2017 22:03 UTC
Isn't it simply possible to Ctrl+A, right click, properties, unblock all of them? Or does the directory structure complicate this?
1) I think unblocking works only file per file, not sure about this
2) But there are different Filetypes so unblocking all is not possible (this is was i first tried)
3) the directory structure complicates this, because it has to be done in every directory
A PowerShell Skript would be nice. But a Copy & Paste from the manual installation instructions of the right command could be feasible, and solves the 'have to unblock the powershell' problem.
2) But there are different Filetypes so unblocking all is not possible (this is was i first tried)
3) the directory structure complicates this, because it has to be done in every directory
A PowerShell Skript would be nice. But a Copy & Paste from the manual installation instructions of the right command could be feasible, and solves the 'have to unblock the powershell' problem.
Edited 18 May 2017 05:50 UTC
Post a reply
Log in to reply.