Maintaining versions of strategies between PC's

[naxo79]

Hi

I do development and backtesting on one PC and have the actual strategies running in production on another PC.

What is the best way to keep strategies synchronized and up-to-date between these PC's.

When exporting and importing many strategies at once I often run into the "import failed. May contain duplicate methods..." http://img146.imageshack.us/img146/9...1061311072.png
or some other error.

So export and import, besides being a hassle doesnt really work.
Opening the strategies in strategy editor and copy-pasting the updated portions of the code and then compiling is a hassle and is error prone.

1. Can one just copy or keep the .cs files in sync?
2. How does one do if one keeps the code in CVS?

Thanks for any hints on this. I am sure many face the same issues.

[NinjaTrader_Bertrand]

naxo79, best suggestion would then be finding out first which methods are really duplicate and therefore cause an issue - if you transfer strategies / codes are you importing / exporting the source code or assemblies?

[naxo79]

Hi,

I guess all are duplicate since of course older versions of the same strategy exist on the PC trying the import.

I have been exporting them as source coude.

[NinjaTrader_Bertrand]

No, they would be overwritten normally if you choose to do so, it would prompt you - you would need to find out what duplicate methods are in conflict, I suspect there's part of them contained in an assembly (not source) so there would be really a conflict present here.

[naxo79]

Sorry, I dont understand.
How can they be contained in an assembly if I export them as source?

Some of the strategies use indicators from NT can these be the ones being in assembly?

[NinjaTrader_Bertrand]

You would need to check the system were you have the issues carefully and debug why you would receive the duplicate methods warning...this is normally seen when assemblies (compiled versions) are at play in the installed NT, so this was a guess from me here to help you troubleshoot the issue.

[naxo79]

Got it sorted by reviewing the tracefile. tnx.

Any guides on using a CVS for code and version maintenance?

[NinjaTrader_Bertrand]

Glad to hear that naxo, what's a CVS?

I would include your own custom version info in the code commentary, or copy to a new code for each significant revision, adds the benefit to cross run / check different builds of your script.