Joel Bennett

Well ... you're not wrong. Adding the extra module probably should have been marked as a breaking change. The only reason it wasn't is that Metadata has always been a...

I'm also really sorry I don't pay more attention to the issue trackers! I don't think I can do anything about this now, however -- no point making a breaking...

Hmm, that's weird. That script is really just two lines: ```PowerShell Install-Script Install-RequiredModule Install-RequiredModule ``` The first line seems to have worked... Which should mean the second line can work!...

The answers to this *really* depend on how you want to set breakpoints and debug. Are you debugging in a console or by pressing F5 in an IDE? How do...

@mattmcnabb sorry to answer after so long ... Have you looked at `Convert-LineNumber`? I missed an alias I should have had ("Script") but if you add it to the type...

Not sure I agree, in principle. I rather think the Metadata module should force UTF8 without BOM (but that wasn't an option on Set-Content at the time, so I settled...

It sounds useful to be able to set a single setting at a specific level ... As a general case, I don't think I want to support importing a specific...

I think the main thing I want is for `Update-Metadata` to support _adding_ fields that aren't there, and then _maybe_ incorporate that into Configuration as: ```PowerShell Update-Configuration -Scope User -KeyName...

Does _anything_ use that property?

In an earlier project, I used that value to restrict which files would be packaged into the module package so that you could, for instance, have a config file in...