# Vs.net solution with prism project writes invalid version to assemblyinfo

**URL:** https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221
**Category:** Discussion
**Created:** [June 1, 2009, 11:20am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221 "2009-06-01T11:20:01Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![rasmusw](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/r/46a35a/32.png) [@rasmusw](https://www.finalbuilder.com/forums/u/rasmusw)
#### Post date: [June 1, 2009, 11:20am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/1 "2009-06-01T11:20:01Z")

</div>

I am testing Finalbuilder with a Delphi Prism project. I am using the vs.net build action and want to update the version.

It seems to write an incorrectly formatted AssemblyVersion string to the AssemblyInfo.pas file:

![]()[assembly: AssemblyVersion(0.3.2.1)]

The build fails, and it seems to be because the version string is not encapsulated in single quotation marks ('').

Without the version update option the build seems to work fine.

What can I do to make the version update function correctly?

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [June 2, 2009, 2:09am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/2 "2009-06-02T02:09:28Z")

</div>

Did the attribute exist in the file before or is this being added to the file by FinalBuilder. If an attribute already exists in a file, then FinalBuilder makes it’s decision based on whether there are quotes there or not. The reason for this is that the parser has no actual knowledge about particular attributes, it treats them all the same so if there are quotes there already then it will respect that, if there are not quotes there it will respect that. When adding a new attribute it will use whatever is specified in the value.

---

<div class="post-metadata">

### Author: ![rasmusw](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/r/46a35a/32.png) [@rasmusw](https://www.finalbuilder.com/forums/u/rasmusw)
#### Post date: [June 11, 2009, 9:43am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/3 "2009-06-11T09:43:16Z")

</div>

The AssemblyVersion attribute is already present in the file, but Finalbuilder does not respect the existing quotes.

Before:

[assembly: AssemblyVersion('0.1.0.1')]

After:

[assembly: AssemblyVersion(0.3.0.1)]  
&nbsp;

The action used to build is the VS. Net Solution build, and I have checked the "Assembly Version" option and entered the new version on the ".NET&nbsp;version" tab in the action properties.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [June 12, 2009, 2:33am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/4 "2009-06-12T02:33:47Z")

</div>

Thanks, I was able to reproduce it here, we’ll have a build with the fix available later today.

---

<div class="post-metadata">

### Author: ![paulsamways](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/p/e8c25b/32.png) [@paulsamways](https://www.finalbuilder.com/forums/u/paulsamways)
#### Post date: [June 12, 2009, 6:35am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/5 "2009-06-12T06:35:58Z")

</div>

Hi Rasmus,   
  
 Here’s the new build of FinalBuilder which should fix the version updating issues you were having:   
  
 URL: [https://www.finalbuilder.com/downloads/finalbuilder/630/FB630\_1555.exe](https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1555.exe)  
  
 Regards,   
 Paul.

---

<div class="post-metadata">

### Author: ![rasmusw](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/r/46a35a/32.png) [@rasmusw](https://www.finalbuilder.com/forums/u/rasmusw)
#### Post date: [June 12, 2009, 8:55am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/6 "2009-06-12T08:55:26Z")

</div>

Thank you for the quick fix, unfortunately, there is still a small issue:  
It is now adding the quotes, but missing a closing square bracket.

After FB changes the assemblyversion, the line looks like this:

[assembly: AssemblyVersion('0.3.0.2')

- note the missing ] at the very end.

&nbsp;

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [June 15, 2009, 6:00am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/7 "2009-06-15T06:00:53Z")

</div>

My apologies, the change I made to the parser last week didn’t quite work as expected, didn’t have prism installed to test with. I have now installed prism (had some issues with licensing) and have fixed and tested fix :   
  
 [https://www.finalbuilder.com/downloads/finalbuilder/630/FB630\_1560.exe](https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1560.exe)

---

<div class="post-metadata">

### Author: ![rasmusw](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/r/46a35a/32.png) [@rasmusw](https://www.finalbuilder.com/forums/u/rasmusw)
#### Post date: [June 17, 2009, 8:23am UTC](https://www.finalbuilder.com/forums/t/vs-net-solution-with-prism-project-writes-invalid-version-to-assemblyinfo/1221/8 "2009-06-17T08:23:22Z")

</div>

Excellent, it seems to work now.   
 Thank you again for the quick fix.
