Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved .NET CORE Support

  1. Misc
0
Votes
Undo
  1. John Niespodzianski
    John Niespodzianski
  2. Beta Testing
  3. Tuesday, 18 February 2020 20:41 PM UTC

We've tested the new C# Class Importer with a .NET Core 2.2 DLL and it works perfectly. 

We also tried with a 3.1 DLL and it gives an error and doesn't let you get any further. 

My understanding is that 2.2 will be going out of support soon; are there plans to upgrade the .NET Core features to 3.x in PB 2019 R2?  Or is that later on the roadmap?

We're definitely excited about this new feature as it will allow us to more seamlessly communicate between the .NET and PB worlds without the need to stand up an API.  There are also 3.x features we'd like to exploit, so I just wanted to get a pulse for when that support will be in place.

Thanks!

John

 

 

 

Is it possible to know the color applied by a them...
Dynamically update expression in DwCompute
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 18 February 2020 21:13 PM UTC
  2. Beta Testing
  3. # 1

Hi John;

 AFAIK at the moment ... Net Core 3.x will be supported in PB 2019 R3.

Regards .... Chris

Comment
John Niespodzianski
  1. John Niespodzianski
  2. Tuesday, 18 February 2020 21:20 PM UTC
Thanks Chris! Good to know that it's tentatively scheduled in a PB 2019 release; we can certainly wait until R3. We can continue prototyping and testing solutions with 2.2 until then.
  1. Helpful
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Tuesday, 18 February 2020 23:07 PM UTC
  2. Beta Testing
  3. # 2

Hi John,

Like you I really, really like this new interop. As long as your API uses C# compatible data types it should handle .NET assemblies independent of language. That's pretty cool. For one I'd like to interop with F# or other functional language -- and with machine learning.

I told Appeon as feedback on current beta that I would use SnapDevelop for more .NET work if it supported C# 8.0 (especially nullable reference types) and .NET Core 3.1 = Latest long-term support (LTS) version. Prior LTS version is actually .NET 2.1 - which is probably part of reason why SnapDevelop has apreference for .NET Core 2.1.

.NET Core 3.1 released just two months ago so it was kind of too late to make it into 2019 R2. I'm happy that it is tentatively in plan for R3 :-)

And due to LTS I expect support for .NET Core 3.1; not 3.0.

/Michael

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 18 February 2020 23:53 PM UTC
Yes, we would support version 3.1 because that is LTS version.
  1. Helpful
There are no comments made yet.
Julie Jiang @Appeon
Julie Jiang @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 19 February 2020 02:14 AM UTC
  2. Beta Testing
  3. # 3

Hi John/Michael/Chris, 

The C# Class Importer in this beta version shall already support .NET Core 3.1 DLLs. If you have issues importing such DLLs, please open a ticket and provide a reproduction test case at https://www.appeon.com/standardsupport/newbug, and our support team will help you.

Best regards, Julie

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 19 February 2020 03:27 AM UTC
Hi Michael, Yes in R3 when SnapDevelop supports .NET Core 3.1 it will also support C# 8.0.
  1. Helpful
John Niespodzianski
  1. John Niespodzianski
  2. Friday, 21 February 2020 14:25 PM UTC
Julie, I tested this with 2019 R2 Beta Build #2279.



Is there a later beta build available that I should test with? Thanks!
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 21 February 2020 15:39 PM UTC
Yes, 2279 build is correct beta version. Please open a support ticket and attach the DLL that fails to import.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.