Executable not working under XP, .Net FileSystemWatcher

[Olivioloyer]

Do not mind the phone number it was a bad copy/Paste,

Sorry about that

[Alhern]

Hi Olivio.

You can check where the dll is if you select "View: DLL's in memory" on the development system. You can do the same in the executable (if you allow debugging) to compare assembly versions and where the dll is.

You can allow executable debugging by following this procedure:

http://digital.ni.com/public.nsf/allkb/8DA679805915DE40862572D5007B2F70?OpenDocument

[Olivioloyer]

Hi Aldo,

I found the DLLs in memory, thoose are mscorlib and System, which where in the dependencies, I tried to add them to the always included VI in the executable but the app builder does not permit that.

I have followed this procedure, and even with a working VI....no chance to see the executing VI on the remote machine.

Thanks a lot

[Alhern]

Hi Olivioloyer.

Did you get an error message when you tried to added to the "always included" section? If you did can you paste it?

You need to add the DLL to the project so you can add it to the build specification (Add: File..., and select the dll).

I'll try to make an example and post it with the project you sent me.

[Olivioloyer]

Hi Aldo,

I found a way to make my exe work on the XP machine using this link.

http://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/configuring_clr_version/

It works but I must include a file next to my executable.

Regarding the DLL inclusion, Labview does not allow me to include it, I added it to my project, moving it from dependencies, but when I try to add it to the always included it in the executable it shows a yellow triangle that says "the selected file is not saved"

By the way, I had no chance making work the remote debug. Don't know what is preventing it from finding the runing VI on the remote computer.

Thanks a lot.