search

Wintellect / WintellectPowerShell

PowerShell scripts for better debugging and life
http://www.wintellect.com
Other
178 stars 41 forks source link

Does not work with projects without Debug / Release configs #5

Closed francofs closed 8 years ago

francofs commented 8 years ago

I tried to use Set-ProjectProperties, but my Projects do not have Debug / Release configuration. I have my own custom configurations and maybe this is hardcoded in the module.

JohnWintellect commented 8 years ago

Look at the -Configurations and -CustomConfigurationProperties parameters. I hard coded Debug + Release as 99.99999% of projects have those configurations. Is this an internationalization issue?

francofs commented 8 years ago

Oh sorry, thanks for the pointer, I got it working after reading the source code. Maybe as a todo you could have the parameters on the readme.

Now it works. My configs are DEV, UAT, PRD. This is our continuous integration configurations so, that's why. We have automatic transformations for the configurations file that requires it to be this way.

Thanks again and nice work! It saved me a lot of time. I have over 40 projects in my solution.

JohnWintellect commented 8 years ago

Very cool! Glad to hear the module saved you some time. My day has been made! :+1:

These parameters are shown in the Set-ProjectProperties help (see the last example). Is that sufficient?

francofs commented 8 years ago

Oh yes, that is sufficient, I think I may have missed the example, but it's all good now :)

Thanks again. All the best!

On Thu, Apr 28, 2016 at 3:49 PM, John Robbins notifications@github.com wrote:

Very cool! Glad to hear the module saved you some time. My day has been made! [image: :+1:]

These parameters are shown in the Set-ProjectProperties help (see the last example). Is that sufficient?

— You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub https://github.com/Wintellect/WintellectPowerShell/issues/5#issuecomment-215525831