Tag Info

Hot answers tagged

16

The three points you listed seem fair: It is a fairly important project so it has to work - a C# solution would not be as stable or work as well as the existing a VBA-based solution. Indeed, later, you tell: "I would like to take this opportunity brush up on my C# skills as I am currently not as competent in C# as I am VBA" (emphasis mine). In other ...


7

I hate to say it, but your arguments just don't hold water. Unit testing. This has been a solved problem for a very long time. There are many Unit Testing frameworks out there. Pick one. You should have been doing this already. I recommend ours, because it integrates into the IDE and provides other great features. Source control This one is a bit ...


4

You can point out that even Microsoft states in this article: Updating the code to improve features or to fix bugs would require that the Office artifact be re-emailed, re-structured, and re-worked by every single user and in every single file that has been using the customization. The article is about different approaches of developing stuff ...


4

I would support going to C#. Others have covered your points very well, so I won't rehash what they've said. There are definitely a lot of good reasons to stick with VBA. However, one of my employers did an impeccable job at creating meaningful documentation. So much so that design decisions were actually written down with justification - if only all ...


1

I would like to take this opportunity brush up on my C# skills as I am currently not as competent in C# as I am VBA and I'd like a project like this to take me to the "next level". Be honest. Do you plan on sharing this information with the other people involved in making this decision? If not, I would place the entire blame on you if the project ...


1

It really depends on how you intend to move to C# (ie what technology you are going to use). If you are going to use OpenXML, then you are talking a total re-write which, if you have a solution that works, isn't recommended. If you are talking about using Interop, you may find that the process is surprisingly smooth. I've moved a lot of code from VBA to C# ...



Only top voted, non community-wiki answers of a minimum length are eligible