/build/static/layout/Breadcrumb_cap_w.png

extension table

hi guys,
i'm packaging a test app and added an extension thats starts with a numeric.. say "3ab" but when i validate the package it shows an ice03 invalid identifier error.. where is this coming from? any suggestions?

thanks =)
rick

0 Comments   [ + ] Show comments

Answers (4)

Posted by: rikx2 19 years ago
Purple Belt
0
additional.. i searched the msdn for this one but all i've come up is the identifier should always start with either a letter or an underscore? is this correct?

any advice or suggestion would be greatly appreciated
rick
Posted by: rikx2 19 years ago
Purple Belt
0
any advice or suggestions guys?

regards
rick =)
Posted by: MSIPackager 19 years ago
3rd Degree Black Belt
0
I had this same validation error with a package ages ago - just can't remember which one.

As far as I can recall you are correct - it fails validation because it starts with a number. Don't think it causes an issue as far as the package working correctly goes so I'd suggest you ignore it - you don't have a lot of options anyway unless you remove the entries in the extension table etc which would stop file association working..

Hope this helps, if I can remember the package I'll have a look to see what I did and let you know. Pretty sure I lived with it though [;)]

Cheers,
Rob.


Just found the package - it was Real Player 10 Gold and has extenstions 3gp and 3g2... works fine!
Posted by: rikx2 19 years ago
Purple Belt
0
thanks for the confirmation MSIPackager.. this just confirms what i have in mind..=)

regards
rick
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ