Log In
Home
09/01/2016
Offline
I looked for another answer for this but can’t find one. So I download the new “opc-core-components-redistributables-3.00.107-20171009.zip” it asks me where I would like to install it, and defaults to “C:\Program Files (x86)\OPC Foundation\Core Components 3.00” Fine that will work. So the installer doesn’t put anything in that directory. I watch it in procmon, I look at the log file… etc… The best I get is a directory of NuGetPackages. I see a discussion on here about that… being the “new” way of distributing fixing problems etc. But the file names are
“OpcComRcw.2.1.107.nupkg, OpcNetApi.2.1.107.nupkg, OpcNetApi.Com.2.1.107.nupkg, and OpcNetApi.Xml.2.1.107.nupkg” But I have 3.00.107… and extracting the NuGetPackages because no matter what I tried in VisualStudio I kept getting errors. I get the regular files and they have internal version numbers of 2.1.107.19. The Date Modified is a couple days ago Monday I believe “10/9/2017”
I know for one I am confused. Why can’t the DLL’s match the version of the release? It makes sense? Either you are releasing 2.1.107 or you are releasing 3.00.107. Or the install is majorly messed up and I am not getting the right files. I don’t have access to the “Corp Members” section so I can’t get the example ones with the .DLL’s already extracted for me… and Googling did nothing it’s like no googling to match the version Numbers I was seeing.
Please someone help me understand!
05/30/2017
Offline
Did you read the “OPC COM Core Components Readme 107.19.pdf” file that was in the ZIP?
The version number for the “Core Components” package is different from the version number for DLLs that are distributed within it.
This is pretty normal whenever an installer groups together binaries from different sources.
(each one of the COM proxy/stub DLLs has a different version number too based on the source COM specification).
Lastly, do you know what a nuget package is?
After re-reading the document it is clear that the document assumes the reader understands what nuget is and how to use it.
I can update the document but I would like to understand better where people are starting from.
09/01/2016
Offline
I didn’t look at the PDF till now. But I fail to see where it in particular talks about the version strategy or why. The best I get is the bullet item that refers to the 106 being removed because of inconsistent component id’s. Nothing that mentions DLL versions vs this release version. And while I can sorta agree with your last point “This is pretty normal…” what I see is 4 DLL’s (after I get them from the Nuget Package) I did choose to unzip and go about gathering them from that… as I get errors in Visual Studio 2012 when trying to use the nuget package files. I end up with 4 DLL’s with version 2.1.107.19.
Maybe I am missing something? Also why does the installer ask for a directory defaults to “Core Components 3.00” and puts nothing in it. Also did you look at the log file it is riddled with warnings/errors. I am just trying to help it is what it is; and obviously not too many people are bothered by it.
05/30/2017
Offline
The version numbers have been the same for nearly 10 years,
This is the first time it has come up as an issue.
If you select ‘install headers’ you should see something in the default directory.
The installer was built with VS2008 (MS used to have integrated support for MSI generation).
I would be surprised if there were not warnings in the logs.
09/01/2016
Offline
I’ve realized that after some research and looking at dates and various things. But, maybe even this topic will help some future soul that wanders the same thing. At first I thought it had to do with OPC 1.0 Data Access vs 2.0 vs 3.0…and I was wanting to try and make sure the DLL I was using had 3.0… but, as you said that’s not the case. It’s just been a learning curve that’s all.
Some of the errors are probably super common.
DEBUG: Error 2826: Control Line1 on dialog MaintenanceForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: MaintenanceForm, Line1, to the right
MSI (c) (98:2C) [11:03:02:403]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2826: Control Line2 on dialog MaintenanceForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: MaintenanceForm, Line2, to the right
MSI (c) (98:2C) [11:03:02:404]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2826: Control BannerBmp on dialog MaintenanceForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: MaintenanceForm, BannerBmp, to the right
Those of us that strive for error free, no warnings etc… often find themselves disappointed in life 
1 Guest(s)
Usage Policy