.NET Issues with LabVIEW 8.5

[mikemattball]

It looks like a teaser - the link doesn't work!  Thanks for finding it - this is good news as I will be porting this week to 8.5 - maybe I can save a day with this.  Surely they are just figuring out how to get it on their site and it will be available in the next few hours...

[_Bryan]

The link is funny, but you can still get it.  I just downloaded it.

Go to the resource center and go to the 8.5 download page.  Copy the link to the exe and paste it into your browser.  Now remove the path after /windows, then you can navigate the ftp site and get to the 8.5.1 exe. 

EDIT:  I atached a screen shot of the ftp site.  The reason for using the 8.5 link is to get the password and log on in the link that will allow you to get to the ftp site.

Message Edited by _Bryan on 04-01-2008 12:42 PM

[Drazen]

I have just upgraded to 8.5.1 and I am still seeing the issue. The issue being: Multiple VIs looking into the GAC are unable to find the registered DLL in which those VIs were built on another computer. Has anyone upgraded/seen the same thing?

[mikemattball]

I found that 8.5.1. was able to automatically relink the .NET on my computer, so it seems to at least have been improved.  We are still investigating the fact that when other computers open this same code it wants to resave due to a recompile.  My computer doesn't need a resave.  I think there is still some sort of path handling issue.  My computer has .NET 3.0 on it I believe, while others only have 2.0 and 1.1.  I think there are still some issues but I'm still investigating.  This sounds like a similar problem to yours, Drazen.  I'll post if I find more info.

[Drazen]

Update:

I have successfuly resolved all the GAC assembly conflicts in the project. However 8.5.1 was not able to do it automatically. When I loaded a conflicting VI it linked its assembly dependecy  to the preloaded .NET assembly in the project. This marks the VI as being changed, so I saved the VI and repeated the process for all the conflicts.

[mikemattball]

I wonder if this is related to our issue.  We reuse (crazy, I know) the same vi in different projects.  Maybe each use case keeps trying to change the vi to point to that new project .NET instance?  I have to admit so far this 8.5 stricter linking schema is currently very painful.  Maybe in a few months I learn to appreciate it, but right now I'm trying to figure out what the problem was they were trying to solve.

[rlinaresh]

National Instruments and Labview have just disappointed me so much. I have programming with Labview for 7 yeas and have always been capable of overcoming bugs and small issues, but this is incredibly big. And the solution, install Labview 8.5.1., requires an activation. Can it be activated with the same license of 8.5? Our automatic updates program or however it's called finished at the end of last year, so I'm stuck in LV 8.5 with an enormous application that has many and many .NET assemblies (of course all of them causing warning windows to appear). Do you think it'll be solved reinstalling LV 8.5 or .NET framework?

Hope I don't have to buy any other license to fix a bug of NI!

Thanks for your help.

[KKE]

Hi all,

I'm wondering since the first post regarding this problem dates back to 11-07-2007 12:54 AM. Is there a final solution or maybe a patch available for the LV8.5 Student Edition.

I've tried the about rebuilding the VI and I can confirm that it does NOT work. It does as long the new VI is not saved, once it is reloaded from disk it displays the warning again.

Thanks in advance,

KKE

[chris.b]

Hey All,

This issue (68471 / E485CF2) was fixed in LabVIEW 8.5.1 (see the LabVIEW 8.5.x Known Issues for more information).  Because you are running the Student Edition, your school should have this version readily available.

[KKE]

In Belgium the NI LabVIEW Student Edition is a commercial product. I bought mine for a "considerable" amount of money less than a year ago ... Since i've encoutered about 3 bugs for every 3 projects that I did with LabView. That makes one bug for every project, i think i could have spend that money in a far better way.

I believe that if you buy a car the manufacturer should make sure the car runs, and not only downhill. I 'll be looking forward a active link where i can download the 8.5.1 release.

Best Regards, 

KKE