Closed zippy1981 closed 9 years ago
What's the aim here? Is this just to prepare for command-line arguments to set the default audio device's, etc?
I appreciate the effort, however, I don't want to use rundll32.exe, I want to own the entry process so that I can dictate and control the manifest and other things dictated by it including app compat settings, configuration, supportedRuntime, and probably ClickOnce in the future.
As an example, because rundll32.exe is manifested to support the Windows version it's built for, you've automatically opt'd AudioSwitcher into Windows 10's breaking changes (and all future OS changes) even though I've not actually tested this app on it.
Let's iterate over the design on the issue you filed, so I can get an understanding on what you want you want in terms of a CLI, and we can move from there.
Well powershell Cmdlets, not CLI arguments, but why not both if someone wants to control the audio device from cmd.exe.
For CLI arguments I don't need to do this. For powershell cmdlets, I need this to be a DLL, not an exe so I can load it as a powershell module.
Maybe the powershell cmdlets just need to be in a separate dll.
For Issue 19. Unfortunately we can't build this as AnyCPU for the unmanaged exports to work. It probably makes sense to just use the 32 bit dlls.