Make SDK files open source and target .Net core 3.1 / .Net 5.0
i can't run my application on .Net Core 3.1 cause 2 bartender dll's need full .Net
Can you tell me when you plan to port to .Net 3.1 / .Net 5.0 ??
Also I would prefer open source sdk files so the community can also debug and help with development.
Thank Mischa, for the message. I also, I try to use Bartender with .Net Core 3.1 gives me the following error.
System.IO.FileNotFoundException: 'Could not load file or assembly 'Seagull.Framework, Version=188.8.131.52, Culture=neutral, PublicKeyToken=109ff779a1b4cbc7'. The system cannot find the file specified.'
when I try to do :
using (Image thumbnailImage = LabelFormatThumbnail.Create(fileName, Color.Transparent, 150, 150))
dotnet core doesnt work
you need full dot net 4.7.1 / 4.7.2 / 4.80
Guys, are there any libraries available as of now for .net core/standard support?0
Currently at this time as of BarTender 2021 R2, the BarTender .NET SDK doesn't support Microsoft .Net core 3.1 / .Net 5.0. It is currently built-on and requires full Microsoft .net framework 4.7.2 or higher.
We are aware of this customer request and already have an open feature request in our system to our development team to hopefully be added in a future release of BarTender.0
Plus 1 for .net core version.
The writing is on the wall with the release of .net 5.0 that dotnet framework is going to die. We want to stay with bartender, and a .net core version will ensure that.0
+1 for .NET 5 support.
It's been a year since this request was first opened and six months since .NET 5 was publicly released.
Do you have a tentative time frame for when BarTender .NET SDK will work with .NET 5?
It would be nice for Seagull to respond to this thread, with something like "we're working on it, hang on", "it's going to be a while", "tough luck, not going to happen", so that we can plan our roadmap accordingly.....0
Hi Timothy, thanks for posting at our community site! I've opened a ticket on your behalf with our Technical Support team! While you may not see consistent updates on feature requests through our community site, we do reach out to users who requested this information through Tech Support. I provided you with more details on this in the email.
I also am interested in this. Sign me up please.
+1 for .NET 5 support!
That would be really nice => .net Core Support.
Any news about that?0
are there any news about .NET5 / .NET6 support? Is there some expected date it will be available?
Or is it possible to use it "somehow" in .NET5 with some limitations since .NET allows to use .NET Framework assemblies from .NET Core / .NET 5 with some limitations?
Thanks for information.0
>> Is there some expected date it will be available?<<
I suggest you look @ the date of the original post and the lack of positive feedback from Seagull and draw your own conclusion. ;-)0
maybe someone needs to reverse engineer these dll's and update them to .net 6
i'm sure this will wake the dev team of bartender up in a sec0
>>i'm sure this will wake the dev team of bartender up in a sec<<
I sent several emails letting them know we were not going to renew our support contracts, that didn't wake them.
I am pretty sure that would be a violation of your license and potentially illegal.0
>> I sent several emails letting them know we were not going to renew our support contracts, that didn't wake them.<<
We are developing a new print server and it is not an option for us to develop it in a .net framework only because bartender is not supported in .NET.
If no answer are provided about .NET bartender libraries we were not going to renew our support contracts.0
I would guess it can't take up more than 30 minutes to recompile these librariies against .net standard 2.10
We have discussed this matter with our development team and I wanted to share with you what the current situation is and our immediate plans for the future:
We currently support the 4.x range for .NET. However, thanks to Microsoft's original naming convention, there seems to be somewhat of a mix-up as Framework 5.0 is yet to be released, and thus, it's not something we currently support.
There is a Core 5.0, however, this is not supported at this moment.
The moment Framework 5.0 releases, our development team will begin the recycling and updating process. That being said, I can't give you an ETA on this since this is not something we currently have in our immediate roadmap.
I'll keep you posted the moment I hear something new regarding this topic.
Until then, I would recommend upvoting the OP post and keeping this thread alive; this way we can transfer your queries to the dev. team and give you more regular updates.
Enjoy the weekend and stay safe! :)0
The mixup is at your side i'm afraid.
Maybe you guys should read up about .net core / .net 5 / .net 6 (LTS)
The old .net 5 you are waiting for is never coming.
Please update your .net 4.x to .net 6 asap.
Thank you for your comments. I'll check with the team and update you.
>>Maybe you guys should read up about .net core / .net 5 / .net 6 (LTS)<<
I *think* you just got your answer. If they don't even understand the roadmaps and differences of the frameworks, it's very clear that nothing has been done and unlikely anything will be release in the near future.0
Hi Xabier Clemente,
I am afraid that if you are not familiar with naming convention of microsoft then you are not use .NET very much and it gives us ETA for development.
Thanks for reply we will discuss with our customer how to proceed since ETA can be a couple of years.
Microsoft uses .NET Framework for classic framework 2.0, 3.5, 4.5 ... 4.8. 4.8 will be the last version of the framework.
Simultaneously .NET Core was created: 1.0, 2.0, 2.2, 3.0, 3.1 and later to avoid confusion microsoft didn't release .NET Core 4.0 but skipped it and immediatelly created .NET 5 (also removed "core" from name).
So now only .NET5, .NET6 .... will be used.0