could not get assemblies from global assembly cache

[cosmo]

Trying to use 'Create .NET controller...' in CVI 8 for first time.  As soon as I click the menu item, I get two errors:

-could not get assemblies from Global Assembly Cache

-Caption __Text: <blank>

Does this mean that the CVI 8 installer failed to install something properly, or do I need to install something from Microshaft on my own?  I have .NET frameworks 1.0, 1.1, and 2.0.

Orlan

[Mohan]

This was working with .NET Framework version 2.0 beta2. Looks like Microsoft must have changed something in the version of .NET 2.0 released after CVI 8.0 and this is causing the error. By default, Windows loads the latest .NET framework for any application, but one can configure a specific version for an application using a config file. Please create a text file called cvi.exe.config with the following contents and place it in the same folder as cvi.exe:

<configuration>
   <startup>
      <supportedRuntime version="v1.1.4322"/>
   </startup>
</configuration>

After saving the file, restart CVI and see if this works.

[cosmo]

Hello again Mohan,

  The config file worked.  Atleast the .NET controller wizard appears now.  I closed CVI and restarted it, but the first time that the wizard opened it took 10 seconds and then popped 'under'.  I had to ALT-TAB to get it to reappear.  From the second time forward, it opens quickly.

Orlan

[Mohan]

Using the config file will prevent you from generating wrappers for .NET assemblies that were built to target .NET 2.0. I found another work around. Basically, the problem is that in .NET 2.0 Microsoft removed a component (mscorcfg) that was being installed in .NET 1.x - Microsoft now installs this component in .NET 2.0 Framework SDK. If you install the framework SDK then you do not need to use the config file. This is available on Microsoft website but takes some time to download and install. I think this is a better workaround as this lets you generate wrappers for 2.0 assemblies too.

The UI does take some time to launch at first run but should be faster after that. Even restarting CVI and relaunching the tool should be faster after the first time as Microsoft caches this information after the first time.

Best regards

[cosmo]

Actually the second idea works even better because, as you point out, you don't loose .NET 2 as you do with the config file approach.  For those without cable or dsl, it might be the only practical fix.  It took just as long to install it as it did to download it (over cable).  Haven't actually tried to use it yet, but atleast the wizard shows all of the version 2 assemblies.

Orlan

Message Edited by cosmo on 12-07-2005 04:13 PM