BUG: [Title for your bug] about bigdecimal HOT 4 CLOSED

Have you tried, "using ExtendedNumerics;" ?

We're working on the library. If you notice any issues, please create an Issue here on GitHub.

from bigdecimal.

Yeah, including the using statement
using ExtendedNumerics;
should do the trick.

The nuget package DOES contains BigDecimal.Parse(string)

Actually, I can think of 1 thing that might be the problem. Let me ask you this: Which framework version are you using in your project? For example, is your project using .NET Framework 4.8, .NET Core 3.1, .NET Standard, .NET 5.0, .NET 6.0 or other (there are many others, this is just a few common ones)? You can find this by viewing the properties of your project file, it should be on the first page under 'Target Framework'.

Note that the latest nuget package does not reflect the latest code updates, but it sounds like this shouldn't matter for your purposes.

Sounds like the property DecimalPlaces or SignifigantDigits is what you're after.

I am working on getting a new .nuget version together that will contain most the different .net frameworks in one for the maximum compatibility. That's pretty much done so I would expect that today, but Ill leave a comment here when it is.

from bigdecimal.

Okay, the latest code has been published to a new nuget version:
https://www.nuget.org/packages/ExtendedNumerics.BigDecimal/2022.73.321

Is supports the following frameworks: .NET 6.0 .NET Core 3.1 .NET Standard 2.1 .NET Framework 4.8

from bigdecimal.

I'm going to go ahead and mark this as resolved. The method on that class IS there, the only thing I could think of that might have been happening is if your project was targeting any other version of .NET other than the .NET Framework 4.5 or lower (4.0, 3.5, etc.).

I have since released a new Nuget library version, version 2022.73.321, which covers the latest version of each of the .NET 'types': Core, Standard, Framework, and what is now known as just dotnet, I guess, that supersedes all three. Since each is backwards compatible, as far as I'm aware, this should cover you, whatever .NET version your project happened to be.

So update the nuget package to the latest version, and I be that will work for you.

Feel free to open another bug ticket if this is unresolved or you encounter new issues.

from bigdecimal.