Why vi dll creates ini file on its own?

[LukaszG]

Hello,

I have built my LabVIEW project as shared library (dll). 

My system looks like this: main exe file loads dll, and this dll loads VI dll.

With LabVIEW 2011 it was ok, but when I switched to 2013 my VI dll started to write into main exe ini file.

When dll is loaded those lines appears in main exe ini file:

[LVRT]
RTTarget.ApplicationPath=C:\Users\user\Documents\LabVIEW Data\Remote Development\startup.rtexe
RTTarget.VIPath=C:\Users\user\Documents\LabVIEW Data\Remote Development

Does someone know what causes this and how to turn it off?

[JunonTenory]

Hello Lukasz!

I tried to reproduce the issue, what you mentioned, but my .ini file was the same (untouched). So i cannot imagine how could such problem occure. If you send me the VI and the dll-s what you made (or a similar one wich has the same problem), maybe i can say more about this and continue my investigation about it. As i see these dll-s are on a real time target. Could you tell me the exact name of these devices? So i can reproduce this problem better.

[mcduff]

I got the same thing when I built an exe. I have a custom INI file, it has the following entries:

[Oscilloscope 2013]
server.app.propertiesEnabled=True
server.tcp.serviceName="My Computer/VI Server"
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=False
DebugServerWaitOnLaunch=True
FPFont="Segoe UI" 15
appFont="Segoe UI" 15
dialogFont="Segoe UI" 15
systemFont="Segoe UI" 15
BDFont="Segoe UI" 15

The only dll it calls is lvanlys.dll. After running the EXE the following are appending to the INI file

RTTarget.ApplicationPath=C:\Users\XXX\Documents\LabVIEW Data\Remote Development\startup.rtexe
RTTarget.VIPath=C:\Users\XXX\Documents\LabVIEW Data\Remote Development

Regards,

mcduff

[JunonTenory]

OK!

I managed to reproduce the problem, so i was able to look after it abit deeper.

It was an existing bug in the LabVIEW 2013, but it was disovered in January. Our R&D to repaired it in April, and in the LabVIEW 2014 it was corrected, if you use the latest version it will not occure.