I have a VSPackage project and I need to use clickonce to deploy it but there is no option to deploy in the solution explorer menu in VS 2008. How can I deploy the VSPackage using clickonce ?
ClickOnce is simply not a possible deployment solution for VSPackages. In Visual Studio 2010, there is the notion of a VSIX enabling simple deployment (it's basically just a zip file + metadata).
For Visual Studio 2008, you can use a '.vsi' file, but this doesn't support VSPackages (only addins).
Related
I'm using Azure devops with the VM = vmImage: 'windows-2019' and I would like to know how to generate an MSI file from my vdproj.
In my local visual studio I have the extension "Microsoft Visual Studio Installer Projects" installed and it works fine. But in the VS2019 of the hosted agent from Azure pipeline I dont have, and I can't generate the msi as an artifact.
I've tried to run by devenv.exe cmd but as I dont have the extension it didnt work.
Is there any way to generate msi files from azure pipeline? I've tried different ways, some custom tasks but it didnt work.
Or can I change my setups to another type of project that the MsBuild reconigze?
My error:
The project file "xxx.vdproj" is not supported by MSBuild and cannot be built.
Cheers.
Component.VSInstallerProjects v: 0.9.9 is now installed on the Microsoft-hosted agent 2019.
The project file "xxx.vdproj" is not supported by MSBuild and cannot
be built.
For this issue ,that because Visual Studio Installer Projects extension is not installed on the Hosted agent. You can view this link for a list of software installed on Microsoft-hosted agent2019.
As a work around , you have to configure your own build agent to run the build.
Make sure the VS Installer Projects extension is installed on your own build agent and then you can build the setup project either use command line task with "devenv" or use the "Build VS Installer" task.
To Build .msi file by VS installer project, you can use Build VS Installer task in marketplace.
You can specify to build .sln or .vdproj to generate .msi file(s) in Task-mode option.
Here are the similar cases:1,2 , you can refer to .
When trying to migrate from TFS 2010 to Visual Studio Online we are getting the error "Template Customization or Template Mismatch error". We know there have been a few customizations like adding more choices to dropdowns but don't know which ones or if there are other changes. A few people here suggested applying an uncustomized template to the projects in TFS but it's not clear which templates should be applied.
We have a project that uses the CMMI template but there are three versions of this on the TFS server - 4.0, 4.2 and 5.0. I don't see any way to tell which one was used to create the project. As a matter of fact the only reason I know it's CMMI is it errored when I created a project in Visual Studio Online with the Agile template and tried to migrate to that.
To add to the confusion, VSO only has templates with version 2013.3 so the project I'm migrating to uses the CMMI 2013.3 template. Should I add the older templates to Visual Studio Online and create my project using the same template?
Which template should I apply to the project to make it able to migrate? Should it be one of these or should I use the 2013.3 template?
Lastly, how do I get a copy of the uncustomized templates? Do I need to create a new project and export it?
Thanks,
Bill
You can use the CMMI process template from either TFS 2010, TFS 2012, or TFS 2013 with the OpsHub TFS to Visual Studio Online Migration Utility. It will attempt to move either of those three to Visual Studio Online's version of the CMMI process template.
You can use the TFS Team Project Manager on CodePlex to help you in comparing your team project's process template with a baseline CMMI process template to help you find the differences. You can create a default CMMI team project on a new TFS server and compare against your current team project.
I have been working on a Visual Studio solution template to be used internally and have been developing this in a Visual Studio 2012 Addin.
The addin is added to the tools menu of Visual Studio and all works fine.
The only question now is, how can I share this tool between my team?
I have added a VSIX project, which in turn references the Solution Template project (added as an asset) but will this alone do it?
I can't see how installing the VSIX I created is manually going to add my add-in to the Visual Studio Tools window.
Can anyone offer any advice as to how I can do this or is there some other way to deploy/publish a Visual Studio addin?
I have found a tutorial which is similar, but I just want to use the VSIX to install my add-in to Visual Studio tools menu, rather than add it as a project template. I have looked around and there doesn't seem to be much information on how to deploy your addin.
It seems addins are soon to be deprecated with the next release of Visual Studio, although I have found this article on how to convert an addin to a VSPackage.
And with a VSPackage I will be able to deploy using VSIX.
There are also some tutorials on VSPackages here.
Then new Enterprise Library 6 is out and can be downloaded here. I have downloaded and extracted EnterpriseLibrary6-binaries.exe to a folder on my C: drive. The readme says this:
MICROSOFT ENTERPRISE LIBRARY 6
Summary: This package contains Enterprise Library configuration console, MSMQ distributor service, merge configuration tool and a script to download binaries for all application blocks from NuGet.
In order to get all the binaries, run the install-packages.ps1 script.
Note: For the Semantic Logging Application Block Out-of-Process service, a separate package is available for download.
I then run Powershell and run the script. I now look in the folder I extracted the .exe to and all of the binaries are there. Now, here are the instructions from the Enterprise Library 6 .chm.
To install the integrated Visual Studio configuration editor
1. On the Visual Studio Tools menu, choose Extensions and Updates.
2. In the Extensions and Updates dialog, search online for EnterpriseLibrary.config.
3. Click the Download button to download and install the Enterprise Library configuration editor.
4. Restart Visual Studio to complete the installation.
To launch and use the configuration editor from Visual Studio
1. Open a solution in Visual Studio.
2. If the solution does not contain a configuration file, add one using the Visual Studio Add menu.
3. In Solution Explorer, right-click the configuration file and then click Edit Enterprise Library V6 Configuration. This launches the integrated configuration editor or the appropriate standalone version of the configuration tool.
Step #3 is where I am stuck. I have a WCF service project with a web.config in it. I right click the web.config and I don't see a "Edit Enterprise Library V6 Configuration" context menu option.
I DO see an "Edit Server Configuration File v6". However, when I click this I get the following error.
All I'm trying to do is use the Exception Handling Application Block in my WCF service project. I've looked around the web and can't find any easy step-by-step tutorial to guide me either. Any help is greatly appreciated.
You need to set the solution property for "Enterprise Library v6 binaries path" to set to
the folder that you extracted "EnterpriseLibrary6-binaries.exe".
You can do that by clicking the solution and then pressing F4 to see the properties window, but you need to make sure that your "Enterprise Library Config tool" is v6.
http://www.microsoft.com/en-us/download/details.aspx?id=38789
The Visual Studio Gallery provides Enterprise Library 5 Config tool which is obviously the wrong Version.
I had to use NuGet to install the application block I wanted to use in the project. For me, Tools >> Library Package Manager >> Manage NuGet Packages for solution and add the appropriate EntLib 6 Exception Handling Application Block WCF Provider.
Just download Microsoft.Practices.EnterpriseLibrary.ConfigConsoleV6.vsix
from the below link and while installing provide VS2012 or Vs2013.
http://www.microsoft.com/en-us/download/details.aspx?id=38789
After installation restart Visual Studio.
You will Enterprise Library 6.0 configuration.
By default Extension and Updates in VS give 5.0 configuration we need 6.0 to work.
This is what worked for me:
Download Microsoft.Practices.EnterpriseLibrary.ConfigConsoleV6.vsix, from here and during installation, provide VS2012 or VS2013.
Then restart your VS2012/2013 and you should be good to go!
A few test scenarios have been recorded using CodedUI test template for my web application in Visual Studio 2010 beta. These run from within the Visual Studio successfully without any issues. I was looking for instructions to create a deployment package.
Configure an environment with a "standalone" MSTest
A series of new test tools is being introduced with Visual Studio 2010. Team Agents provides a very small footprint and includes MSTest (it will be installed in a Visual Studio path).
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\mstest.exe
You can copy the contents of your test project(s) bin\ directory to the machine with Team Agents installed and execute MSTest against your test container.
mstest /testcontainer:x:\test-project\automated-tests.dll"
Coded UI tests use namespaces within libraries that are part of Visual Studio e.g. Microsoft.VisualStudio.TestTools.UITesting
This is unlike UI Automation which is part of the core .NET framework e.g.
System.Windows.Automation
Therefore as I understand it you cannot package Coded UI tests to run in an environment that does not have Visual Studio installed.