NT errors

[Baruch]

Hi,
If I make a lot of changes in a strategy and at first compilation get a lot of errors and then correct them, I get the attached error.
The solution that I found to overcome this, I rename the strategy outside of NT (in NT this doesn't work) and then the compilation goes without a problem.
I think there should be a better solution.

Baruch

[NinjaTrader_AdamP]

baruch,

Here is a forum post on this : http://www.ninjatrader.com/support/f...ad.php?t=45139

[Baruch]

What for an answer is this?
You point to a year old thread, without resolution.

[NinjaTrader_AdamP]

Baruch,

It looks like there are a couple resolutions for this at the following links.

http://www.ninjatrader.com/support/forum/showthread.php?t=12306

http://www.ninjatrader.com/support/forum/showthread.php?t=11985&highlight=serialize

People have tried repairing the DB, as well as uninstalling/reinstalling the indicator. Ill also ask development Monday about this to see if they have any known solutions.

Please also ensure all DataSeries are set to be private. I.e.

private DataSeries mydataseries;

[Baruch]

Adam,
You didn't read or understand my problem and solution.
I'll say it again: To correct this, I rename the strategy outside of NT and thats it!!!

[NinjaTrader_AdamP]

Baruch,

Serialization is the process of converting complex objects into stream of bytes for storage. Deserialization is the reverse process.

Just doing some quick research :

Only a few error conditions lead to exceptions during the deserialization process. The most common ones are:

• The name of the root element or its namespace did not match the expected name.
• An enumerated data type presented an undefined value.
• The document contained illegal XML.

My suggestions to you from before mostly deal with the first and second parts.

[Baruch]

Adam,
Can you tell me how renaming the strategy can correct any of the problems you say I may have?

[NinjaTrader_AdamP]

Baruch,

Renaming a strategy is similar to reinstalling it since it has to be recompiled. This is a solution that was noted in the links I provided. How exactly are you renaming it? Are you just renaming the .cs file itself? Inside each .cs file there is a name that must match the .cs file name itself. Without having access to your strategy itself, its difficult to pinpoint exactly what is causing this issue. If you provide it I can look closer.