#Office 2010 pia how to
#Office 2010 pia install
#Office 2010 pia code
#Office 2010 pia plus

#Office 2010 pia install

ItвЂ™d be so much simpler if the VSTO Runtime was automatically installed with Office or the Framework, but as we know, Microsoft are trying to reduce install sizes these days not add to them. NET Framework and the VSTO Runtime, and complex VSTO applications can be installed with a single install and enabled to configure itself. This is welcome news to VSTO developers (actually probably more so for IT Managers).

No-PIA installs (no need to include the PIAs вЂ“ achieved via Type Embedding вЂ“ a feature in CLR 4.0.

Post deployment custom actions (eg moving files to user directories, deleting files during uninstall).

Multi-project deployment (eg install an Outlook add-in, Excel add-in and Word add-in all at once).

As the recent PDC presentation from Saurabh Bhatia demonstrated (PowerPoint file here), thereвЂ™s already key functionality increases.

So, itвЂ™s good to see that the team are making excellent progress in VS2010. NET 3.5 further eased the process.Д«ut, itвЂ™s a process that still needs improvement. The VSTO team have been focusing on deployment and security issues over the last 2 releases, and in the VS2008 release they made significant improvements.

#Office 2010 pia how to

Finally thereвЂ™s limitations with how to control post-install events (Eg copying Word or Excel templates into the proper locations). For developers like you and me this doesnвЂ™t sound like much of a problem, but for an IT Manager in charge of rolling a simple VSTO app out across an enterprise this can be a significant headache (although Group policy can solve some of this).ДЄnd it doesnвЂ™t stop there, because if you have a number of VSTO add-ins going out, each of them needs to be installed separately.

#Office 2010 pia plus

The issue is the size of the download, plus requiring Admin privileges on the box you are installing on. Now, packaging these isnвЂ™t the issue, since the Visual Studio team have worked hard to make the ClickOnce process a simple and seamless experience. Simply remove the word ' Class' from the new statement.One of the biggest hurdles with VSTO is deployment.ДЄs you probably know, the pre-requisites for running a VSTO app (even of the simplest Hello World variety) include: The synthetic ' XxxxClass' classes are not embedded, just the ' Xxxx' interfaces.

#Office 2010 pia code

A worst-case scenario is targeting a newer version than you have installed on your machine, that's liable to make your program crash with very hard to diagnose exceptions like AccessViolationException.Дo note that you have to make small modifications to your code to allow it to work. They've kept it up for 15 years now but it has been running out of steam. Actually doing this is questionable, Microsoft has a hard time keeping new Office versions completely compatible with old versions. If that's a requirement then you still need the PIAs for that version, force the Embed Interop Types to True in the Properties window. If you load an old project that previously used PIAs then just remove those reference assemblies and add them back from the COM tab.Дo note that a feature is lost, intentionally targeting an old version of Office that you don't actually have installed on your dev machine is more difficult. And pick, say, ' Microsoft Excel 15.0 Object Library' to generate the interop types for a program that uses Excel. NET Framework tab, you now use the COM tab. Instead of adding a reference to the assemblies as available in the Add Reference dialog. Many megabytes reduced to a few kilobytes. In addition, the PIAs for Office are very large, the great advantage of embedding the interop types is that your assembly only contain the types that you actually use. Solving the issue when neither takes care of it, an entirely too common mishap. The feature is very desirable, it avoids your customer having to install the PIAs on his machine and for you to include them with your installer. Which is the reason that Microsoft doesn't publish the PIAs for Office 2013, they expect you to embed the interop types instead. A good video that covers the underlying technology is available here. Supported since Visual Studio 2010, you'll find it back in the Properties window when you select a reference assembly. They have been thoroughly and elegantly replaced by the 'Embed Interop Types' feature, also known as the 'No PIA' feature. PIAs are a historical artifact, required only by old.