From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
Problem with LabVIEW calling a .NET DLL. Reference problem?
01-10-2011 11:01 PM - edited 01-10-2011 11:04 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Thank you Paul.
The same DLL.
Joel has been helpful; but can you work with me?
How do we get to the solution?
best regards
Paul_M.
NI Employee (retired)
01-12-2011 04:38 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Sandeepvd,
So what we need to do is figure out what the difference is between the EXE instance of the application and the VI instance. One way we can do this is buy building a debugable assembly. What did you use to create the .NET assembly in the first place?
Take a look at the knowledgebase articles that I've linked below so that you get an idea of what I'm talking about.
http://digital.ni.com/public.nsf/allkb/6229347C7982CC81862576E30076A4AE
http://digital.ni.com/public.nsf/allkb/3087D91EEADBAF3D862571D1004AF192?OpenDocument
Once you set up the assembly and exe as debugable we will be able to see what's going on in both LabVIEW and the .NET assembly so that we can compare the EXE and VI instances.
Paul M
National Instruments | Applications Engineer | www.ni.com/support
ottomatic
Member
07-11-2013 11:14 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
any resolution on this? I am having the exact same problem?!
Kilometers
Active Participant
07-12-2013 05:05 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Ottomatic,
It's unlikely that you'll get a response from one of the previous posters on a 2 year old thread. It may be best to create a new thread, or we can talk about this here. Could you describe your system to make sure it's understood. Are you calling a DLL from labview, seeing errors in a VI, but not in an executable? If so, what are you expecting to see? What are you getting instead? What hardware are you working with? What data type are you pulling in to the front panel? Are you getting any LabVIEW or Windows errors?
Miles G.
National Instruments
Staff Applications Engineering Specialist
National Instruments
Staff Applications Engineering Specialist
Smithpohl
Member
10-17-2017 10:56 AM - edited 10-17-2017 10:57 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello,
I was able to find a solution to a very similar problem on a different program I was working on. With My Program we had a C++ DLL that we were attempting to access with a C# wrapper.
I had the same problem where the base program was unable to run correctly with the C# wrapper until it was wrapped up into an application with all of the built version of the wrapper and DLL located in the same folder as the application.
The solution I found was to move the same files I used to get the application working into the same folder as the LabVIEW project. Additionally it was beneficial to add the files into the LabVIEW project, This way when we built the application we can we can choose to always include these files upon building the application.
Sincerely,
Jacob Steltenpohl
- « Previous
-
- 1
- 2
- Next »
