![]() ![]() ![]() In your case, the application hosting the CLR is the LabVIEW Development environment, so the file is. NET CLR to specify alternate probing paths (see ). Use a config file for the application hosting the.They have to be signed to do this so if the vendor has not signed the assemblies then this is a no-go. It can be a sub-folder in the project folder. ![]() Keep the dependencies in the project path (as you are currently doing) so that LabVIEW's default search locations are added to the probing paths.I assume when you refer to "application" you are talking about a series of VIs loaded into the Dev environment as opposed to a stand-alone executable? If so, then as far as I know you really only have a few 'easy' options ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |