Wrong numeric precision when comparing database with files

aibo

I am wondering if anyone else had experienced the same problem that SQL compare reports wrong precision for numeric parameter on CLR stored procedure. I have just updated to SQL Compare 8.2 and have been using 7.x. I have CLR assembly being called via CLR stored procedure. I maintain a script file for each object in the database (i.e. one file per sp, function, table, etc). SQL compare consistently report the precision of numeric input parameter on CLR stored procedure wrong. It always reports precision of 0, although the script files clearly showing something else. It is however reading the precision correctly from the live database.
This is causing me issues as I am using the individual script files for source control and automated deployment. Now I have to correct this manually every time!

Thanks!

James B

Just to let you know I have mailed you directly to go through the problem.
Thanks!