visualstudio-docs | official Visual Studio | Code Editor library
kandi X-RAY | visualstudio-docs Summary
kandi X-RAY | visualstudio-docs Summary
This repo is the home of the official Visual Studio, Visual Studio for Mac, Visual Studio Subscriptions, and Scripting Technologies documentation for Microsoft.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Main entry point .
visualstudio-docs Key Features
visualstudio-docs Examples and Code Snippets
Community Discussions
Trending Discussions on visualstudio-docs
QUESTION
I would like to use the best security coding practices in a VSTO
Addin project I am implementing for Microsoft Outlook
application and I have a question regarding code signing.
Following the creation of a code signing certificate (.pfx), I have successfully signed:
a) the DLL files produced by my project via using Visual Studio post-build event parameters.
b) the EXE & MSI installers using the SignTool
command-line tool.
c) <"filename">.vsto and <"filename">.dll.manifest files
My question is that I used mage
tool (Manifest Generation and Editing Tool) to sign the <"filename">.VSTO and <"filename">.dll.manifest files via the following commands - according to Microsoft:
ANSWER
Answered 2021-Jan-31 at 02:28You can see digital signature in Windows Explorer only for the executable (dll and exe) files.
VSTO is a text file (try to open it in Notepad).
QUESTION
I am attempting to update a Visual Studio extension to be compatible for installation in Visual Studio 2017. I have followed the steps and notes in each of the following pages (and others I've searched):
- https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/extensibility/faq-2017.md#can-i-build-a-vsix-v3-with-visual-studio-2015
- http://www.visualstudioextensibility.com/2017/01/10/its-time-to-change-the-vsix-manifest-of-your-extension-to-v3-for-visual-studio-2017-compatibility/
I originally encountered a separate issue noted in this post, which has been resolved. Now, the project (and extension) continue to build successfully locally, but it is failing on our TFS build server with the following error:
...ANSWER
Answered 2018-Dec-11 at 02:15Error VSSDK1001: Unable to find Microsoft.VisualStudio.CommandTable.VSCTCompiler type
You should add a nuget restore task before you build task in your TFS definition.
When you build in the local via Visual Studio, Visual Studio have two options to restore nuget packages automatically when we build the project:
But, when you build on the TFS server, there is no such options to restore those nuget packages automatically. So we need add a task nuget restore before we build the project/solution:
Add a task, search nuget and add it into the agent job, select restore in the Command:
Configure this nuget restore task correctly and set it before your build task.
Note: You can also add a NuGet Tool Installer
task to specific version of NuGet.
Hope this helps.
QUESTION
The documentation of Visual Studio Extensions says that I can apply conditionals for the elements inside the vsct
file.
I've been trying to build different menus for VS2019 and another one to the others. I've created a conditional compiltaion symbol which defines VS2019
for Visual Studio 2019+.
ANSWER
Answered 2019-Jun-26 at 03:49The .VSCT file is compiled down to a binary command table output (.cto) resource, which is then embedded into your package assembly as a resource. This .cto resource is compiled at build time, with the conditionals being evaluated when the .cto resource is built.
Because your menu group is defined when you built the package, your menu group looks to be parented based upon which version of VS you built it with.
Sincerely,
QUESTION
I want find some way to let custom task pane get current inspector. what method should I use?
I build a VSTO Outlook C# add in by follow this Link: Walkthrough: Display custom task panes with email messages in Outlook
I insert a button on the task pane. Now I want to use this button to insert a mail title like "test for button" by action Button_Click
I try to use Outlook.Inspector inspector = Globals.ThisAddIn.Application.ActiveInspector();
OrOutlook.MailItem mailItem = Inspector.CurrentItem as Outlook.MailItem;
to get current inspector but seems not work.
Here is my code below:
...ANSWER
Answered 2019-Apr-04 at 01:10John Hart@GitHub answered my question. Here is his code below:
QUESTION
I'm trying to use the Globals class in a Console Application.According to MSDN documentation,Globals is a class that Visual Studio automatically generates when you create an Office project.My question,can I use this class in a Console Application?I added references to Interop and Microsoft Office but I still cannot access the class.
Here is the link: https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/vsto/global-access-to-objects-in-office-projects.md
...ANSWER
Answered 2019-Feb-23 at 17:36The documentation to which you link is for Visual Studio Tools for Office (VSTO) - a special library that runs in-process in an Office application. These namespaces cannot be used in Console or WinForms applications, only in Office Add-ins or document-level customizations.
Note that the documents on GitHub are the same as what is found on docs.microsoft.com, but with less "context". For information purposes it's better to use "docs" and not GitHub.
QUESTION
I am attempting to update a Visual Studio extension to be compatible for installation in Visual Studio 2017. I have followed the steps and notes in each of the following pages (and others I've searched):
- https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/extensibility/faq-2017.md#can-i-build-a-vsix-v3-with-visual-studio-2015
- http://www.visualstudioextensibility.com/2017/01/10/its-time-to-change-the-vsix-manifest-of-your-extension-to-v3-for-visual-studio-2017-compatibility/
In the end, the project (and extension) will build successfully locally, but it is failing on our TFS build server with the following error:
...ANSWER
Answered 2018-Dec-07 at 23:13If you have it working locally, just create a new project on TFS and transfer it, any missing packages will be re-stored when you open the project after you map it in you computer.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install visualstudio-docs
You can use visualstudio-docs like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page