[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[amibroker] Re: Anyone using a System-CheckSum?


  • Date: Sun, 28 Feb 2010 16:57:30 -0000
  • From: "dotnetsdkforab" <dotnetsdkforab@xxxxxxxxx>
  • Subject: [amibroker] Re: Anyone using a System-CheckSum?

PureBytes Links

Trading Reference Links

Hi All,

my guess is that your problem is the reliability of a trading system deployment. Checksum does not ensure that deployment is successfull and the deployed system is working. It is just a help to troubleshoot an already failing system!

I think it should be addressed with a decent "design - code - test - build - deploy" development cycle. Source control tools are part of this process. They help coding, but they do not replace build and deloy phase.

Once this process is in place there is no need to use checksum. If you still find something suspectfull you can use windiff (compare files and directories) or other tools to quickly detect the problem.

To give you some hints, here is my cheep solution for AFLs:
I code in a work folder that AmiBroker do not use directly. (This is where I have my source control sw set up.)
When I'm done with coding I run a project build script (simples cmd file) that copies all afls in that project into a folder stucture similar to AmiBroker's folder structure.
This project folder stucture is DELETED AND RECREATED at each builds from the actual sources! After build has run I have a complete set of files for that project. It has a deploy command (simple cmd file) as well, that will copy all files to the local AB folders.
If I'm on my dev machine I run the build and deploy cmds one after another and I test my coding. If I find any coding error, I fix it in the work directory and start over again. (build and deploy is only 1 second.)
Once all bugs are removed, and  project is tested, I need to label my source files, save and label the last project folder structure and copy it to target machines. There I run the SAME deploy.cmd as on the dev and test machines.

My "general includes" was a separate project. If I "touched" it, I rebuilt all other projects and tested them all. This project was always deployed with the other projects that used it.
It is now a plugin. This plugin's latest version is also deployed along any AFL project.

I keep the last deployed project structure on the target machines. If I would find any issue I just compare its files against files in AB's folder.

Regards,

Y



------------------------------------

**** IMPORTANT PLEASE READ ****
This group is for the discussion between users only.
This is *NOT* technical support channel.

TO GET TECHNICAL SUPPORT send an e-mail directly to 
SUPPORT {at} amibroker.com

TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)

For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/amibroker/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/amibroker/join
    (Yahoo! ID required)

<*> To change settings via email:
    amibroker-digest@xxxxxxxxxxxxxxx 
    amibroker-fullfeatured@xxxxxxxxxxxxxxx

<*> To unsubscribe from this group, send an email to:
    amibroker-unsubscribe@xxxxxxxxxxxxxxx

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/