Update the SDK Already
First, some required reading:
https://www.interviewbit.com/blog/net-core-vs-net-framework/
Long story short, .NET Framework is a product line that is no longer receiving major updates and any remaining support is relegated to maintenance. .NET 6.0 is the most recent version of the entire .NET product line (as of writing, .NET 7.0 is in preview phase), and is able to operate as far back as .NET Standard and .NET Core with some (limited) compatibility with the even older .NET Framework. .NET Standard/Core/5.0/6.0 offer many newer features, improvements, and overall blow .NET Framework out of the water. I feel it would be beneficial to Bartender's long-term viability to create a .NET Standard-compatible version of the SDK, as that will allow much more modern applications to leverage Bartender's other useful features without requiring a dated, and soon to be unsecure, product to do so.
As for the REST API, it is nice when that is a viable option, but it may not be for a great many applications and certainly isn't for my company's. My readings on the various features also show that the .NET SDK has more to offer due to having a deeper, direct connection with Bartender.
-
I have been frustrated by this for the last several years, at least a .net standard SDK that can be used by both .net framework and .net6 , but something needs to change if we're going to continue using BarTender in our products.
0 -
I HAVE been able to work around it, but the way I had to was kind of absurd. I basically wrote a whole second WCF application service that can take data from my .NET 6 web-app and use the .NET Framework SDK to create print jobs.
0
Iniciar sesión para dejar un comentario.
Comentarios
2 comentarios