Is C# .NET used in Finance or C# is still too new to be adopted in Finance?

C++ is used by quantsJava and C# are used by IT folkand some people do a lot of Excel VBA as well

there are quants using C# and JAVA as well.

When to use C++ and when to use C#? Are quants free to choose their favourite language? I have been using C#, I would think it as a setback to have to use C++ again.

whenever you work alone, you freely decide what to do and which language to use, but if you´re a team player, you have to abide to what´s already implemented.

I'd stay away from any Microsoft created entity. My advice is to stick with generally accepted standards such as C++ / Java to maintain portability and platform independence. You don't want your libraries of C# code to go to waste once your employer decides to switch platform on you. You'll be hating life.

no one makes a financial program from A to Z for oneself. many people use a finance-related library.In selecting your programming language, you should take into account available finance-related libraries.c++ is supported by many finance-related libraries.that's reason to recommend c++ than c#.regards,sjoo

Are quants free to choose their favourite language? Sometimes, but generally they get told to use what everyone else is using, and most commonly that is C++ or VB.I have been using C#, I would think it as a setback to have to use C++ again.Tough.We see very many more quant jobs in C++ than C#You may think C# better, won't get you through an interview though.chyang has got it so wrong...I'd stay away from any Microsoft created entity. Cars are bad things as well, all that pollution. Don't use cars.No one here has better credentials for abusing Microsoft than I. but the real world has a lot of MS in it. They have the best IDE for development, and the latest drop of C++ is very close to standard.I've used Eclipse. Will be good, one day, I estimate 2 years.My advice is to stick with generally accepted standards such as C++ / Java to maintain portability and platform independence.And you read this where ?I've done porting of C++ code between Unixes, and trust me it ain't always trivial.I've run projects with Java in them. You have no idea of the pain we've had with the fact that there are god alone knows how many different, incompatable JVMs out there.In any case most quant code is thrown away long before a platform move. Changes in platform are very rare events. The idea of spending any effort whatsoever on portability is laughable in 90% of cases.In short don't waste time on something you will probably never need.You don't want your libraries of C# code to go to waste once your employer decides to switch platform on you. If someone is C# now, it's very hard to see them changing in the next 5 years.Do you care that far ?Java is a valid solution to a subset of quant problems, so is C#.If they get the job done use them.If some junior programmer lite told me that he wouldn't use some C++ feature to get the job done because it wasn't portable, he'd be re-educated rather directly.You're not paid to write code. You're paid to calculate, move data around and draw pretty pictures.You'll be hating life.

QuoteOriginally posted by: MBAFinanceIs C# .NET used in Finance or C# is still too new to be adopted in Finance?The answer to both questions is YES.I know one quant who does all his n-factor PDE/FDM modelling in C#, having moved from C++. He has never looked back since.C++ is a langugae and great for number crunching. Unfortunately, it take years to learn properly and many books tend not to tackle the REAL fundamentals to help you become a skilled craftsaman. Question: how many people who develop in C++ still do not know about the difference between stack and heap? Bit like a 2nd year maths guy not knowing how to manipulate complex numbers.We need a more structured approach, and a bit less of the tricks.Some traders I have spoken to prefers C#; C++ is too arcane for them.In generall, the future is just around the corner, as always.There are several future scenarios, one of which is combination of C# and C++ in my opinion.

QuoteOriginally posted by: MBAFinanceIs C# .NET used in Finance or C# is still too new to be adopted in Finance?Funny that no one in this thread talks about programmere productivity (quantity and quality of code)!! When you build a house what's the first thing you think about?C# versus C++? include I/O stuff and C# programmer is 4 (FOUR) times as productive. Have seen this now a few times.

Funny that no one in this thread talks about programmere productivity (quantity and quality of code)!! When you build a house what's the first thing you think about?Sad to say, I fear your metaphor works against good engineering.When we had a large extension built the local arts graduates on the council made use "compatable" ghastly yellow bricks, and old tiles, rather than efficient new ones.Buildings have to be "in keeping" with others. I live in a nice street, but one with no architectural merit of any kind, why we should have to make part of our house look like the yellow rabbit hutcheson the other side quite escapes me.The City of London is plagued by other graduates who enforce the maintenance of badly built 1950s emulations of mediocre 1900s architecture. Frequently we see the front of a building left standingwhilst a new inside is built, at great cost, but poor structure.This is a clear parallel with the weight of history that stops us making clean greenfield engineering decisions about software.It's worse even than that.If you build a house, you don't have to worry about whether new versions of the bricks will be developed, or whether the manufacturers will make them compatable with the old ones.Many building materials in Britain are of imperial measure, but in metric units, thus you buy 2 inch thick wood by the metre length.In you invest your time learning C#, or commit your group to develop a project in it, you have to worry about it's future.Java has been the victim of mendacious acts by both Sun and Microsoft.C++ isn't as standardised as I would like, but enough for 99% of what I do.Who in our game really cares about portability ?I care a lot more about the productivity that Cuchulainn cites, and reliability with performance normally being third in that list. Portability to me doesn't really get to the top 10.

C# will give you a valid call stack most of the times which is for me the big plus compared to c/c++. As stated before forget about reuse of code unless the # lines is large and this is pure IT work. The MS IDE is a must. I am currently looking into moving part of my architecture from C++ to C# ( GUIs ).there is no bad or good language, actually there are some, but between c/C++/java/C# it does not make much of a difference. C# is a good language for beginners, it's "safer" and therefore will allow you to track down errors more quickly. Quality is the key, CMMi, Agile XP... my favorites! If I can give you one advice : Build test system first, chosing C# vs C++ is a non event.

Quality is realised both at design time and implementation time. Producing good design blueprints is a guarantee for success, the language choice is almost irrelevant.My team communicates at blueprint level and gives us a vocabulary that is richer than the nitty details of C++, C#