Originally posted by andrius
View Post
so I am not alone fighting with NT support for reference problem. They try to convince me that this is expected behaviour, but I still resist 
My last email was about two days ago or so.
Funny thing happens if you have say proprietary indicator and vanilla system. Then you create your simple indicator, that doesn't require any external references. If you choose to export it Info.xml is added with reference to that proprietary indicator. This is clearly a bug.
In any case it's possible to find out which libraries some code requires and there should be added only those references. Looks like they search references in the same folder all indies lurk. What about simply copying needed indie and all referenced indies by that indie to tmpdir and only then wrap everything up in .zip? This is only one of possible ways to fix this. Of course there are more clever scenarios like http://stackoverflow.com/questions/4...l-dependencies, google "list dll dependencies".
My last email was about two days ago or so.Funny thing happens if you have say proprietary indicator and vanilla system. Then you create your simple indicator, that doesn't require any external references. If you choose to export it Info.xml is added with reference to that proprietary indicator. This is clearly a bug.
In any case it's possible to find out which libraries some code requires and there should be added only those references. Looks like they search references in the same folder all indies lurk. What about simply copying needed indie and all referenced indies by that indie to tmpdir and only then wrap everything up in .zip? This is only one of possible ways to fix this. Of course there are more clever scenarios like http://stackoverflow.com/questions/4...l-dependencies, google "list dll dependencies".
Comment