Is there a way to tell Visual Studio that it needs to install some packages (like NetMQ) via Nuget automatically just before the first run of the project?
Visual Studio should do that by default if you're using Visual Studio 2015 and if your package is in your packages.config.
Highlighted options are available in Visual studio 2013 and 2012 as well.
Related
I am trying to build a VS 2017 solution which includes a Visual Studio Installer Project with the just released Visual Studio Pro 2019. Of course, when I tried to open the solution I got an error because there was not Visual Studio Installer project type in VS 2019. And, I cant find a place to load it from.
How do I add a Visual Studio Installer Project type in the released version of VS 2019?
Install the addin in Visual Studio 2019:
This extension provides the same functionality that currently exists
in Visual Studio 2015 for Visual Studio Installer projects. To use
this extension, you can either open the Extensions and Updates dialog,
select the online node, and search for "Visual Studio Installer
Projects Extension," or you can download directly from this page.
This extension is designed to work with Visual Studio 2017 and
Visual Studio 2019.
I have generated visual studio installer from Microsoft visual studio community version. i want to ask is there any difference of installer generated from visual studio community version and visual studio enterprise version OR visual studio ultimate version ?
The installer project extension is the same, assuming that's what you're referring to. There are no extra (or missing) features that depend on your version of Visual Studio.
I have created SSIS packages using visual studio can i open it and run the same packages on visual studio express? I have installed viual studio express 2015 and SSDT 2015 installed but in my new project template it havent show the option to create new SSIS package.
I am upgrading my project from visual studio 2010 to visual studio 2015
please tell me is there any need to upgraded the ms-build project.
Follow these steps to upgrade project created in earlier versions of VS this may help you:
In VS, on the File menu, click Open and then click Project/Solution,
Web Site, or File, depending on the kind of project you are
upgrading.
In the Open Project dialog box, select a project file, and then click
Open. If VS detects that the project or file was created in an earlier version of Visual Studio, the Visual Studio Conversion Wizard opens.
Complete the Visual Studio Conversion Wizard.
Refrence
is there any need to upgraded the ms-build project?
The answer is No. That because since start with Visual Studio 2013, Visual Studio team made a number of exciting changes to MSBuild for Visual Studio 2013. Now the 2013 version of MSBuild will ship as a part of Visual Studio instead of the .NET Framework. See this blog MSBuild is now part of Visual Studio! for more detail info.
You can find the MSBuild.exe from the directory: C:\Program Files (x86)\MSBuild\14.0\Bin
Since it ships as a part of Visual Studio 2013, just as Michael said, MSBuild upgrade should happen with the VS installation. So you do not need to upgrade the MSBuild separately.
Hope this helps.
I have a project in a solution I am working on in Visual Studio 2012, and I get this message for one of the projects: "This version of Visual Studio does not have the following project types installed, or does not support them." It is a vdproj. What does this mean and how do I resolve this problem
The correct procedure to resolve "Incompatible" issue with VDPROJ Projects coming from Visual Studio 2010 and 2015 in 2017 or 2019 is:
Enter Visual Studio .NET 2017 or 2019
2017: Click on "Tools" -> Extension and Updates -> Online
2019: Click on "Extensions" -> Manage Extensions -> Online
Type "Installer Project" on the search box
Click on "Install" in Microsoft Visual Studio Installer Project
Restart Visual Studio .NET and follow the instructions to install the extension
With this extension the old project (2010, 2015) is capable to work in (2017, 2019). VDPROJ are not deprecated, simply they are improved with a new extension, for more information about this please visit the oficial MarketPlace.
There is also the official:
Microsoft Visual Studio 2015 Installer Projects
Microsoft Visual Studio 2013 Installer Projects
Microsoft Visual Studio Installer Projects (2017 & 2019)
Microsoft Visual Studio 2022 Installer Projects
if you can jump to VS 2013, 2015, 2017+2019, or 2022
But BozoJoe is right, its time to drop vdproj and move on to WiX.
vdproj is a MSI creation project for Visual Studio. Its been deprecated and most people have moved on to either WIX or NSIS or a professional grade installer creation tools such as Install Shield.
If you do not require an installer for your product just exclude the vdproj project from the solution and continue with your life
for fun if you want to try to transition right away to wix, try this powershell script https://github.com/chrisoldwood/vdproj2wix
Visual Studio 2017 can use the Visual Studio Installer. It is NOT a default. You have to run InstallerProjects.vsix. You can get it at Microsoft Visual Studio 2017 Installer Projects. I have used it and worked great, at least for a windows GUI project. It's worth a shot before you get into the Install Shield intricacies.
if You use Microsoft Visual Studio Installer Project (Vs2017).
Microsoft Visual Studio Installer Project may be disabled after an update.
Tools -> Extensions and Updates..
Click Installed
Find and Select -> Microsoft Visual Studio Installer Project
do Enable
Restart Visual Studio