VSTO Installation and Excel 2003 and VS 2005
Thanks,
Martin Kulov
Thanks,
Martin Kulov
Hi Martin,
You should be able to simply re-run the Office setup, and enable the .NET Programmability support for the various Office components and this should then install the Office PIAs.
If you have any questions please let me know via the posting.
Regards,
Ken Laws
MSFT
This posting is provided "AS IS" with no warranties, and confers no rights.
For more information regarding Visual Studio Tools for Office 2005:
Best of Blogs: Visual Studio 2005 Tools for Office
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_2003_ta/html/odc_landvsto2005_ta.asp
Visual Studio Tools for Office Forum
http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=16
Visual Studio Tools for the Microsoft Office System
http://msdn.microsoft.com/office/understanding/vsto/default.aspx
That’s what I thought also.
Thanks Ken.
I will let you know if I have any difficulties. Martin Kulov
www.codeattest.com
However, when I start an Excel project in VS2005, and choose a cell, most of the properties in the property window have the following (unalterable) value:
Old format or invalid type library. (Exception from HRESULT: 0x80028018 (TYPE_E_INVDATAREAD))
Any way to solve this?
Thanks
Harry Miller
Thanks in Advance
Well, I am placing my excel workbook created with VSTO (VS2005 + Office ->Excel Workbook). Then, on compiling the the application, I place the excel application in network share. Now, if any user accesses the application from there, it prompts that PIAs are not installed. Is it possible that the PIA's get installed automatically without going through the proces of manually doing setup.
One option could be I place all the required PIAs in a MSI and execute the MSI first. But i want to avoid this option of running another file first.
I directly seek to run my excel application.
Please let me know ...
-thanks
In a scenario where Microsoft Office 2003 was installed to a computer using the default setup options, after the .NET Framework has been installed, the Office PIAs will be set to "Install on First Use".
In this scenario if a user opens a document which has a VSTO assembly attached, the PIAs should automatically install assuming that the installation source for Microsoft Office is available.
Otherwise, you would need some mechanism to get the PIAs installed in order to be able to run your VSTO application. The Office 2003 PIA redistributable package that Misha previously mentioned provides one mechanism for doing so.
Regards,
Ken Laws
MSFT
This posting is provided "AS IS" with no warranties, and confers no rights.
For more information regarding Visual Studio Tools for Office 2005:
Best of Blogs: Visual Studio 2005 Tools for Office
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_2003_ta/html/odc_landvsto2005_ta.asp
Visual Studio Tools for Office Forum
http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=16
Visual Studio Tools for the Microsoft Office System
http://msdn.microsoft.com/office/understanding/vsto/default.aspx
You should be able to install Visual Studio 2005 onto the computer without needing to reinstall Excel 2003 or Visual Studio 2003.
If you are going to install Visual Studio 2005 and want to keep Visual Studio 2003 I would suggest doing a side-by-side install which should leave VS 2003 intact.
A couple of issues that you most likely will encounter regarding your VSTO projects that you created with Visual Studio 2003 after the install of Visual Studio 2005.
1. Once Visual Studio 2005 is installed Microsoft Office will load your VSTO 2003 projects using the .NET 2.0 Framework, so you may need to add security policies to the 2.0 Framework in order for the project to load.
2. Once Visual Studio 2005 is installed you may encounter problems debugging your VSTO 2003 project from within Visual Studio 2003. This is again a result of Microsoft Office loading the project in the 2.0 Framework. A couple of options that you have for debugging would be to convert the project to a VSTO 2005 project and you could then debug using Visual Studio 2005 or you could also implement an app config file to force Microsoft Office to load the project in the 1.1. Framework.
I hope this helps!
Regards,
Ken Laws
MSFT
This posting is provided "AS IS" with no warranties, and confers no rights.
For more information regarding Visual Studio Tools for Office 2005:
Best of Blogs: Visual Studio 2005 Tools for Office
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_2003_ta/html/odc_landvsto2005_ta.asp
Visual Studio Tools for Office Forum
http://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=16
Visual Studio Tools for the Microsoft Office System
http://msdn.microsoft.com/office/understanding/vsto/default.aspx