You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When silly users, like me, specify feature IDs via /id 123456 instead of /id:123456 per the documentation, an unhandled exception occurs. (I only call this out because this also triggers my JIT debugger and interrupts my workflows.)
Version
ViVeTool v0.3.1
Steps to reproduce
Issue command: vivetool /enable /id 123456
Observe exception
Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Albacore.ViVeTool.ArgumentBlock.Initialize(String[] args, ArgumentBlockFlags flags)
at Albacore.ViVeTool.Program.ProcessArgs(String[] args)
at Albacore.ViVeTool.Program.Main(String[] args)
The text was updated successfully, but these errors were encountered:
Checking if value is null for various options in ArgumentBlock.cs and falling through if so seems to be the simplest fix here. Doing so will result in this output:
ViVeTool v0.3.1 - Windows feature configuration tool
Unrecognized parameter: /id
Unrecognized parameter: 123
No features were specified
If you're okay with that @thebookisclosed, I can submit a simple PR.
Summary
When silly users, like me, specify feature IDs via
/id 123456
instead of/id:123456
per the documentation, an unhandled exception occurs. (I only call this out because this also triggers my JIT debugger and interrupts my workflows.)Version
ViVeTool v0.3.1
Steps to reproduce
vivetool /enable /id 123456
The text was updated successfully, but these errors were encountered: