dot netdll registration

[95128007]

Hi,

I am using dot net dll in my program using constructor node, but when i run this exe program, it crashes and after 5 to 10 mins gives an error " this is not a write path". and i have to reboot the computer again.

I have tried registering the .net dll but it says " there is no such type to register"

I am confused what i have to try next. whrer i have to locate the dll in my computer, (write now its in 2 locations, one is in desktop and another is in c drive.) so that the constructor node identifies the dll.

is any one can help me .

[Charlie_P]

Good Afternoon 95128007,

Try placing your dll in the same directory as the program which is calling it.  Alternatively, you can register your dll with the GAC.

An Overview of Accessing DLLs or Shared Libraries from LabVIEW

     http://zone.ni.com/devzone/cda/tut/p/id/3009

[sandy1]

ThanThanks for the reply.

I have tried to register through regasm.exe  (also gac)it say there is no such type is to be register. I also spoken with the people hoe created thid .net dll, they said you don't need to register this dll

what can i try next?

thanks

[Charlie_P]

Good Morning sandy1,

Have you tried to put their .dll in the same directory as your VI which is calling it?

[sandy1]

Hello Charlie,

Thanks for your help, i have added dll in the same directory now its working. But now, when i run the exe, memory goes up quickly. it is using memory when we are reading sdo messages at every msec. is there any way to handle memory?

[Charlie_P]

Good Morning sandy1,

I'm glad you were able to get your program working.  Memory is a whole other issue.  Did you see this memory leak when you ran the program as VIs instead of an executable?  This question is only valid if you ran both for the same length of time and had them executing the same procedures.

[sandy1]

Hi Charlie,

We are currently running the program as executable. We din't had memory leak problem when we ran as a vi's. 

Thanks 

[Charlie_P]

Hello sandy1,

Please provide some more information on these sdo messages that you are reading.  To which "SDO" are you referring?  How are you reading these messages?

You said that memory goes up quickly.  How quickly?  To classify this, we can look at total computer memory usage before running this program.  Then, we can monitor total memory usage after 1 minute, 5 minutes, etc. (or whatever time frame makes sense for your program).  We also want to note which process is using the memory.  My assumption is that it is your .exe, but let's make sure.