Fixed bug: DirectoryConfigMap property should be used instead of DictionaryConfigMap

[lbenus]

Hi guys,

I found a nasty bug in EMA C#.
#300

This was related to our scenario when we programmatically added some custom directory/service configuration. But it's not recognized so we can't publish to TREP via NI Provider.

Could you please take a look and apply?

[V-Anyakin]

@lbenus Thank you for raising this issue and the information provided. We created an internal Jira to investigate it and to apply the provided solution.

In the meantime, let me suggest you to use a workaround, if needed: encode configuration for the Dictionary group like it is done in the example 421_MP_ProgrammaticCfg so that the condition in question is fulfilled and the corresponding Directory configuration data is copied.

[lubomir-benus]

I am already doing something similar in the code. So not sure, why the condition isn't evaluated as true. I didn't debug yet.

            configMap.AddKeyAscii("DictionaryGroup", MapAction.ADD, dictionaryGroupElementList
                .AddMap("DictionaryList", dictionaryListMap
                    .AddKeyAscii(dictionaryName, MapAction.ADD, dictionaryNameElementList
                        .AddEnum("DictionaryType", DictionaryTypeEnum.FILE)  // Default 1. Options: FileDictionary (0), ChannelDictionary (1)
                        .AddAscii("RdmFieldDictionaryFileName", fieldsPath)  // Sets the location of the RdmFieldDictionary
                        .AddAscii("EnumTypeDefFileName", enumsPath)          // Sets the location of the EnumTypeDef file
                        .Complete())
                    .Complete())
                .Complete()); 

[lubomir-benus]

Hi guys, any news regarding the above? Could you please release a hotfix of the nuget package?

Regards

[lubomir-benus]

Hi guys, any news regarding the above?

[V-Anyakin]

@lubomir-benus we are very grateful for your contribution to discovering and fixing this issue. Could you please check your inbox, after the Contributor agreement is signed we will be able to merge the pull request. Meanwhile, a workaround or a patched library is the way to go. Thanks!

[lbenus]

The agreement was signed.

Workaround doesn't work for me, I would prefer to merge the FIX and release a new nuget package.

Thanks.