Missing code generation DLL

[rkrans40]

My system is missing "labview_grpc_generator.dll" and all of the build processes I've run appear to execute correctly (note some do not like paths with spaces), without error, but do not generate this dll. All VI packages appear to be installed, gRPC appears in the LabVIEW Tools menu, but the proto compilation process fails immediately when it can't locate the code gen dll (which doesn't appear to exist anywhere on my system). Any thoughts?

[jasonmreding]

Do you have this package installed? If not, you might have to download the appropriately versioned asset from the releases page and manually install the downloaded package from VIPM.

[rkrans40]

These are my gRPC related VI packages:

[jasonmreding]

Ultimately, the dll should get installed to a path that looks something like C:\Program Files\National Instruments\LabVIEW 2025\vi.lib\gRPC\gRPC Server and Client Template [2]\gRPC Scripting Tools\Proto Parser API\Libraries\Win32. Do you see the dll present on disk at that path? If not, you might want to try uninstalling and reinstalling the gRPC Server and Client Template [2] package. I have verified when I uninstall that package, that dll is removed from disk and when I reinstall that package the dll is present again at the above location. If that still doesn't work, I'm not sure what is going on since I am also using version 1.6.1.1 of that package. I am using the following version of VIPM. I know there were some wonky bugs with some recent versions of VIPM where it didn't manage some path calculations quite right. I forget the exact details now, but I think there were preview feature settings available that would work around most of the issues assuming everything isn't fixed in the latest version. You might double check VIPM version and settings if none of your other trouble shooting uncovers anything.

[rkrans40]

I'm wondering if my PC is blocking the dll during the build/make process? The package install creates all directories except the Libraries folder and children.

[jasonmreding]

I'm wondering if my PC is blocking the dll during the build/make process?

Perhaps I misunderstood the issue. Are you trying to build the dll and vi packages locally and then install them? Or did you say "build/make" when you really meant install? Everything I referenced above is simply using the already built packages that are attached as release assets to the releases page or uploaded to the VIPM community repo. You should not need to build anything if you simply want to use what has already been released. If you are trying to build stuff locally, perhaps you can provide some more details on what you are trying to accomplish and I can provide suggestions and trouble shooting from there.

[rkrans40]

Where is this released asset that includes the VIP? I was building the package since I could not locate that package.

[jasonmreding]

Every github repo has a releases page that is linked from the repo's landing page. For each release, there are attached assets for that release. In the case of grpc-labview, there is a zip file which you can download which includes the three VIPM package files which are produced by this repo.

[rkrans40]

Awesome that was my issue. I was working with the source and the grpc-labview.zip that was the source download versus the collection of packages in the latest release. Unfortunately, these two files have the same name.