VSTO & .NET & Excel

November 1, 2012

VS 2012: A disaster for VSTO Developers?

Filed under: .NET & Excel, Apps for Office, Excel, Tools, VSTO & Excel — Dennis M Wallentin @ 9:33 pm

I thought I would get on with the blog much faster than I have done. Visual Studio (VS) 2012 has been out now for some time but still it’s ‘a new kid in town’.

First I thought I would make some kind of a walkthrough for the news in VS however I ended up turning down that approach. Let other bloggers do that.

Whenever something is dramatically changed there exist some kinds of explanation that we can take part of. Usually we understand and also accept the changes although it will take some time to do it. During the beta stage of VS 2012 I thought that some parts are already fixed and therefore not part of the beta. One of the parts that were missing was the Office Shared Add-in template.

When the RTM was released I was quite surprised to find out that the Office Shared Add-in template was not available. Later I got quite upset and raised the question in some closed mailing lists. When no one bothers to answer I realized that Microsoft had done something that they don’t want to discuss in public, not even in a closed mailing list.

From my point of view I find it to be quite a stupid action as Microsoft directly abandon a group of Office developers, those developers that only develop Office solutions with VSTO. That’s indeed remarkable as Microsoft have pushed Office developers to use VSTO for the last nearly 10 years!

Because it’s not possible to develop UDFs in VSTO Office developers need the Office Shared Add-in template. Of course, it exist external alternatives such as Excel-DNA that can easily replace the template. Perhaps another better approach is to buy a copy of the RAD Tool Add-in Express for Office and .NET. In my opinion the best RAD Tool available.

But the point here is that Microsoft silently has removed a good tool for VSTO developers and of course for other Office developers as well. Not every developer is allowed to use third-party tools when developing customized Office solutions.

Soon will the next new version of Office be launched; Office 2013. One thing that really sticks out is the new concept “Apps for Office”. Technically it means that we use JavaScript, HTML and CSS to create customized Office solutions with. Don’t hold You breath because version 1.0 only includes creating task panes for various tasks. If we look around us we can conclude that JavaScript/HTML5/CSS is hot, actually it’s so hot that You burn Your fingers. In other words, “Apps for Office” is probably the future for Office development.

What about VSTO? Well, there is no big news in VS 2012 except that VSTO Add-ins for Office 2007 is no longer available in VS. In other words, the VS Team had made another silent action. I suspect that some developers will be surprised when they launch VS 2012 for the very first time and start to look for VSTO Add-ins for Office 2007.

If we look behind the scene we notice that almost all original members of the VSTO Team at Microsoft are no longer working with VSTO. They have moved to new interesting areas inside Microsoft. It seems that the support for VSTO inside Microsoft have also been remarkable downsized.

It’s amazing how the VS Team has been able to cut off Office Developers from the .NET platform in silence.

I have some suggestions to make:

#1 Make the Office Shared Add-in template be available again in VS 2012

#2 Bring back the VSTO Add-in Templates for Office 2007

#3 Otherwise VS 2012 is a disaster for VSTO Developers!

Kind regards,
Dennis

Advertisements

6 Comments »

  1. I am also very disappointed that there is no template for Office Shared Add-Ins in VS 2012 available. Maybe someone can convince one of the Add-In developers for VS to build an Add-In or a template that make the missed functionality available. Eternal glory and honor will be the reward.

    Comment by Thomas Möller — November 2, 2012 @ 2:00 pm

    • Thomas,
      Thanks for letting me know that I’m not the only guy around that miss it.

      Kind regards,
      Dennis

      Comment by Dennis M Wallentin — November 2, 2012 @ 3:56 pm

  2. Hi Dennis,
    Great post. I have felt like office development has been going down hill at ms for a while now, around the time that 2007 came out. In fact desktop development in general seems to be something that ms are just not interested in supporting anymore. How win 8 will effect devs working in Delphi, or java, etc., I don’t know.

    they seem to be modernising and aiming for the lowest common denominator , with no regard for any one else.

    Time will tell if it works for them, but I can’t help but feel a little let down!

    Keep plugging away my old firend, maybe they will shock us all and update vba!

    All the best
    Ross

    Comment by ross — November 2, 2012 @ 10:58 pm

    • Ross,

      Good to hear from You 🙂

      I fully agree with You. Win8 is the first version that does not per se targeting the desktop platform. It’s designed to work with smart devices. Office 2013 will probably be the last version of Office that explicit target the desktop platform.

      Well, I see the same as You do; MS has left the desktop behind and instead focus on the Azur and on smart devices. In fact, .NET will hardly survive much longer as larger frameworks are no longer relevant when we switch back to primitive scipting languages.

      Sad but true…

      Take care my friend and all the very best,
      Dennis

      Comment by Dennis M Wallentin — November 3, 2012 @ 1:13 am

  3. Hi Dennis,
    What you wrote makes me very sad because it confirms my impression that MS is slowly and silently losing interest in the VSTO platform. I feel that many other developers out there have sensed this, too. There is less and less VSTO stuff on the Internet (check out MS’s sites, the silence when it comes to VSTO is deafening), no decent VSTO books have been published for several years, and now, as you mention, MS is downgrading VSTO in VS 2012; all these are ominous signs for us who love Excel. I am also stunned by the decision to take out the MSI installer from VS 2012; I apologize if I sound whining, but click-once in my eyes is merely a toy, you can’t seriously use it for any commercial VSTO application.
    Hälsningar,
    Alex

    Comment by Alex — November 3, 2012 @ 8:56 am

    • Alex,

      Thanks for Your comment and insight. I do agree with You. Ever since VSTO was ported to the Office it has become smaller and smaller. In fact, I doubt it will be alive to the next Office after 2013. Focus is on ‘Apps for Office’ and therefore VSTO will be gone.

      Kind regards,
      Dennis

      Comment by Dennis M Wallentin — November 3, 2012 @ 5:51 pm


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: