Excel VB.net: VSTO vs .NET DLLs

Hi

I develop VB.net Excel applications. I am currently on a project where an Excel spreadsheet containing thousands of lines of VBA has to be protected and moved over to VB.net. I want to used an Excel 2007 spreadsheet application while another developer says he wants to rather build a set of .net DLLs for it. What is the difference and what are the pros and cons
Murray BrownMicrosoft Cloud Azure/Excel Solution DeveloperAsked:
Who is Participating?
 
Meir RivkinConnect With a Mentor Full stack Software EngineerCommented:
using separate .net dlls allows you to modify them in the future without the need to rebuild the whole excel application.
if the dlls are the heart and soul of your application it's a very good idea.
0
 
CodeCruiserConnect With a Mentor Commented:
DLLs would make it possible for you to reuse business and other common logic in other projects(for example winforms) if you need to.
0
 
Murray BrownMicrosoft Cloud Azure/Excel Solution DeveloperAuthor Commented:
Any cons concerning dlls
0
 
Meir RivkinConnect With a Mentor Full stack Software EngineerCommented:
the cons rises when u deal with different target platform (32/64 bit) or cross platform application.
in those cases its easy to have everything in a single executable and not dealing with marshaled data and being required to have 2 sets of dll's, 32bit and 64bit (although it hardlt ever happens).
overall, i can't think of a real reason not to use dlls.
another (big) advantage is unit testing.
when dealing with complicated business model, its easier to create test project which separately tests one or more dlls without running the whole application.
0
 
Murray BrownMicrosoft Cloud Azure/Excel Solution DeveloperAuthor Commented:
Thanks very much for the help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.