Nate McMaster

I was able to get this working by setting both publicPath and outputPath like this ```js new AddAssetHtmlPlugin({ filepath: path.resolve('./dist/js/*.dll.js'), includeSourcemap: false, publicPath: '/dist/js', outputPath: 'dist/js' }) ``` Result: no...

This request sounds reasonable. I think the current form of generic host integration can be adjusted to accommodate this, though I'm not completely sure how. @wasabii made a similar request...

> do you have a pointer what I could use to make the argument parsing work without creating a separate command line application? Is that even possible? Yes and no....

I've seen the `--[no-]option` pattern before, but struggling to remember where and how it was useful. Do you have some concrete examples of what a user would do with this?

After though: I've also seen `--[disable/enable]-feature`, so need to be careful about being too opinionated on naming conventions.

I think this idea needs to be fleshed out a little more. I thought I knew what you were asking, but then your response didn't fit with my original assumptions....

@JakeSays your suggestion on toggle enum is an interesting idea. I think I would implement it slightly differently though. What do you think of usage that looks like this? ```csharp...

Sorry, allow me to clarify. I meant for `ToggleState` to be something from user code, not in this library. Maybe this makes it clearer? ```c# Option myMappedOption = app.AddMappedOption(o =>...

I'd rather just have one API which supports both short and long options. ```c# Option myMappedOption = app.AddMappedOption(o => { o.Map("-b|--banana", FruitOption.Banana); o.Map("-a", FruitOption.Apple); o.Map("-p|--pear", FruitOption.Pear); }); ```

My two cents: > is there any idea how to present this in help-output? I was planning to start with this for simplicity: ``` Usage: ConsoleApp1 [options] Options: -i|--int IntOption...