-
Notifications
You must be signed in to change notification settings - Fork 7
Assembly Patching #5
Comments
No, all assembly info is generated based on what it says in the project.json files. The assembly patching in AppVeyor runs before any assembly info code generation takes place. |
Hmm, ok. So does that mean you cant have an auto increment of the verions number besides the version prefix ? Thanks for your help |
I'm not sure but I think you can control the version info using environment variables
It's not clear if You might try something like this: ps: $Env:DOTNET_BUILD_VERSION = "1.0.$Env:APPVEYOR_BUILD_NUMBER-CI"
ps: $Env:DOTNET_ASSEMBLY_FILE_VERSION = "1.0.$Env:APPVEYOR_BUILD_NUMBER" |
I test that out and report back soon. |
I am getting The assembly file version is invalid: 1.0..51 |
I forgot that assembly versions have 4 components instead of 3. It's interesting that dotnet parses it as Try setting all 4 components: |
already tried it with no luck :) I found where the exception happend |
@dknaack did you figure out a solution? |
Do someone know if Assembly Patching does work? Cant get it work.
Thanks in advance!
The text was updated successfully, but these errors were encountered: