Howard,
| > For Microsoft Outlook, VSTO allows you to create a managed COM Add-in
for
| > Microsoft Outlook.
|
| Could one not already do that with VB .NET or C#?
| How does VSTO make this better/
The "biggest" advantage I've seen so far with VSTO, is that you no longer
need to create C++ shims to go between Outlook's COM World & .NET World. See
the following article for details:
http://msdn.microsoft.com/office/de...html/Office_VSTOOutlookAdd-inArchitecture.asp
Here are a couple more good articles that discuss VSTO for Outlook:
http://msdn.microsoft.com/office/de...a/html/OfficeVSTOIntroducingOutlookAdd-in.asp
http://msdn.microsoft.com/library/d...alk/html/office06012005_VSTOOutlookAdd-in.asp
| > > For example, can VSTO be used to create a DLL, in particular, a DLL
that
| can
| > > be used as an ActiveX DLL with Office?
Yes VSTO for Outlook creates a DLL, as the COM Add-in is deployed as
inprocess. I seem to remember that Word & Excel VSTO also create DLLs, I
would expect InfoPath does also, however I have not tried the InfoPath yet.
| > > In VSTO, other than the addition of the support for Office 2003 and
| omission
| > > of C++, are there ANY other differences between VS Pro and VSTO?
?? VS Pro is an edition of Visual Studio. VSTO is a set of tools that you
use with VS Pro & higher to simplify creating Add-ins for specific office
products (Word, Excel, InfoPath, and Outlook)...
Hope this helps
Jay
| | > I've included a couple of links below that I hope will address your
| > questions regarding system requirements and the differences between
Visual
| > Studio 2005 Professional and Visual Studio 2005 Tools for the Microsoft
| > Office System.
|
|
| Thanx.
|
| > Visual Studio 2005 Beta 2 System Requirements
| >
http://lab.msdn.microsoft.com/vs2005/resources/sysreqs/default.aspx
|
| I'll need to get another computer.
|
| > Comparison of the Visual Studio Editions
| >
http://msdn.microsoft.com/howtobuy/vs2005/editions/pro/
|
| I had seen that.
|
| >> For Microsoft Word and Microsoft Excel, VSTO allows you to create a
| managed
| > .NET assembly to add additional functionality to a template, document,
or
| > workbook. The assembly is document-centric and as such gets loaded when
| the
| > user opens the document or workbook.
|
| That appears to be no different than with VSTO 2003.
|
| > For Microsoft Outlook, VSTO allows you to create a managed COM Add-in
for
| > Microsoft Outlook.
|
| Could one not already do that with VB .NET or C#?
| How does VSTO make this better/
|
| The following remain unanswered:
|
| > > For example, can VSTO be used to create a DLL, in particular, a DLL
that
| can
| > > be used as an ActiveX DLL with Office?
| > >
| > > In VSTO, other than the addition of the support for Office 2003 and
| omission
| > > of C++, are there ANY other differences between VS Pro and VSTO?
|
|