Open meastp opened 10 years ago
Hmm.
Interesting idea. I may be able to do something like that... I think I can look at it after I push out the next build (where I have a few dangling bugs).
G
Thanks. :)
I'm toying with the idea of using nuget packages + package restore for daily development workflow, and for this to work properly, every Build must generate a new nuget package. This feature would make the implementation easier.
I'm going to try and dedicate all next week to coding on the CoApp tools. I'll ping you when I'm closer to writing some code for this, as I want to make sure that I get it right.
Cool, thank you!
(I sent you an e-mail on this topic as well, earlier in my thought process (30 nov.). I think this feature makes that workflow possible and, hopefully, elegant :) )
Have you had time to look at this yet?
There are at least two use cases for this:
Creating a NuGet package during normal build with MSBuild/Visual Studio
When I build from Visual Studio, I am only building a single pivot configuration. To be able to reuse a single .autopkg file for everything, I will need to specify (with Visual Studio variables) which pivot configuration I have built, and will be creating a NuGet package for.
Example:
Write-NuGetPackage projectA.autopkg -SelectPivot $(DefaultPlatformToolset) $(Platform) $(Configuration) $(ConfigurationType)
Evaluates to e.g. :
Write-NuGetPackage projectA.autopkg -SelectPivot v120 Win32 Debug DynamicLibrary
(I realise that DynamicLibrary isn't currently an alias of dynamic Linkage pivot)
Flexibility during CI / nightly build
When I build all projects using a build server, I sometimes want to exclude a pivot configuration temporarily, while still using a single .autopkg file for everything.
Example. :
Write-NuGetPackage projectA.autopkg -SelectPivot v120 Win32 Debug DynamicLibrary -SelectPivot v120 Win32 Release DynamicLibrary
With a lot of pivots, it would be convenient to be able to exclude pivot configurations as well.