-
Notifications
You must be signed in to change notification settings - Fork 60
Error when Build-Module params are specified but no Build.psd1 present #44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ultimately, build.psd1 is basically our project file -- we're even calculating relative paths relative to the build.psd1 -- if it was called build.psproj would you still be trying to get rid of it? I suppose you would. I don't know. One problem with this is: what is |
So, now that all the paths are relative to the module.psd1 instead of the build.psd1 ... |
I'm waiting for the current version to be released before tackling this one, as I need it for my current project. |
Sorry that took so long. |
@gaelcolas This issue should be resolved once the PR #90 is merged? |
When invoking the command Build-Module with required Parameters like this:
Build-Module -Path .\Source\ModuleBuilder.psd1 -OutputDirectory ..\ -VersionedOutputDirectory
but the
Build.psd1
file is absent, we get the error below.The only way to work around it is to create a
Build.psd1
with an empty hashtable.I think we should make that file optional when required parameters are provided, and clearer error when not.
The text was updated successfully, but these errors were encountered: