Packages for .NET API 3.19 P6 broken?

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search

Post Reply
7 posts • Page 1 of 1
jcbaar
Posts: 25
Joined: Fri Sep 02, 2011 12:20 pm

Packages for .NET API 3.19 P6 broken?

Post by jcbaar »

It would seem that the nuget packages for WinCC OA 3.19 Patch 6 are broken. The following nuget packages are installed:

etm.trace.1.0.2.nupkg
etm.wccoa.basics.1.0.2.nupkg
ETM.WCCOA.Interop.3.19.6.nupkg
ETM.WCCOA.Interop.3.19.6.snupkg
ETM.WCCOA.Manager.3.19.6.nupkg
ETM.WCCOA.Manager.3.19.6.snupkg

However the ETM.WCCOA.Manager.3.19.6 package has a dependency on ETM.WCCOA.Basics >= 1.2.0 which causes the package restore to fail. It also fails to properly install on a new project because of this missing dependency.

Does anyone else have this issue?

gschijndel
Posts: 330
Joined: Tue Jan 15, 2019 3:12 pm

Re: Packages for .NET API 3.19 P6 broken?

Post by gschijndel »

We have noticed this problem already with P005 and got the 1.2.0 version packages on the day of the P006 release.

jcbaar
Posts: 25
Joined: Fri Sep 02, 2011 12:20 pm

Re: Packages for .NET API 3.19 P6 broken?

Post by jcbaar »

So does this mean that the packages will be included in the next patch?

gschijndel
Posts: 330
Joined: Tue Jan 15, 2019 3:12 pm

Re: Packages for .NET API 3.19 P6 broken?

Post by gschijndel »

I assume so. Apparently it is recommended to use just Logging instead of ETM.Trace.

Code: Select all

using ETM.WCCOA.Manager.Logging;
...
// configure logging
builder.ConfigureLogging(loggingBuilder => {
  // add OA Logging Provider
  loggingBuilder.AddOaLogFile();
  // remove Console Logging Provider
  loggingBuilder.RemoveConsole();
});

User avatar
hpuchegger
Posts: 38
Joined: Fri Oct 08, 2021 10:38 am

Re: Packages for .NET API 3.19 P6 broken?

Post by hpuchegger »

Hello,

the correct packages will be available with the next WinCC OA version 3.19 P007.
However, if you need the correct files in the meantime, please open a service request so that we can provide you with the data promptly.

Br, Herbert

jcbaar
Posts: 25
Joined: Fri Sep 02, 2011 12:20 pm

Re: Packages for .NET API 3.19 P6 broken?

Post by jcbaar »

@gschijndel
The out-of-the box .NET logging was one on the reasons I was trying to upgrade. I have currently a .NET logging provider based on ETM.Trace but wanted to use the logging provided in the new packages. I will wait for the correct packages to be released.

@ hpuchegger

I can wait for P007. No problem.

Thanks for the information.

jcbaar
Posts: 25
Joined: Fri Sep 02, 2011 12:20 pm

Re: Packages for .NET API 3.19 P6 broken?

Post by jcbaar »

I'm afraid the packages in 3.19 P9 are broken again. The ETM.WCCOA.Manager.3.19.9 package depends on ETM.WCCOA.Basics >= 1.3.0 but version 1.2.3 is installed with the patch. This is becoming a serious issue since managers compiled against the older packages do no longer work properly when P8 or P9 is installed :(

Sample error of a 3.19 P8 compiled manager running on a 3.19 P9 system:

WCCOAM_Archie(5), 2024.02.15 09:17:23.468, IMPL, SEVERE, 0, , WCCOAM_Archie ERROR: Processing EAD(Wait) failed. - One or more errors occurred. (Multiple errors during add of DPs (Unable to find an entry point named 'CSharp_ETMfWCCOAfInternal_DynVar_Append___' in DLL 'libCsCoreBridgeV319'.) (Unable to find an entry point named '?' in DLL 'libCsCoreBridgeV319'.))
Multiple errors during add of DPs (Unable to find an entry point named 'CSharp_ETMfWCCOAfInternal_DynVar_Append___' in DLL 'libCsCoreBridgeV319'.) (Unable to find an entry point named '?' in DLL 'libCsCoreBridgeV319'.)
Unable to find an entry point named 'CSharp_ETMfWCCOAfInternal_DynVar_Append___' in DLL 'libCsCoreBridgeV319'.

Post Reply
7 posts • Page 1 of 1