dymosoftware / DCD-SDK-Sample

DYMO Connect SDK Samples
Other
60 stars 27 forks source link

WPF dotnet Core 3.1 - Could not load DYMO.CrossPlatform.Common #16

Open avazon opened 4 years ago

avazon commented 4 years ago

I would like to use the SDK from dontet core 3.1 WPF application. I downloaded the sample for dotnet 4.x and it works. But when I create a dotnet core 3.1 project I get the error message:

Could not load file or assembly 'DYMO.CrossPlatform.Common, Version=1.3.1.160, Culture=neutral, PublicKeyToken=null'. File not found.

The file exists and information of file is 1.3.1.160

vmark99 commented 4 years ago

Facing the same issue. Can we get this to work with .NET Core?

dymosoftware commented 3 years ago

Hi @avazon & @vmark99, we are working on it. Once a beta version is ready we'll let you know.

Jhultink commented 3 years ago

Also looking to use this with .NET Core 3.1

AndyHale commented 3 years ago

Would be great for .NET 5 too :)

mtbayley commented 3 years ago

Please! .Net5!

theOzzieRat commented 3 years ago

Same issues here. Trying to use .NET 5. @dymosoftware any news on an update? It's been almost 4 months since you said you where working on it!!

ghost commented 3 years ago

Yes - please update for .NET 5.0. Trying to write a Blazor app and this would be much needed. As of now, trying to use the JS framework but it doesn't work with the JSInterop. Has anyone got the dymo.connect.framework.js to work from a web in Blazor?

DaveSlinn commented 3 years ago

+1 For .NET 5 support.

theOzzieRat commented 3 years ago

@dymosoftware an update would be nice.

DaveSlinn commented 3 years ago

@dymosoftware - this is a real blocker for us. The majority of our code is .NET 5. The only code still running on 4.7 is the stuff to send labels to the printers. Any thought to open sourcing the code? Perhaps the community could assist with migration. After all, the software isn't the commercial product - the printer and the labels are.

DaveSlinn commented 3 years ago

With the pending release of Visual Studio 2022 - only .NET 6 will be supported - which means .Net Framework 4.8 or earlier will not be supported at all, which would prevent us from moving to it. It's been 8 months since the comment above stating they were working on it and a beta would be available. How can we move this along? Let us help @dymosoftware!

AndyHale commented 3 years ago

Also happy to help with this @dymosoftware. We're in a similar position where Dymo prints will shortly be our last bit of .Net Framework code. Happy to contribute.

PerryCodes commented 2 years ago

It's not promising when a company doesn't respond for over a year...

Pelice commented 2 years ago

news for a dotnet core 5/6 sdk?

bertenvdb commented 2 years ago

Also waiting for a .NET 6 compatible SDK...

eljayg commented 2 years ago

From #51:

DymoSDK nuget is currently targeting netstandard2.0 as of today. It will provide multi targeting for net5, net6 in future release. We don't have timeline for the project yet.

Anyone care to share what they're doing in the mean time until there's a fix? Running on .NET 4.7 or 4.8 until then?

Makin-Things commented 2 years ago

@dymosoftware I have given up on Dymo and replaced all my label printers with an alternate brand. I will never purchase another product from Dymo or the Rubbermaid group since the level of support is non-existent. They promised a beta well over a year and a half ago to target a newer .net, that is now also unsupported software. So they need to start again (if they had actually started in the first place).

Pelice commented 2 years ago

Anyone care to share what they're doing in the mean time until there's a fix? Running on .NET 4.7 or 4.8 until then?

I build a dedicated small app just for printing in .net 4.8 . I haven't found other ways..

mtbayley commented 1 year ago

Here we are at .NET 7 and still no support outside of .NET Framework.

JLOrdaz commented 1 year ago

I have the same issue. Not working. The error is: System.IO.FileNotFoundException: Could not load file or assembly 'DYMO.CrossPlatform.Common, Version=1.4.3.37, Culture=neutral, PublicKeyToken=null'.

cmwales commented 1 year ago

Its been three years. I doubt they are going to fix it.

gkawin commented 9 months ago

I gave up on creating a Printer Web API for the internal network.

asifiqbalpatel commented 6 months ago

Is there any update on this bug, I am still facing it