opening the DotNet assembly reference window freezes labview

[orbital56]

I am running windows XP SP2, I have Visual Studio DotNet 2003 installed I also have DotNet runtimes: v1.0.3705, v1.1.4322, v2.0.40607, and v2.0.50110 installed. Follow steps
Tools-> Advanced->DotNetAssemblyReference... now when the window opens there are 5 assemblies already referenced that point to non existant directories and assemblies. Labview then pins the CPU to 99% and freezes permenetly. This is repeatable every time. So I was wondering a couple things. 1) if labview is freaking out due to non existant directories/assemblie references where are these stored e.g. in the registry or some settings file? 2) This question has nothing to do with the problem but I was wondering when support for events is going to be implemented?

[Lycangeek]

You've run into a known problem that happens if the beta of .NET 2.0 is installed along with LabVIEW. Currently the only solution is to remove v2.0.40607 and v2.0.50110. I'm still planning on seeing if I can come up with a workaround but haven't had the chance yet.

As to events, they're in and working for the Constellation version (see my blog http://detritus.blogs.com/lycangeek/2005/04/constellation_c.html). However the one thing I'm not allowed to do is mention anything regarding release dates. So, it's coming but that's all I can say.

[-=StoneR=-]

I am getting the same problem but i have already uninstalled all Beta 2.0 products.
I had VS.NET 2005 Beta 1 installed at one time but i uninstalled it earlier along with the beta 2 .net framework.
I even tried uninstalling the 1.1 framework and reinstalling it. (Still locks)

Any help would be appreciated.

Thanks
Nick

[Lycangeek]

There is something in the GAC that LV doesn't like. I don't know how well the b2 uninstall works but that is the only thing I know that can cause the window to lock.

You can try this...Be careful about deleting anything but uninstalling should leave the following directories empty.

1. Uninstall all .NET frameworks from the Add/Remove (1.0, 1.1 and 2.0). Reboot.
2. Go to \Windows\Assembly\GAC via a command window (cmd.exe) (not windows explorer) and see if there are any subdirectories. If you have installed .NET applications, they may have installed components there. If so, you may need to uninstall and reinstall those after this sequence is complete. If that is going to be too difficult, let me know and I can walk you through a more involved process. Hopefully that won't be necessary.
- You should be able to delete the Assembly directory at this point. You should also be able to delete the c:\Windows\Microsoft.NET directory also. Again, check to see if there is anything left in there before deleting.
3. Install the 1.1 framework.
4. Try LV again.

[thfwong]

I ran into the same problem after installation of vs.net b2. The problem went away after I removed vs.net b2 and followed the instruction to "Uninstall additional components".

[Lycangeek]

Just wanted to update those interested in the .NET 2.0 support in LabVIEW. See http://detritus.blogs.com/lycangeek/2005/06/labview_and_net.html

[asche]

Brian,
Having the same problem in 7.1 discussed, I tried the ".config" file suggestion. I tried both, the "suggested" and "required" rintime specification. No luck. Is there any way to know if lv is reading the .config? I would hate to remove v2.0 to mess up other things.

[Lycangeek]

The config file option only works with the patched version of LabVIEW 7.1 or Constellation. We have a patch that we are letting people try out until .NET 2.0 is formally released and we can formally release our patch. If you are interested in trying it, please contact me at bloggingbrian@gmail.com.