Porting Win32 and VBA code of MS Office solutions to .NET
Migrating VCL and VBA Office-based solutions to .NET
As you probably know the .NET Framework has a number of advantages compared to Win32 programming:
However, Office programming is a tricky area. If you decide to migrate your Win32 or VBA Office code to .NET yourself, you should be aware of some specificities that might turn this task into a pretty hard job. Such things as an immense number of .NET Framework classes, peculiarities of host application object models, necessity to deal with a different strategy of releasing COM objects, and other stuff like this may perplex even an experienced developer, and they do complicate the process of migrating.
What can we do for you?
Almost everything. Indeed. We have been working in this area for years. We do know many things: object models, Office bugs and workarounds, functioning and inner structure of Office windows, ins and outs of all Office applications. We have created hundreds of solutions, have written dozens of articles and HowTo examples. We used this knowledge to develop our programming tools, now we can use it for porting your Office solution to .NET, whether it is a COM add-in, Excel Automation add-in, XLL add-in, RTD server, or Smart Tag. We can migrate your Office code to VB.NET or C#, with or without using VSTO.
Here is just a short list of what we can do for you:
Such things can be done very quickly, say in a day or two. If you need something more complicated, write to us and tell about your requirements. We will sign an NDA, agree on the timeframe and cost, and you will have the working solution in a short while.