Transaction Scope Compiler Warning

Kinetic ERP
,
21

@SteveFossey it says 8.0.11

22

idk why not. It works on server, so it is not server problem.
Also 6x was long ago, currently it is 8x.

23

Update: I uninstalled every version of .NET runtime and SDK, then I installed the version our cloud server has installed the 8.0.11 runtime and the 8.0.404 SDK. Now in addition to the warning I was getting I am getting the following message as a syntax error.

Code: CS0012
Message: The type ‘TransactionScope’ is defined in an assembly that is not referenced. You must add a reference to assembly ‘System.Transactions.Local, Version=8.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51’.

It doesn’t prevent me from saving the BPM and enabling it, it’s just very annoying. Has anyone got this warning to go away?

Just for context, if I use the following code I get the syntax error:

using (var txScope = IceDataContext.CreateDefaultTransactionScope()) {
        //Any Business Object Update Code Here
        txScope.Complete();
}

If I use the following code (for the sake of testing) I don’t get the syntax error:

using (TransactionScope txScope = new TransactionScope()) {
        //Any Business Object Update Code Here
        txScope.Complete();
}

But either way I still get the compiler warning message.

24

I’m seeing this too we’re SaaS so have no control of the server.

image

25

Only supported on Windows… That’s really funny

1 Like
26

I’m surprised no one else has the answer on this yet… This is due to the move of SaaS servers to Linux. Instead, use (when it becomes an error):

using (var trx = TransactionScopeFactory.CreateDefault())

4 Likes
27

@Epic_Santiago

28

Hi everyone,
We have introduced some new warnings to verify that code is cross-platform. This is in preparation to moving to Linux for 2025.1. The warning was backported to 2024.2 to help identify such code prior to the upgrade. You can find examples of code that is not cross-platform (like the Windows registry) here:

TransactionScope.Close() however is a false positive as this method is indeed portable. This has already been fixed and the warning should go away in the next build.

Not directly relevant to this question but another good resource to reworking absolute paths in custom code (since C:\Folder won’t work on Linux where it would be something like /Folder) is this:

4 Likes
29

Hold on that’s not a certified platform, how can that be?

1 Like
30

So the platform certification is going to changed for 2025.1? is it going to be likely that on-prem will be able to benefit from the use of containers.

And if going to Linux, is this for the both the app servers and SQL or just the app servers?

and if SQL Linux are they going to remove the limitation of named pipes for the install of EDD?

sooooo many questions :slight_smile:

1 Like
31

To my understanding it is cloud only at least initially. On prem will still be windows.

Also for cloud it is for the Kinetic App AKS instances only. The likes of EDD will remain in windows for now.

Also the move to Linux app servers is not at the same time as 25.1 release. 25.1 is the first step to enabling it to happen. The rest will happen later on in the year. :safe_harbor:

2 Likes
32

Of course… why would we (on-prem) ever get to benefit from huge potential cost savings of Linux.

I knew they wouldn’t do this. I’m sure, as you’ve already hinted, they’ll provide the same nonsense excuse as AI. Billion+ in ARR but deploying software is too hard.

1 Like
33

So, “on prem” is a little misleading here. @josecgomez runs in Azure but says he’s on prem. What I think we mean by “on-prem” is not Epicor SaaS.

One could always spin up their own AKS instance in Azure using Linux. :person_shrugging:

If one REALLY wants to be on-prem, one can run AKS on a local machine using Arc enabled Kubernetes Service:

1 Like
34

We run “on-prem” Azure, too. Still doesn’t mean there’s any path for me to get Kinetic installed on a linux app server or even container. You could likely follow the documentation for hosting ASP.NET Core on Linux, but this relies on everything in Kinetic’s server deployment being platform agnostic. Anything that isn’t will blow up.

1 Like
35

Pretty sure someone here mentioned that this would be available for any AKS users - not that AKS is easy to manage, but maybe something changed in the meantime. :person_shrugging:

2 Likes
36

If released as a container, even better. Ultimately, my problem is only if they decide to keep it to themselves and then use it as a selling point for why cloud is better. Like AI.

Just hoping it makes it to the customers, complex or not. For the orgs who can’t handle it, Epicor and their partners would benefit from the professional services required.

3 Likes
37

Thank you @Epic_Santiago I’ll keep my eyes out for any warning not referencing TransactionScope.

1 Like
38

@Epic_Santiago I got one for you warning CA1416: This call site is reachable on all platforms. 'MailPriority.High' is only supported on: 'Windows'.

2 Likes
39

I just checked and with the fix, MailPriority.High doesn’t give a warning. Add this one to the list of ones to ignore. Sorry for the hassle.

3 Likes
40

What about the use of System.Xml namespace? I use it to extract information from BpDirective table, Body field which is stored in XML.

warning CA1416: This call site is reachable on all platforms. 'XmlDocument.LoadXml(string)' is only supported on: 'Windows'
1 Like