Skip to Content
0

PB.NET 12.6 Reference 4.5 assemblies

Jul 11, 2017 at 10:26 AM

86

avatar image

Hello,

I am confused regarding all the data in the help files of PB.NET 12.6

Is it possible to reference 4.5 assemblies in a WPF target or is it not? If it is not, what is the difference between this and version 12.5.2 ?

Thank you

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

avatar image
Former Member Jul 11, 2017 at 04:10 PM
0

Version 12.6 of PB.Net is the final release and SAP support of 12.6 ends June 30 2018. Don't bother trying to learn it. Appeon is not supporting PB.Net because few companies actually used it.

Share
10 |10000 characters needed characters left characters exceeded
Arcady Abramov Jul 11, 2017 at 05:08 PM
0

Hello, Roland

I already have a working application in PB.NET 12.5.2

It works fine except for the problem with v4.0 of the .NET framework. We need to integrate 2 large projects, one written in pure C# and the other written in PB Native and PB.NET. We also need support for TLS1.2 and async calls.

These projects have a lot of shared functionality and we need them to share code as well. The only way to do it seamlessly is to share the .NET assemblies, which are written in C# in v4.5.

I was hoping that I will be able to do it with PB2017, but without being able to integrate .NET assemblies into the PB code it is not possible,

So, now my only hope is to migrate the PB.NET console app into version 12.6 integrate the .NET assemblies in it.

But the information in the help and online is extremely confusing.

All I need to know is this: if I simply migrate the WPF app from 12.5.2 to 12.6. Will I be able to migrate the .NET assemblies to 4.5 and continue to use them? Surely someone has done it over the years. I did not think the question would be so difficult to answer.

If it is not possible, then we will have to abandon PB in the course of the next 2 years and migrate most of our interfacing application to pure C#. I would really like to avoid that!

Share
10 |10000 characters needed characters left characters exceeded
Arcady Abramov Jul 12, 2017 at 01:40 PM
0

And now we have a new beast - .NET Core, which is only possible to access from .NET 4.5

So, remaining with 4.0 is not an option. And using COM wrappers is not an option.

So, PB.NET is all that remains. If .NET 4.5 can be used with PB.NET WPF app - great, we got at least another year, may be 2. Hopefully, the next version of PB from Appeon will allow using .NET assemblies as we use NVOs, at least through some sort of an internal proxy.

Share
10 |10000 characters needed characters left characters exceeded