Using C# in Excel
- Thread starter kean
- Start date
- Joined
- 9/10/06
- Messages
- 71
- Points
- 16
There is a thread out there that already discusses a little of it:
Integrate C++ program into VBA
Are you asking because this is something you have to do? Also, do you want to use C# as a replacement for VBA macros, or do you want to call the Excel object model from a C# program? Those are totally different issues.
Integrate C++ program into VBA
Are you asking because this is something you have to do? Also, do you want to use C# as a replacement for VBA macros, or do you want to call the Excel object model from a C# program? Those are totally different issues.
C#
Joe, thanks. What I mean is integrated C# and Excel (not C++, it is C#).
Secondly, I want to know how call C# object model from Excel and vice versa.
Joe, thanks. What I mean is integrated C# and Excel (not C++, it is C#).
Secondly, I want to know how call C# object model from Excel and vice versa.
..
More precise.."Calling the IMSL C# Numerical Library from Microsoft Excel"
Please let me know if you have any recommendation..or articles will do.
More precise.."Calling the IMSL C# Numerical Library from Microsoft Excel"
Please let me know if you have any recommendation..or articles will do.
- Joined
- 9/10/06
- Messages
- 71
- Points
- 16
Unfortunately, C# is not "integrated" into office, something you no doubt found out already. I believe the next version of office allows this, but even so that will not help everyone, there are many spreadsheets out using copious VBA code there that cannot be retired, so they will lurch onward zombie-like through the years, eating the brains of those unfortunate enough to have to maintain them.
But I digress.
Basically, VBA communicates with other platforms using an object model known as COM. It does not use .NET. So, you must either use 1) a "com-callable wrapper" technology to present C# objects to VBA as if they were COM objects or 2) a "runtime-callable wrapper" used to present the Excel object model to C# as if it were a .NET library.
If you want to control C# code from your excel sheet (which is probably what you want to do) you have to pick #1. If you want to control your excel sheet from C# code, you have to pick #2. If you pick #1, you will face wretched performance. If you pick #2 you will have to deal with Excel's wretched object model.
Be assured you will have to refer to msdn.microsoft.com quite a bit if you want to do something like this. The problem isn't figuring out how to do this - Microsoft's tools make it easy. The problem is figuring how to handle horrendous performance or debugging issues. Good luck.
But I digress.
Basically, VBA communicates with other platforms using an object model known as COM. It does not use .NET. So, you must either use 1) a "com-callable wrapper" technology to present C# objects to VBA as if they were COM objects or 2) a "runtime-callable wrapper" used to present the Excel object model to C# as if it were a .NET library.
If you want to control C# code from your excel sheet (which is probably what you want to do) you have to pick #1. If you want to control your excel sheet from C# code, you have to pick #2. If you pick #1, you will face wretched performance. If you pick #2 you will have to deal with Excel's wretched object model.
Be assured you will have to refer to msdn.microsoft.com quite a bit if you want to do something like this. The problem isn't figuring out how to do this - Microsoft's tools make it easy. The problem is figuring how to handle horrendous performance or debugging issues. Good luck.
VSTO
Joe, thanks again.
I think VSTO 2005 SE will do the job. Yes, a VBA wrapper for C# will do the job. I saw a person demonstrated Matlab integrated C#. I have contacted Microsoft and hopefully I can hear some good news soon.
I think MS announced earlier that the intention of VSTO is to "replace" current VBA platform. Due to Excel is using COM object model so porting to .Net may take some times. However, I do not see any tedious problems for MS.
I mean people who use VB 6 or VBA can still use their applications. For new development, the trend is going forward to .Net platform. As far as trading system platform I will vote for .Net.
Cheers,
K
Joe, thanks again.
I think VSTO 2005 SE will do the job. Yes, a VBA wrapper for C# will do the job. I saw a person demonstrated Matlab integrated C#. I have contacted Microsoft and hopefully I can hear some good news soon.
I think MS announced earlier that the intention of VSTO is to "replace" current VBA platform. Due to Excel is using COM object model so porting to .Net may take some times. However, I do not see any tedious problems for MS.
I mean people who use VB 6 or VBA can still use their applications. For new development, the trend is going forward to .Net platform. As far as trading system platform I will vote for .Net.
Cheers,
K
Here's a link that provides some clarity on VSTO vs. VBA:
http://msdn.microsoft.com/msdnmag/issues/07/08/VSTO/default.aspx
http://msdn.microsoft.com/msdnmag/issues/07/08/VSTO/default.aspx
- Joined
- 11/19/07
- Messages
- 18
- Points
- 11
If you are using Excel 2002 or higher, you can call C# assemblies [as long as they follow the interface].
Here are some links:
http://msdn2.microsoft.com/en-us/library/aa140061(office.10).aspx
http://msdn2.microsoft.com/en-us/library/aa140056(office.10).aspx
I am using it at my company and calling C# assemblies from Excel VBA and sometimes directly as a formula in the Excel cell.
Here are some links:
http://msdn2.microsoft.com/en-us/library/aa140061(office.10).aspx
http://msdn2.microsoft.com/en-us/library/aa140056(office.10).aspx
I am using it at my company and calling C# assemblies from Excel VBA and sometimes directly as a formula in the Excel cell.
- Joined
- 5/2/06
- Messages
- 12,164
- Points
- 273
If you have Visual Studio 2008 Pro/Team version, then VSTO 2008 comes with it. I don't think they offer standalone VSTO version anymore.
I'm developing a couple of C# applications in VS now so I'll look into making my C# apps an addin in Excel 2007.
I'm developing a couple of C# applications in VS now so I'll look into making my C# apps an addin in Excel 2007.
- Joined
- 3/23/07
- Messages
- 130
- Points
- 26
I've had so much trouble with putting .NET on top of Excel, that I would not recommend it. For me it worked fine up to a point, but once I started doing a large amount of calculations/cell changes things would bog down and eventually would crash Excel. It got to be so much trouble that I gave up and ported it to be a stand alone VB .NET program. Things work great now, and it really didn't take that much more programming.
In VSTO 2008, it is not difficult at all. All built in and it is easy to use. All we need to do is to create shared assembly in VSTO and then check the add-in. You can easily share from Excel. There are at least two vendors offer C# QF tools. I couldn't remember the names. I will let you know if I find out.
These vendors provide easy solutions for metrics solution in C# and other stuff like graphical solutions.
These vendors provide easy solutions for metrics solution in C# and other stuff like graphical solutions.
- Joined
- 5/2/06
- Messages
- 12,164
- Points
- 273
I'm actually looking for a way to port my C#/VB.NET code to Excel as an addin. I know VSTO is the way to go but haven't actually played with it.
Anyone's done this before can suggest a book, website ?
I'm using VS 2008 if it makes any different.
Anyone's done this before can suggest a book, website ?
I'm using VS 2008 if it makes any different.
- Joined
- 5/2/06
- Messages
- 12,164
- Points
- 273
An update to the post above.
I have added the Euro option pricing (BS model) which I wrote as a stand alone C# app into Excel 2007 via VSTO. This involves creating a new ribbon that when you click will display/hide the panel where you calculate.
Here is a screenshot of the C# code inside Excel 2007 as an addin. It shows a custom ribbon as well as the input inside a task panel on the right.
I have added the Euro option pricing (BS model) which I wrote as a stand alone C# app into Excel 2007 via VSTO. This involves creating a new ribbon that when you click will display/hide the panel where you calculate.
Here is a screenshot of the C# code inside Excel 2007 as an addin. It shows a custom ribbon as well as the input inside a task panel on the right.
Attachments
- Joined
- 5/2/06
- Messages
- 12,164
- Points
- 273
Have fun. Keep in mind that I tested it with VS2008 Team edition and Excel 2007.
Looks nice Andy. I just want to add my opinion on Excel and .NET intergration (I know it might looks like an ad but I believe this information might be really usefull to visitors of this forum and could save them a lots hours of programming).
I've been working with Excel, VBA, .NET and C# for quite some time and for last few years in the as a developer in quantitative finance area (research / support). During this time I have been built several Excel <-> .NET frameworks, and very recently I finished a v.2.0 of my latest Excel&.NET RAD development kit and at the moment it is available as a public beta version.
The main idea - is to simplify Excel to .NET integration as possible - at the moment it is not a drag-n-drop type of integration yet, but quite close.
And it also comes with a lot of features: support of debugging, monitoring, profiling, document generation, remote assistance for the users, etc.
If you are interested - you may get a free fully functional beta version from here:
http://excel4net.com/Download.aspx
"Quick overview" page is here http://excel4net.com/Overview.aspx
and
"Getting started" documentation is here: http://excel4net.com/Documentation.aspx
If you have any questions about Excel4Net or a general question on Excel and .NET development - you can either post it here (if it's ok with Andy) or email me to beta@excel4net.com.
Happy Holidays!
C# Excel Help
Check with the following url , some useful c# excel help
http://csharp.net-informations.com/excel/csharp-excel-tutorial.htm
jerryil.
Check with the following url , some useful c# excel help
http://csharp.net-informations.com/excel/csharp-excel-tutorial.htm
jerryil.
Looks like some interesting examples on how to utilize Excel object model from desktop applications, but from my experience most of the quants use Excel and .NET quite differently - Excel as a front end UI and .NET assemblies as a place to put calculation and other business logic, not the vice versa.
Similar threads
