Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Anatomy of a fob file
xo
Member Posts: 34
Has anyone tried to dissect the fob file format?
It would be interesting with a knowledge base of known facts about the format.
I have a simple use-case for such information: comparing two objects and detecting whether they are "mostly equal", where mostly means I don't care about things like the object date and time. In addition it appears that the binary changes after each compile. So I want to create a small tool which isolates details such as these and does a comparison of two fob files but skipping over these parts. It could also be used to create "semantic" hashes.
I can probably figure out the basics by trial and experimentation but if someone has done the legwork it could save some time.
Another interesting aspect is changes to the fob file format that one has to be aware of (especially with respect to the above).
Thanks in advance.
It would be interesting with a knowledge base of known facts about the format.
I have a simple use-case for such information: comparing two objects and detecting whether they are "mostly equal", where mostly means I don't care about things like the object date and time. In addition it appears that the binary changes after each compile. So I want to create a small tool which isolates details such as these and does a comparison of two fob files but skipping over these parts. It could also be used to create "semantic" hashes.
I can probably figure out the basics by trial and experimentation but if someone has done the legwork it could save some time.
Another interesting aspect is changes to the fob file format that one has to be aware of (especially with respect to the above).
Thanks in advance.
0
Comments
why don't you use the text export for this? Then you can use a comparison tool like Beyond Compare.
Hope this helps,
Willy