无法找到或加载.NET类型

我自己也遇到过这个问题 - 似乎是因为微软不会让你信任自己的网络！
问题（据我所知）不是VEE，而是.NET，所以如果你使用.NET类，你就会坚持这个原则 - 你需要将程序安装到机器的硬盘上
它 - 在Windows 7及更高版本中变得更加困难 - 再次因为不信任的事情，你会发现从网络复制到C： Program Files（以及其他一些“神圣的”目录）中的任何地方都会欺骗你
认为它已被复制并显示在文件管理器中，但实际上Windows已经将它分发到一个“虚拟文件夹”中，只是为了浪费更多的时间，我知道这并没有真正回答你的问题，但希望它可能会节省
你有段时间。



     以下为原文

  I have come across this myself - it seems that it is because Microsoft won't allow you to trust your own network!  The problem ( as far as I can determine ) is not with VEE but with .NET and so you are stuck with that principle if you go with a .NET class - you will need to install your program onto the hard drive of the machines using it - and that's become more difficult with Windows 7 and beyond - again because of the distrust thing, you will find copying from your network to anywhere in the C:Program Files ( and quite a few other 'sacred' directories ) will fool you into thinking it has been copied and shows in the file manager but in fact Windows has secreted it into a 'virtual folder' for you, just to waste more of your time  

I know that doesn't really answer your question but hopefully it might save you some time.

我可以在本地驱动器上安装DLL文件。
使用LabVIEW，我已成功在本地驱动器上使用相同的DLL，而调用LabVIEW程序则在服务器上。
这是我无法用VEE做的事情。



     以下为原文

  It is acceptable for me to have the DLL file on the local drive. With LabVIEW, I have successfully used the same DLL on the local drive, while the calling LabVIEW program was on a server. This is something I haven't been able to do with VEE.

我不能评论LabVIEW的情况。
我曾尝试使用.NET程序（用C＃编写）访问[自制] .NET dll，我遇到了同样的问题，所以我认为这是一个.NET限制 - 抱歉，如果这是误导。
我曾经考虑过，有些情况下你可能可以从服务器运行你的VEE文件，但我没有测试过这些，例如将运行目录设置为硬盘上的目录或将DLL导入.NET框架
（而不是它只是在你的程序中使用的DLL）。
然而，从实现的角度来看，两者都不是理想的，并且从长远来看可能会比仅将整个程序VEE + DLL安装到目标机器上引起更多麻烦。



     以下为原文

  I can't comment on the LabVIEW situation.  I have tried using a .NET program ( written in C# ) accessing [home-made] .NET dlls and I had the same issue, so I assumed it was a .NET limitation - sorry if that was misleading.

I had considered that there may be situations where you might be able to run your VEE file from the server but I have not tested these, such as setting the run directory to a directory on the hard disk or importing the DLL into the .NET framework ( as opposed to it being a DLL only used in your program ).  Both however are not ideal from an implementation point of view and may cause more headaches in the longer term than just installing the whole program, VEE + DLLs, onto your target machine.

谢谢回复。
看来我必须忍受在本地驱动器上安装VEE文件。
至少主要功能。
不应该使用DLL的UserFunction应该可以在服务器上使用。
将它们放在服务器上意味着我不必为开发和测试提供单独的副本。



     以下为原文

  Thanks for the reply. It seems I have to live with having the VEE file on the local drive. At least the main function. UserFunctions that don't use the DLL should be possible to have on a server. Having them on a server means I don't have to have separate copies for development and test.