Back in 2005 Stephen Bullen, Rob Bovey and John Green collaborated on one of the most useful Excel development books ever written. That book, affectionately known as PED (Professional Excel Development) has been a staple for most Excel Devs ever since. As you can see my copy has had a lot of use!
Hi Dennis,
Q: I notice that 2009 marks the 20 year milestone for “XL-Dennis”, for the few readers that might not be familiar with your work and background could you tell us a little bit about what you do?
A: I have a Masters in Business Management & Accounting and I started to use spreadsheet in the mid 80’s. Back then Lotus 1-2-3 was the #1 spreadsheet tool which I used on a daily basis. The concept of XL-Dennis was created in the end of the 80’s and it started out with the Excel 2.1c version. XL-Dennis utilises Excel and other tools to develop professional business solutions. For the last 3-4 years I have been specialising in .NET and VSTO and today most clients’ solutions are based on these two technologies.
20 years with Excel has so far been an exciting journey and I’m looking forward for the coming 20 years.
Q: How did you become involved in the second edition of the PED?
A: When Rob and Stephen outlined the second edition they wanted a new section that covered Excel and .NET. They quickly found out that there are not so many developers in the Excel community that have the knowledge and the practical experience to work with Excel and .NET. So they ended up with a non-English and non-MVP person like me.
Q: I believe this is your first outing as an author, how does it feel to have your name in print and how much work did it all take?
A: That’s correct although I have contributed with some materials in other Excel books. Having your name associated with these guys’ is an absolute honour. To see your name on the coverage (second billing) on a book like PED is very pleasant and satisfying given all the work.
I didn’t count the hours but imagine that you start out with a blank Word document and the final version is 50-60 Word pages per chapter. Although my English has improved the language itself is a barrier that has consumed much time for me.
I take this opportunity to thank Rob for all his support. He has been the team leader for this edition and in my opinion he has done an excellent job. I would also like to thank Gabhan Barry (a Program Manager in the Excel group at Microsoft) who has been the technical reviewer of the .NET chapters.
Q: That’s a significant effort, was it worthwhile, would you do it again?
A: I would say it’s nice when the work is done but during the process you go through all the emotions. At present I would turn down any offers however in the future, and if a new edition of PED is to be produced, then I’ll have probably forgotten all the hard work and say “yes” again.
Q: PED was a critical success, how did you go about writing new material for it. Was this a challenging undertaking and did you feel you had to live up to the high standard it originally set?
A: Initially it was a burden for me but when I realized that I’m the guy with all the .NET knowledge and experience in the team I managed to place myself in a better position. Because I always try to deliver high quality myself the standard of the first edition was not an issue for me. In fact, I got more motivated.
Q: PED’s treatment of Excel was as a powerful development platform. It was aimed at experienced developers, really wanting to push the boundaries of Excel development. Should we anticipate the seconded edition to be pitched at the same audience?
A: Yes, the second edition also targets the professional Excel developer. We continue to support best practice and try to catch up with the latest technologies .NET and VSTO. This is the first Excel book that covers VB.NET and VSTO in detail.
Q: What can we expect to get out of the second edition, what’s new and what’s been updated?
A: Because this is the second edition we feel it is important to be very clear on this aspect so that potential buyers can make a good decision to buy or not.
The second edition includes five new chapters. One chapter covers Ribbon UI in Excel 2007, another new chapter is about creating cross-versions applications and three chapters are about .NET and VSTO. The book has 29 chapters in total so 24 chapters have had minor updates.
If the potential buyer has little interest in .NET and VSTO and already has the first edition of the book then I would recommend to save the money and wait for the next edition.
It is also important to know that to follow the chapters about .NET and VSTO it requires VS 2008 Professional or later. To fully leverage the VSTO chapter it also requires Office 2007. In addition, to put .NET solutions in production it is also recommended using a commercial digital certificate.
With this edition we will launch a site devoted to the book. It will consist of updates, additional materials etc and a forum in which the readers can communicate with us.
Q: The VBA community have been a little reluctant in adopting .NET technologies; do you see this as a problem?
A: As long as the standpoints are based on genuine business terms I cannot see anything wrong with it. For the professional Excel developer the question is not if rather when to adopt .NET. We hope that the second edition will get them started.
Q: VSTA shipped with info path in office 2007 but was not integrated in any other apps. Do you think getting VSTA in Excel would spark some passion for .NET with Office Devs?
A: Looking ahead we know that Microsoft will incorporate a new IDE with Excel. The question is two folded; in which version of Excel will the new IDE be available and which .NET language will be in use. To answer the question I must honestly admit that I have no idea.
Q: What are some of the major benefits to leveraging the .NET Framework over more traditional VBA solutions?
A: Two words: Security and deployment. With .NET we have a new security model and VBA has nothing like it. As for deployment we can now deploy our solutions in several (secured) ways.
Q: Like any new technology .NET has a learning curve. What do you think the average time investment would be for a VBA developer coming to .NET?
A: All I can say is that requires a lot of hard work. As a kick start I would recommend to take a class in general VB.NET programming.
Q: How do you see the future 5 to 10 years shaping up for Office developers? Will VBA still be king, or is a move to .NET just a matter of time?
A: In the foreseeable future we will work with two types of environment: the desktop and the web office. As long as VBA is around it will continue to play a central role for the desktop environment together with .NET while for the web Office environment .NET is the only available alternative.
Q: In the first edition chapter 22 was dedicated to Excel and .NET and its focus was VSTO. Will the update include details on managed Com addins and/or automation?
A: I’m pleased to say that the second edition includes three new chapters devoted to Excel & .NET:
Chapter 24 Excel and VB.NET (77 pp): This is an introduction to the VS IDE, VB.NET and automation of Excel with VB.NET. We have intentionally tried to pitch it at a beginners level.
Chapter 25 Writing Managed COM Add-ins with VB.NET (90 pp): This is the “flagship” for the .NET section in the book and we step through all the steps to create and deploy managed COM add-ins, including a discussion about managed Automation add-ins.
Chapter 26 Developing Excel Solutions with Visual Studio Tools for Office System (58 pp): In this chapter we discuss what VSTO is and when to use VSTO. In our experience this is a must so that the reader can decide if VSTO is something to pick up or not. We also discuss VSTO add-ins and single workbook’s solution together with how to deploy VSTO solutions from a web site.
For the chapter 24 and 25 we have a practical case study: PETRAS Report Tool .NET which interacts with a SQL Server database and with some predefined native Excel templates.
Q: One of the often bemoaned issues with VSTO is that most of the sample code is presented in C#. Happily PED used VB, can we expect this to continue?
A: Yes, PED will still be supporting VB for the foreseeable future. It’s remarkable that Microsoft has such a strong focus on C#, especially if they want professional VBA developers to port themselves to the .NET platform.
Q: Following on from the previous question, what language type do you prefer and why, would you strongly recommend one over the other when targeting Office?
A: In general I would like to avoid discussions about which language to use and so forth.
Today we can meet clients’ requirements for Office solutions with a toolbox that includes a various number of tools, VBA, classic VB, VB.NET and VSTO. In some situations the choice is dictated by the customers or by their desktop environment. In other cases we can select tool(s) to be used on our own.
But if we only discuss the question from a strictly technically perspective then .NET is in favour as it offers a modern IDE.
Q: When can we expect PED to hit the shelves?
A: The book is scheduled to be available in May 2009. (See it at Safari here)
Q: And finally, do you have any plans for a second international VSTO conference in the Phone Box, and will the beer still be free!!!!
A: Actually we will have the release party for the second edition of PED in the Phone Box at XL-Dennis Street. And believe it or not the second VSTO conference will also be held there and at the same time! In addition to the free beer we will also give away unknown bugs in Excel for free too!
Thanks Dennis, I’m sure the second edition will be a success!
Is C# like Robby Williams?
4 February 2009 by Ross McLean
When Take That first came on the seen Robby Williams was a young sexy super stud, loved by all, women wanted to be with him, men wanted to be him (ok, maybe the analogies not perfect). Now he’s a slightly overweight widero who chases flying saucers.
And so C#. When it came out (easy!) developers flocked to it, hailing it’s development speed over C++, and hoisting it’s strongly typed compile time error detection pants up the flag pole of integrity. Now, with C# 4 around the corner, those panties have slid down the pole a bit, as MS have seen fit to invite a bloshy Dynamic Runtime Library sorry, Dynamic Language Runtime (- what every it’s called!) to the party.
What am I going on about? Well, MS have stated that they want to bring VB, and C# much closer, so that new features in either language (read C#) are deployed at the same time in both. Other stuff that’s coming with the new release of .Net is the Dynamic Runtime. I’m no expert – in fact what I am is a Luddite on a soap box – but for this to work (with out having to write 10 million lines of code), C# has to have much of the features of VB, basically dynamic types. This is not necessarily a requirement at the developer code level, but required to make the language work with external object. This in turn means that .Net can work more directly with Office and all other components developed in other languages! – cool!. Hence why they can get rid of the dreaded PIA’s.
Along with this MS are making other changes, like named arguments and not having to write ref missing 10 billion times to fill out all the optional parameters. Also in VSTO deployment is getting better too.
So the point? well 2 things really:
1. In both VB and especially C# it’s getting easier to develop,… for Office.
2. C# and VB are getting even more alike, expect to see “with {}” some time soon. Why an organization would invest in developing 2 languages that both have the same strengths and weakness is for Stevie Bulmmer to debate, but I can’t see the point can you?
As always, M.I.E will be the 5th or 6th to bring you slightly wrong information about the latest developments in the world of Office and .Net.
Some links worth reading if you want to find out more:
The Future of .NET Languages
Office client developer enhancements with VS 2010
VSTO news
Tags: Comment, VB.Net
Categories: C/C++, General, VB.Net, VSTA, VSTO • 5 Comments »