-
Version(s)4.0.0 (I also tested on 4.1.0) To reproduceSteps to reproduce the issue:
Expected behaviourI expected the project to build Actual behaviourProject doesn't build because a target of WPF is launched before MinVer and want to access the AssemblyVersion Error: NB: I used AssemblyVersion = WorkaroundsI can make it work if I add this target in my .csproj Additional contextIt seems that the target that generate baml file from xaml files launches before MinVer an makes this problem I don't know if it's me that doesn't use correctly MinVer with the AssemblyVersion but anyway I wanted to let you know of this problem ;) |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
@Sironas in your step to reproduce, what does this step mean?
How are you setting |
Beta Was this translation helpful? Give feedback.
-
@Sironas I'm closing this because a month has passed and you haven't replied. If you are still having problems, please re-open the issue with a response to my previous question. |
Beta Was this translation helpful? Give feedback.
-
@adamralph Sorry I was in holidays the last month I already said in the description of the issue how I set the version:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Sorry I thought it was obvious as I'm used to it. I will share with you an example In the .csproj I have this <Project Sdk="Microsoft.NET.Sdk">
...
<!-- Version number -->
<PropertyGroup>
<MinVerMinimumMajorMinor>1.0</MinVerMinimumMajorMinor>
<AssemblyVersion>$(MinVerMajor).$(MinVerMinor).$(MinVerPatch).0</AssemblyVersion>
<FileVersion>$(MinVerMajor).$(MinVerMinor).$(MinVerPatch).0</FileVersion>
<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>
</PropertyGroup>
...
</Project> |
Beta Was this translation helpful? Give feedback.
-
That will not work. The way to make this work is documented in the FAQ. |
Beta Was this translation helpful? Give feedback.
That will not work. The way to make this work is documented in the FAQ.