.NET Framework - This newsgroup

Asked By theNugget2009

12-Sep-09 06:08 AM

Hi All

I have been reviewing this Newsgroup for a while and there never seems to be
much activity on it. Where is there a active Forum\Newsgroup for VSTO?

Regards

D

13-Sep-09 01:00 PM

The main reason is that, I guess, there is not a lot people doing VSTO
development: it is jsut too risky in term of ROI (return of investment).
Basically, you can only target Office 2007 and Office2003 Pro users. I'd
better there are still more Office 2003 users that Office 2007. Among Office
2003 users, how many of them use Office 2003 Pro, instead of Office 2003
Standard? Even VS2008 made quite some changes to VSTO so that it is a bit
easier to work with than VSTO2003/5, still, comparing to VBA, it is just too
early to to choose VSTO than VBA.

14-Sep-09 09:02 AM

The main VSTO support area is an MSDN Web forum. The VSTO team participates
there and there is a lot more traffic there.

The URL for that forum is
http://social.msdn.microsoft.com/forums/en-US/vsto/threads/

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm

18-Sep-09 03:12 PM

Hang on, i thought you could target Office 2003 Standard users?

22-Sep-09 10:07 AM

Only the stand-alone Office app, such as MS Word 2003, or MS Excel 2003. or
MS Outlook 2003 as individually bought product, not the ones coming as part
of MS Office2003 standard suite. In reallity, there a much less users who
bought MS Office app individually than uses who have Office2003 suite, be is
Standard suite or Pro suite. Yes, VSTO project only works with Office 2003
Pro and individual lisenced app, not the Standard (or Basic, as many OEM
pre-loaded into a new computer) suite, which are used by most users.

23-Sep-09 03:37 AM

Isn't this a ballsup by Microsoft, in my firm most users have standard
edition as they do  not require Access.

25-Sep-09 08:27 PM

I would not waste time on VSTO stuff, before .NET4.0 and VS2010, at least,
and maybe, only with MS Office2010 or later(?). too.