# AssemblyInfo Updater does not update fully qualified attributes
**URL:** https://www.finalbuilder.com/forums/t/assemblyinfo-updater-does-not-update-fully-qualified-attributes/7060
**Category:** Bugs
**Created:** [June 14, 2021, 9:52pm UTC](https://www.finalbuilder.com/forums/t/assemblyinfo-updater-does-not-update-fully-qualified-attributes/7060 "2021-06-14T21:52:08Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@greg](https://www.finalbuilder.com/forums/u/greg)
#### Post date: [June 14, 2021, 9:52pm UTC](https://www.finalbuilder.com/forums/t/assemblyinfo-updater-does-not-update-fully-qualified-attributes/7060/1 "2021-06-14T21:52:09Z")
This is another wrinkle to this [issue](https://www.finalbuilder.com/forums/t/assemblyinfo-updater-does-not-update-default-assemblyinfo-cpp-properly/3147). If one uses fully qualified paths rather than having using statements, the AssemblyInfo Updater appends unqualified attributes that fail. An example is shown below:
```auto
[assembly: System.Reflection.AssemblyVersion("1.0.0.0")]
[assembly: System.Reflection.AssemblyCompany("My Company, Inc.")]
[assembly: System.Runtime.CompilerServices.RuntimeCompatibility(WrapNonExceptionThrows=true)]
[assembly: System.Reflection.AssemblyProduct("ApplicationHandler")]
[assembly: System.Reflection.AssemblyCopyright("")]
[assembly: System.Diagnostics.Debuggable(System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations | System.Diagnostics.DebuggableAttribute.DebuggingModes.EnableEditAndContinue | System.Diagnostics.DebuggableAttribute.DebuggingModes.IgnoreSymbolStoreSequencePoints | System.Diagnostics.DebuggableAttribute.DebuggingModes.Default)]
[assembly: System.Reflection.AssemblyTitle("ApplicationHandler")]
[assembly: System.Reflection.AssemblyDescription("Simplifies manipulating Hwnd items.")]
[assembly: System.Reflection.AssemblyConfiguration("")]
[assembly: System.Runtime.CompilerServices.CompilationRelaxations(8)]
[assembly: System.Reflection.AssemblyTrademark("")]
[assembly: System.Runtime.InteropServices.ComVisible(false)]
[assembly: System.Runtime.InteropServices.Guid("beba9058-7a17-4079-81d8-f76f22da5260")]
[assembly: System.Reflection.AssemblyFileVersion("1.0.0.0")]
#region Assembly Information Added By FinalBuilder
[assembly: AssemblyFileVersion("1.6.1.1610")]
[assembly: AssemblyVersion("1.6.1.1610")]
#endregion
```
Note: Only one project of the 50+ in the solution was done this way so we are just changing it. However since the syntax is correct even if non-standard, it seems like the action should be able to handle it correctly. Using FB 8.0.0.2983.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [June 15, 2021, 12:27am UTC](https://www.finalbuilder.com/forums/t/assemblyinfo-updater-does-not-update-fully-qualified-attributes/7060/2 "2021-06-15T00:27:30Z")
I agree this is not great, will look into it.
FWIW, the only two attributes that the action actually has any knowledge of is those two it’s getting wrong! I guess you are updating those from a property set as that is the only time I could see this happening? If not then it’s just a case of fully qualifying them in the action.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [June 16, 2021, 12:54am UTC](https://www.finalbuilder.com/forums/t/assemblyinfo-updater-does-not-update-fully-qualified-attributes/7060/3 "2021-06-16T00:54:04Z")
This turned out to be harder to deal with than I would have thought. The way the action is structured, it has no way of knowing that the file has fully qualified versions of the attributes before it generates the new/updated entries from the property set. Changing this would be a major amount of work, so as a work around I added a new option to fully qualify those two attributes from the property set (defaults to false). Will be in the next update.