Announcing Visual Studio Tools for Office, Version 2005 Beta

Visual Studio Tools for Office, Version 2005 Beta 1 Announced

Visual Studio Tools for Office, Version 2003 — Thu, 01 Jul 2004 01:42:00 GMT

re: Announcing Visual Studio Tools for Office 2005 Beta

Sean — Thu, 01 Jul 2004 01:00:00 GMT

The name just begs the question "Where can I get a copy of Office 2005??"

"Oh, you mean it works with Office 2003? *scritch*scritch* but it -says-..."

;)

Yikes.. anyway you sling it, it's still a mouthful.... maybe some names that would be less ambiguous would be ...

"Visual Studio 2005 Beta Tools for Office"?
"Visual Studio Tools for Office Release 2005 Beta"?

"Visual Studio Tools for Office - The Search For Spock Edition"?

re: Announcing Visual Studio Tools for Office 2005 Beta

Cyriel — Thu, 01 Jul 2004 08:05:00 GMT

Aren't the OfficeZealot blogz located over @ http://www.officezealot.com/BlogHome.aspx or did they take over gotdotnet? ;-)

re: Announcing Visual Studio Tools for Office 2005 Beta

Cyriel — Thu, 01 Jul 2004 08:07:00 GMT

correction: blogs.officezealot.com ... what can i say it's early in the morning ;)

re: Announcing Visual Studio Tools for Office 2005 Beta

Cyriel — Thu, 01 Jul 2004 12:11:00 GMT

@ Sean: What about "Visual Studio 2005 Tools for Office 2003" ? ;-)

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Paul Cornell — Thu, 01 Jul 2004 15:34:00 GMT

Thanks, Sean, for pointing out the issue with "Office 2005." The official name of the product is Microsoft Visual Studio Tools for the Microsoft Office System, Version 2005. We sometimes shorten it to Visual Studio Tools for Office, Version 2005. Some folks even shorten it to Visual Studio Tools for Office 2005, which is incorrect, because it gives folks the impression there is an Office 2005, which is also incorrect. Sorry for any confusion.

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Paul Cornell — Thu, 01 Jul 2004 15:32:00 GMT

Thanks, Cyriel, for catching the incorrect URL. It has been changed to http://blogs.officezealot.com/chris/.

Visual Studio Tools for Office

doncampbell's WebLog — Fri, 02 Jul 2004 03:34:00 GMT

Visual Studio Tools for Office

doncampbell's WebLog — Fri, 02 Jul 2004 06:03:00 GMT

Back after a break!

Scott McCulloch — Fri, 02 Jul 2004 11:56:00 GMT

La Siguiente Generaci

Nazul's Weblog — Sat, 03 Jul 2004 18:38:00 GMT

La Siguiente Generaci

Nazul's Weblog — Sat, 03 Jul 2004 18:41:00 GMT

Es tiempo de betas: Visual Studio 2005, Visual Studio Express Products, SQL Server 2005.

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Joseph peleg — Mon, 12 Jul 2004 09:20:00 GMT

I need beta version of visual studio net

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Paul Cornell — Mon, 12 Jul 2004 15:41:00 GMT

Head over to http://lab.msdn.microsoft.com/vs2005/ for instructions on how to get the beta.

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

John Smith — Wed, 14 Jul 2004 22:17:00 GMT

I have 2 concerns

1. When I deploy my VSTO 2.0 applications to my customers' machines, do they need to have Office 2003 installed? I know VSTO 1.0 needs that.

2. How about VSTO pricing? VSTO 1.0 is priced $499. Will VSTO 2.0 be much more expensive than that?

Thanks.

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Paul Cornell — Wed, 14 Jul 2004 22:19:00 GMT

Yes, customers need Office 2003 installed.

It's too early at this time to discuss VSTO 2.0 pricing.

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

John Smith — Wed, 14 Jul 2004 22:27:00 GMT

Thanks for your quick reply, Paul. But I have a doubt in your first answer.

At page http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx#2005, you can see:

-----------------------

Making data in Office documents a transparent, directly accessible component enables new server-side opportunities. First, the data island embedded in the document can be manipulated without starting the Office application. This is a dramatic shift from the current model, by which, in order for code to manipulate the contents of the document, Excel or Word must be running. This limitation blocks many customers from implementing a common solution requirement—creating Office documents from within an ASP.NET application.

By contrast, the VSTO 2005 runtime will support instantiation on a server without the need to run Excel or Word. The data island in a document could then be manipulated from the server-side code. When the user opens the associated Office document the view would be re-synchronized with the data island and the user would be automatically presented with the updated data. In this model, Excel and Word are not needed to write to the data on the server, but rather only to view it on the client. This updated model will provide the scalability customers desire and the ability to perform high performance batch processing of documents containing data islands on the server.

--------------------------------------

"the VSTO 2005 runtime will support instantiation on a server without the need to run Excel or Word" indicates Office 2003 is not a must to run VSTO solutions at customers' machines. Am I wrong?

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Paul Cornell — Wed, 14 Jul 2004 22:35:00 GMT

Good point, John. I should clarify further.

End-user customers will need Office 2003, the .NET Framework 2.0, and the VSTO 2005 runtime installed.

For server scenarios, the server will need at least the .NET Framework 2.0 and the VSTO 2005 runtime installed. Office 2003 is not required to support VSTO 2005 server scenarios.

Hope this helps.

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

John Smith — Thu, 15 Jul 2004 00:17:00 GMT

Sorry Paul if I keep bothering you as I'm still not quick clear about when I should have Office 2003 installed.

Let me give you a typical example. As I'm concerned with Office 2003 intallation only so I ignore other sutff such as .NET Framework 2.0 and the VSTO 2005 runtime.

You can say I'm the VSTO solution developer. I develop 2 VSTO based applications.

The first one is a Windows form application, used in a deskstop environment. Say, its name is MyDesktop. I need to deploy MyDesktop to 2 customers: Alice and Bob. For Alice and Bob, to enable them to run MyDesktop, do their desktops need to have Office 2003 installed?

The second one is a Web form application, used in a web server environment. Say, its name is MyWebServer. I need to deploy MyWebServer to 2 customers: Cindy and Danny. For Cindy and Danny, to enable them to run MyWebServer, do their web servers need to have Office 2003 installed?

re: Announcing Visual Studio Tools for Office, Version 2005 Beta

Paul Cornell — Thu, 15 Jul 2004 21:39:00 GMT

I'm confused about your scenario. It appears from the way that you've worded how you're developing your applications, that you're not calling Office-based solutions. How do you want your Windows Form and Web Form applications to interact with a VSTO solution specifically?

To recap my earlier statements:

Naturally, VSTO-based solutions need Office 2003 installed if an end user is interacting with a VSTO-based Office solution on their computer.

If you are in a VSTO server scenario, Office 2003 does not need to be installed.

In either of these two previous cases, whether you have an end-users computer or a server computer, at a minimum the VSTO 2005 runtime and .NET Framework 2.0 must be installed to interact with a VSTO-based solution.

Hope this helps.

Visual Studio Tools for Office, Version 2005 Beta 1 Announced

Di .NET e di altre amenit — Fri, 27 Aug 2004 11:11:00 GMT

It's OK to tell people what they already know

Office Development, Security, Randomness... — Fri, 03 Sep 2004 11:27:00 GMT