Avoid inserting version if the attribute is not found

[Geekays]

For some of the projects that I build occasionally have an additional file AssemblyInfoCommon.cs with the version number stuff. So, I have to run this task for AssemblyInfo*.cs files. However, this task inserts the version attributes to the files if it does not contain one. This causes duplicate entries and builds to fail.

Is there a way to avoid inserting in case the file does not have one?

[Scordo]

Hi,

if I do understand you correctly AssemblyInfoCommon.cs does not contain version attributes and no version attributes should be placed in this file?!

So why do you include them in the filter? If you dont want them to be processed just choose a filter which does not include them like: AssemblyInfo.cs (which only Includes AssemblyInfo.cs but not AssemblyInfoCommon.cs)

If I got you wrong please help me better understand your problem.

Regards,
Jens

[Geekays]

Sorry, seems there is little confusion.

I am using the task to update AssemblyInfo.cs as well as AssemblyInfoCommon.cs as in some projects, the version attribute is in assemblyinfo.cs file. Whereas in some others, the version attribute is present in the assemblyinfocommon.cs file.

This works good for the projects (part of the source code) where the version is set in the AssmblyInfo.cs file only and the AssemblyInfoCommon.cs file is non-existent.

However, when the task runs on the code sections where we do have the version attribute in the AssemblyInfoCommon.cs and not in the AssemblyInfo.cs files, I see the challenge. This task updates the version in the AssemblyInfoCommon.cs file correctly but also inserts the Version Info in the AssemblyInfo.cs file there.

This causes the build to fail as it gets duplicate version tags.

So, if there could be a setting that says that "Don't insert version tag if the attribute is not available" then it will be helpful.

Hope, I could put the ask properly.

[Scordo]

Ok. Now I understand. This is currently not possible. As a workaround you could maybe add the task multiple times but with different path-filters. But this isn't nice. I'll have a look at supporting this scenario - But it will take a good amount of time, because I'm on vacation for the next 3 weeks.

[Geekays]

Great! Have a good vacation and enjoy.

I shall await the update.