By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,742 Members | 1,570 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,742 IT Pros & Developers. It's quick & easy.

Dot Net team why isn't there a System.Financial?

P: n/a
sr
There is a System.Math class that is very helpful I couldn't imagine
any next generation framework or language without one a Math class!
What is the issue with having a System.Financial class for common
financial formulas using the .net decimal datatype recommended to be
used in financial calculations? The universal formulas I'm referring
to are used to find payments, PV, FV, rate, and etc... exactly what is
in the legacy Microsoft.VisualBasic namespace except upgraded to use
the decimal data type.

Peeps don't reply if one of your answers are amongst the mind numbing
below:
- you can do this by referencing the legacy Microsoft.VisualBasic
namespace.
- why rewrite what has already been written you can easily reference
the legacy Microsoft.VisualBasic namespace
- this is easy just write your own class wrapper that references the
legacy Microsoft.VisualBasic namespace then reference this as a dll or
cut and past the code into all your projects

Just would like to know the drawbacks of giving .NET developers writing
business applications a new .NET class called System.Financial used
only for financial calculations that could be accessed just like the
class System.Math.

Thanks!

Nov 16 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
As well, I found it odd that .NET doesn't include a Money value type
that carries an amount and a currency. Perhaps I'm looking at this in
too simple-minded a way, but I would have thought Money to be a
fundamental type that lots of people would want to use...?

Nov 16 '05 #2

P: n/a
"Bruce Wood" <br*******@canada.com> wrote:
As well, I found it odd that .NET doesn't include a
Money value type that carries an amount and a
currency.


Too specialised, in my opinion. Can you think of any other programming
language that has such a type (excluding SQL, which isn't
general-purpose)? You might just as well argue for a Temperature type
with a value and a scale.

Also, storing the currency along with the value wouldn't be very
helpful, since exchange rates are not constant and the Framework would
have no way to convert between currencies - it would just be a
glorified number/string pair anyway.

P.
Nov 16 '05 #3

P: n/a
Considering how much of the Win32 API that still hasn't made it into the
framework, it's hardly surprising that something this specialised isn't
included, or ostensibly will be in the future.

however, 2 things come to mind. Excel has tremendous support for financial
calculations and you are always free to hit that library from COM Interop.

Or, you coudl start writing one. I'd be very interested in participating in
such a project if you're interested.

cheers,

bill

--
W.G. Ryan MVP (Windows Embedded)

TiBA Solutions
www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"sr" <30**@bellsouth.net> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...
There is a System.Math class that is very helpful I couldn't imagine
any next generation framework or language without one a Math class!
What is the issue with having a System.Financial class for common
financial formulas using the .net decimal datatype recommended to be
used in financial calculations? The universal formulas I'm referring
to are used to find payments, PV, FV, rate, and etc... exactly what is
in the legacy Microsoft.VisualBasic namespace except upgraded to use
the decimal data type.

Peeps don't reply if one of your answers are amongst the mind numbing
below:
- you can do this by referencing the legacy Microsoft.VisualBasic
namespace.
- why rewrite what has already been written you can easily reference
the legacy Microsoft.VisualBasic namespace
- this is easy just write your own class wrapper that references the
legacy Microsoft.VisualBasic namespace then reference this as a dll or
cut and past the code into all your projects

Just would like to know the drawbacks of giving .NET developers writing
business applications a new .NET class called System.Financial used
only for financial calculations that could be accessed just like the
class System.Math.

Thanks!

Nov 16 '05 #4

P: n/a
You're probably right, although the Temperature thing was a cheap shot.
95% of business software needs to deal with monetary amounts. I don't
know many apps that need to know how hot it is outside.

The only benefit to storing currency along with the monetary value
would be ensuring that you didn't mistakenly try to add US$ to Yen.
That and providing some sort of starting point for application
programmers to build up a currency conversion framework. Again,
probably not enough benefit to warrant the addition. (I was just
annoyed that I had to build my own Money type.)

I agree that basic financial calculations would be an excellent
addition.

Nov 16 '05 #5

P: n/a
I may have an interest in participating in a Financial functions library as
well.

"W.G. Ryan eMVP" <Wi*********@NoSpam.gmail.com> wrote in message
news:%2****************@TK2MSFTNGP11.phx.gbl...
Considering how much of the Win32 API that still hasn't made it into the
framework, it's hardly surprising that something this specialised isn't
included, or ostensibly will be in the future.

however, 2 things come to mind. Excel has tremendous support for financial calculations and you are always free to hit that library from COM Interop.

Or, you coudl start writing one. I'd be very interested in participating in such a project if you're interested.

cheers,

bill

--
W.G. Ryan MVP (Windows Embedded)

TiBA Solutions
www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"sr" <30**@bellsouth.net> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...
There is a System.Math class that is very helpful I couldn't imagine
any next generation framework or language without one a Math class!
What is the issue with having a System.Financial class for common
financial formulas using the .net decimal datatype recommended to be
used in financial calculations? The universal formulas I'm referring
to are used to find payments, PV, FV, rate, and etc... exactly what is
in the legacy Microsoft.VisualBasic namespace except upgraded to use
the decimal data type.

Peeps don't reply if one of your answers are amongst the mind numbing
below:
- you can do this by referencing the legacy Microsoft.VisualBasic
namespace.
- why rewrite what has already been written you can easily reference
the legacy Microsoft.VisualBasic namespace
- this is easy just write your own class wrapper that references the
legacy Microsoft.VisualBasic namespace then reference this as a dll or
cut and past the code into all your projects

Just would like to know the drawbacks of giving .NET developers writing
business applications a new .NET class called System.Financial used
only for financial calculations that could be accessed just like the
class System.Math.

Thanks!


Nov 16 '05 #6

P: n/a
sr wrote:
Just would like to know the drawbacks of giving .NET developers
writing business applications a new .NET class called
System.Financial used only for financial calculations that could be
accessed just like the class System.Math.


Mainly because Financial operations are basic OS functions, so by
attempting to put them into the OS, would open MS open for a new round of
anti-trust lawsuits.

DO a Google search: There should be a third-party library available.
--
Truth,
James Curran [erstwhile-MVP]
Home: www.noveltheory.com Work: www.njtheater.com
Blog: www.honestillusion.com Day Job: www.partsearch.com
Nov 16 '05 #7

P: n/a
> Mainly because Financial operations are basic OS functions

Huh???

Tom Dacon
Dacon Software Consulting
Nov 16 '05 #8

P: n/a
..haha I read this and it makes me laugh..

You can always create a library and have it customized to your
financial pleasure..even cheat a little, like Enron did.
::C++JAVAC# vs VB6VB:::

Nov 16 '05 #9

P: n/a
"Tom Dacon" <td****@community.nospam> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

Huh???


Ooops....

That should read "Mainly because Financial operations are NOT basic OS
functions"

--
Truth,
James Curran
[erstwhile VC++ MVP]
Home: www.noveltheory.com Work: www.njtheater.com
Blog: www.honestillusion.com Day Job: www.partsearch.com
Nov 16 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.