Re: Upgrade from VS2005 Pro to VSTO?

Thanks for your reply Norman.

No doubt you're right although it seems a shame to penalise single
developers who, I assume, represent a small share of the VS market anyway.

I see that Team Suite starts at about GBP1600, which seems a bit too much
just to add the document-level functionality I was hoping for!

I guess I'll just stick with the current VSTO SE Beta version for now!

Best regards

John

"Norman Yuan" <NotReal@xxxxxxxxxxx> wrote in message
news:%23PjI53Q%23GHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
No way to "upgrade" VS2005Pro to VSTO2005, because the two suites are in
the same level of "technical depth". They have the same functionalities
for most parts with some key features missing in each one, as you
realized. I found VSTO, by its name, is very misleading, adding the fact
the previous version of VSTO is an add-in to VS. The result is that you
were misled, although your side of mistake (not reading the details of the
product carefully enough) has to take some blame.

From point view of marketing, it is obvious this will force many
developers to go with team suite, rather than by either VSPro or VSTO,
because the mutually excluded features in the 2 suites are very commonly
interesting developers. Team suite make more money than VSTO's Office part
as add-in.

Back to reality, your options are, either buy VSTO with its most features
being redundant, which makes your look stupid in front of your boss; or
upgrade to team suite, even your are the sole developer in your office.

"John" <JohnSickOfSpam@xxxxxxx> wrote in message
news:eksvRuP%23GHA.2180@xxxxxxxxxxxxxxxxxxxxxxx
Does anyone know the thinking behind splitting VS2005 Pro and VSTO (and,
aside from the new VSTO SE Beta that enables add-ins, why you don't seem
to be able to add the Office functionality to Pro)?

I bought Pro a couple of months ago and didn't really appreciate the
difference at the time and so now, as far as I'm aware, if I want to use
the Office functionality inside Visual Studio I have to buy another full
product (please tell me I'm wrong).

Now aside from the fact that it's my fault (I should have read the
details more carefully), what is the commercial thinking behind not
allowing people to pay for upgrading or at least adding the functionality
at a reasonable price? I spent over GBP500.00 on Pro, so I'm clearly not
going to spend the same again just to get the Office side? Surely I'm
not the only person who's in this situation?

Does anyone know why?

Best regards

Puzzled John





.

Relevant Pages

  • Re: Upgrade from VS2005 Pro to VSTO?
    ... parts with some key features missing in each one, ... VSTO, by its name, is very misleading, adding the fact the previous version ... Team suite make more money than VSTO's Office part as add-in. ... to be able to add the Office functionality to Pro)? ...
    (microsoft.public.vsnet.general)
  • Re: Support for optional parameters
    ... programming language, but THE central programming language of the .Net ... Office being THE cash cow at Microsoft, well, forgive me for restraining my ... The success of the VSTO initiative and the success of Office are two ... >> sure it comes in handy for a few developers out there from time to time. ...
    (microsoft.public.dotnet.framework)
  • Re: Is there a "Large Scale Python Software Design" ?
    ... perspective - what functionality the application provides & its scope. ... million lines of code (all C++ & about 60-70 developers), ... different custom servers, a full web-based administrative interface, an end-user ... I've found that competitors in our same space tend to have ...
    (comp.lang.python)
  • Re: Access 2003 and Visual Studio 2005
    ... The only thing that VSTO 2003 provides Access Developers is the Access ... Developers Extensions (ADE): a Packaging Wizard and a royalty-free license ... > previous install of Visual Studio to operate. ...
    (microsoft.public.office.developer.vba)
  • Re: XP, a Criticism
    ... >> incrementally and use refactoring to expand the necessary functionality, ... > XP relies very heavily on customer participation and unless a customer ... > requirements to both the developers and the QA people. ...
    (comp.object)
Quantcast