What is the workflow when developing VSIX extension? Should I uninstall and install extension each time I rebuild the project, or is there any easier way to do this?
Is it possible somehow to rebuild it and see the changes without uninstalling it and installing again?
Add the solution:
Like Simon Mourier's suggestion, for the VSIX project, you don't have to uninstall it if you want to update it. It would cover the previous project automatically during you run the latest version.
Related
Our company is currently developing the Continuous Integration process in Visual Studio Team Foundation Services and we've gotten to the part where we need to replace locally saved NuGet
packages with the packages which have already been uploaded to the MyGet server (https://www.myget.org/).
We are currently investigating two things:
Is there any option in Visual Studio where the IDE detects and builds packages automatically (and that's only counting the projects in which I've done changes, not triggering the build for all of them)?
Is there a way to save the packages locally to one root folder and not in the bin folder of each project? Please bear with me if the questions are silly, I'm still new to all of this.
What is the process of swapping the locally saved packages with the MyGet packages? Is there a task which can be added in VSTS? Should a PowerShell script be written for that process?
Any guidance will be extremely appreciated.
First, the Visual Studio can’t detect and build package automatically if you’ve done changes.
Secondly, there are many ways to sync the packages, but the changes need to be pushed to server.
Publish NuGet packages to your MyGet server through NuGet push task (add it to your CI build)
Do it in MyGet build directly when code is pushed to a Git repository in VSTS: MyGet with Visual Studio Team Services
I need to downgrade NuGet Package Manager extension for Visual Studio 2015 for testing purpose. How to do this? Is there any way to download an older version of this extension and install it into Visual Studio?
This site lists all recent releases, you must install the VSIX file.
https://github.com/NuGet/Home/releases
You can usually try a variation of the link you can get from the download button from the extension's page on https://marketplace.visualstudio.com/ .
For example, at the time of this writing Failwyn/WebCompiler64 version 1.14.9.2 has an issue, so I downloaded version 1.14.8 from https://marketplace.visualstudio.com/_apis/public/gallery/publishers/Failwyn/vsextensions/WebCompiler64/1.14.8/vspackage .
An easier way to downgrade any visual studio code extension is by:
1. search for the extension in visual studio code
2. Right click on the extension you want to downgrade
3. select Install Another Version...
4. Pick the version from the list if any and install
VS Code - how to rollback extension/install specific extension version
I am trying to publish my Web App in Visual Studio Professional 2013 but getting the following error
I got the same question asked over here but no useful answer.
Can anyone please help
You probably will be using older version, that was having an issue. refer detail [here]
Install the newer web deployment tool, should work.
which .net version are you using.
check web deploy version. if vs has 2 web deploy version, the vs get confuse to take which version. If it has 2 version, just uninstall vs and then instal it along with web deploy. if the Vs has one 1 web deploy version, you uninstall and install the web deploy. It will rectify your problem i hope.
You can refer This link
Check if version 9.0.0.0 of the assembly is installed in GAC. (from the VS2013 developer command prompt) gacutil /l Microsoft.Web.Deployment. Issues like this have occurred in the past where things worked, then after installing an update (or trying to install one) then reports of missing dlls, like nuget, occur.
The usual course of action is to repair the Visual Studio installation.
There is a problem with your publish profile. Delete the pubxml file located bellow Properties folder in your project and then create a new publish profile.
I got the same problem when older project runs into the new .NET Framework, for that you have to do the following.
Right Click on your project name->select Property Pages -> Click Build from the menu-> then select Target Framework .Net framework 4.5 or your current using framework..
"Could not load file or assembly" means the required file (of that mentioned version) is not available in the assembly (nor in the registry). All you gotta to do is to ensure this same is installed properly that would allow you to proceed further. The other things to ensure is the latest framework installed on your system.
Think you have some errors happen when to install or update Visual 2013, so you can reinstall again and this error will be fixed.
i've been working on a ASP.Net mvc5 project and been using TFS as my Version control. Been going great up until now when I formated my computer to Windows 10.
I have a couple of references that didn't work, so I need to restore them.
I know I can use the following nuget command Update-Package –reinstall how ever using that doesn't work as I want it to. It does not restore all the packages such as System.Web.Mvc How can I fix this?
You need to update or re-install your .net Framework.
Does anyone have a good way to build MSI (vdproj) projects using MsBuild or Nant?
I know one answer was to install Visual Studio on the build server and just use devenv.exe to build the project, but, I prefer not to install Visual Studio on our build servers.
Short of the method you mentioned above (devenv), there is no way to do this with the current version of MSBuild.
The method the Visual Studio team uses to run their MSI builds is with Windows Installer XML. You can learn more about using WiX to deploy setup packages here.
Please note WiX doesn't support vdproj files so it means you'll be recreating your installer projects.
Edit: Looks like I was beat to the chase when grabbing my references :)
We use Wix to automate MSI builds for IronPython and IronRuby.
EDIT: to clarify, this probably means starting over from scratch when building your installer. While Wix has a mechanism to create a configuration directly from a preexisting MSI file, I've never gotten a satisfactory result from using this tool