I'm trying to add the Microsoft Office InterOperability reference to my header but I cannot find it.
I went here: http://msdn.microsoft.com/en-us/library/kh3965hw.aspx
I installed the PIAs but I cannot find the reference still. There is a registry entry in the Add and Remove Programs but for some reason Visual Studio 2010 is not seeing it.
Edit: I have Visual C# 2010 Express
Visual Studio will install these Office PIA files as well to the following:
When you install Visual Studio, the PIAs are automatically installed to a location in the file system, outside of the global assembly cache. When you create a new project, Visual Studio automatically adds references to these copies of the PIAs to your project. Visual Studio uses these copies of the PIAs, instead of the assemblies in the global assembly cache, to resolve type references when you develop and build your project.
These copies of the PIAs help Visual Studio avoid several development issues that can occur when different versions of the PIAs are registered in the global assembly cache.
Visual Studio installs these copies of PIAs to the following locations on the development computer:
%ProgramFiles%\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office14
(or %ProgramFiles(x86)%\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office14 on 64-bit operating systems)
%ProgramFiles%\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office15
(or %ProgramFiles(x86)%\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office15 on 64-bit operating systems)
Did you include the Office files when installing Visual Studio?
If not, then run Visual Studio setup again and choose to Add Options and choose the Office PIA relevant pieces.
Related
Where can I find Create GUID options in Visual Studio 2017?
I'm using Visual Studio Enterprise 2017 Edition and I'm not finding the Create GUID options from the Tools menu.
Please follow troubleshoot section in this documentation.
https://social.technet.microsoft.com/wiki/contents/articles/33047.create-guid-tool-in-visual-studio.aspx
If the tool does not appear under the Tools menu, click Tools >
External Tools (see image above). It may be that the tool was not
registered correctly within the IDE. Using the External Tools window,
we can add a reference to guidgen.exe.
Mine was in Microsoft Visual Studio 11.0 instead of the Microsoft Visual Studio
Under c:\program files (x86) there are several MVS folders and each with a Common7 folder and some with Tools folder.
In one of then guidgen.exe is hiding.
Replace the links from Tools -> External Tools -> Create GUID, for example in my case
c:\program files (x86)\Microsoft Visual Studio 11.0\Common7\Tools
This is pretty late but nowadays with the C# REPL built into VS.NET or the numerous online REPLs a new guid is only as far away as a single line of C#:
Guid.NewGuid();
I have a Visual Studio 2013 extension that has a reference to Microsoft.VisualStudio.TeamFoundation.VersionControl.dll, from which the following type can be obtained:
Microsoft.VisualStudio.TeamFoundation.VersionControl.VersionControlEx
Today I uninstalled all previous installations of Visual Studio and then installed Visual Studio 2017 Enterprise with the options ".NET desktop development" and "Visual Studio extension development".
I opened the project with Visual Studio 2017 and had to replace some of the references (EnvDTE, envdte80, Microsoft.VisualStudio.Shell.15, etc) and also installed the nuget package Microsoft.TeamFoundation.VersionControl.All.
Unfortunately the namespace Microsoft.VisualStudio.TeamFoundation and therefore VersionControlEx are not recognized.
I have searched the file on my machine with FileLocator Lite and it does not exist.
Any idea how has this changed in Visual Studio 2017?
I basically to access the PendingChanges window.
Thanks in advance.
By doing a search, I was able to find the file in there:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
I also found copies associated with other versions of Visual Studio. Given the path of the file, it appears to be included along with Team Explorer.
I suspect the reason you were not able to find the file on your machine is that you had uninstalled your prior versions of Visual Studio and Visual Studio 2017 did not release with Team Explorer.
If you update your version of Visual Studio or you run the standalone installer, I expect that you will be able to find the file.
I am developing an application which will send emails using C#. The app will be able to use templates for mail, among other things. The problem is I'm having trouble finding any Office.Interop references, which means I cannot work with Outlook.
Office is installed on my computer, but I've also tried to install the PIA from this link http://www.microsoft.com/en-us/download/details.aspx?id=3508. Unfortunately, this didn't change anything: When I launch the MSI it stops without a word, and I don't know if that is part of the problem.
Look for them under COM when trying to add the references. You should find the reference below, and possibly Microsoft Outlook 15.0 Object Library, if you need that. There are similar libraries for Word, Excel, etc.:
Update: The Object Library should contain the Interop stuff. Try to add this to a source file and see if it can now find what you need:
using Microsoft.Office.Interop.Outlook;
I forgot to select Microsoft Office Developer Tools for installation initially. In my case Visual Studio Professional 2013 and also 2015.
If you're using Visual Studio 2015 and you're encountering this problem, you can install MS Office Developer Tools for VS2015 here.
With Visual Studio 2015 I have activated it with the following steps.
Programs and Features --> Select Visual Studio > Change
Choose Modify
Windows and Webdevelopment --> Tick/select "Microsoft Office Developer Tools"
Start Update
It should work now.
You can find it at link:
C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Word\15.0.0.0__71e9bce111e9429c\Microsoft.Office.Interop.Word.dll
Browse it then add references
If you have installed latest Visual studio and want to
To locate library of Microsoft.Office.Interop.Outlook or any other Microsoft.Office.Interop library then you should look into below 2 folders:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office14
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office15
Please note that folder could be C:\Program Files\
I think you need to run that .msi to install the dlls. After I ran that .msi I can go to (VS 2012) Add References > Assemblies > Extensions and all of the Microsoft.Office.Interop dlls are there.
On my computer the dlls are found in "c:\Program Files(x86)\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA" so you could check in a similar/equivalent directory on yours just to make sure they're not there?
You need to install Visual Studio Tools for Office Runtime Redistributable:
http://msdn.microsoft.com/en-us/library/ms178739.aspx
I had the same issue with Visual Studio Community 2013, I fixed it downloading and installing the latest update of Office Developer Tools for Visual Studio 2013. Now I am able to see the whole Microsoft.Office.Interop.* list when I go to
Add References > Assemblies > Extensions
you can download it from here:
https://www.visualstudio.com/en-us/news/vs2013-update4-rtm-vs.aspx#Office
http://aka.ms/OfficeDevToolsForVS2013
Just doing like #Kjartan.
Steps are as follows:
Right click your C# project name in Visual Studio's "Solution Explorer";
Then, select "add -> Reference -> COM -> Type Libraries " in order;
Find the "Microsoft Office 16.0 Object Library", and add it to reference (Note: the version number may vary with the OFFICE you have installed);
After doing this, you will see "Microsoft.Office.Interop.Word" under the "Reference" item in your project.
Hi I was wondering if the icons used in Visual Studio 2010/2012's Intellisense menu, to distinguish between Methods and Fields etc, were available for download somewhere?
They would be useful as placeholders for my current application I am developing.
The images are publicly available in the Visual Studio 2008 SDK under the following path:
VisualStudioIntegration\Common\Source\CSharp\LanguageService\Resources\completionset.bmp
I do not know what license the images are distributed under, as I have only used them as part of extensions for Visual Studio itself.
Edit: The images were distributed with the SDKs for Visual Studio 2005 and 2008, but are no longer included in the SDKs for Visual Studio 2010 or 2012.
Avalon Edit is open source and there may be images from that you can use:
https://github.com/icsharpcode/SharpDevelop/wiki/AvalonEdit
The images are the property of Microsoft and as such should not be used, I'm sure a quick google will point you in the direction of suitable images for use.
Visual Studio 2012 (and later)
For VS 2012 and later, you can download the icons from Microsoft's Visual Studio Image Library.
Visual Studio 2010 (and earlier)
According to their docs, earlier versions were bundled with Visual Studio, so you can be find them locally if you have VS installed:
Visual Studio 2005
...\Program Files\Microsoft Visual Studio 8\Common7\VS2005ImageLibrary\VS2005ImageLibrary.zip
Visual Studio 2008
...\Microsoft Visual Studio 9.0\Common7\VS2008ImageLibrary\1033\VS2008ImageLibrary.zip
Visual Studio 2010
...\Microsoft Visual Studio 10.0\Common7\VS2010ImageLibrary\1033\VS2010ImageLibrary.zip
I need to use the TextTransform tool in a standalone mode. But it doesn't want to run on machines that don't have Visual Studio installed. Has someone figured out how to do this?
If you are using this solely on a build machine, then as of Visual Studio 2010, you are licensed to copy the dlls for text templating from the GAC of a Visual Studio installed machine to the build server.
We accidentally omitted the filenames from the buildserver.txt file in Visual Studio 2010 RTM, but we've corrected that for Visual Studio 2010 SP1.
T4 isn't licensed for use on machines other than build servers that do not have Visual Studio installed.