Every time I start a new MVC project in Visual Studio, I have to update my Nuget packages. Things are several versions behind. I'm regularly updating my Visual Studio to stay current there, but how do I make sure my packages are up to date in new framework?
If needed, running Visual Studio 2017 Enterprise
What update of Visual Studio 2017 are you on?
How about modifying the inbuilt templates?
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\ItemTemplates\Web\CSharp\1033
Related
When I try to install the Monogame extension into Visual Studio 2022, it straight up does not show with the right extension.
it is not listed on the extension list:
(image of list)
i have the .NET framework installed into visual studio, (but I did that after installing the actual vs program)
does anyone have any idea why this is happening?
MonoGame 3.8.1 is out and is compatible with Visual Studio 2022!
https://community.monogame.net/t/monogame-3-8-1/17786
I have installed Visual Studio 2019 community version, but it is somehow in a conflict with Visual Studio Code. When I open the Developer PowerShell in Studio 2019, direct to a project folder and enter "code .", the projects gets opened in Visual Studio Code. How can I set-up Visual Studio 2019 as default program? I know how to do it for certain file-formats, but not for project folders as a whole.
Thanks!
Visual Studio 2017 comes with Nuget 4.0.0. However, it's not placed on the path. Where can I find the nuget executable to use the CLI?
Visual Studio 2017 doesn't use NuGet.exe but instead uses an extension of NuGet to achieve this. You should be able to find the extension in this path:
C:\Program Files (x86)\Microsoft Visual Studio\2017\<VSEdition>\Common7\IDE\CommonExtensions\Microsoft\NuGet
... where <VSEdition> is the version of Visual Studio being used, for example Community or Enterprise.
If you want to use the CLI, you'll have to download it separately. Here is a link explaining the same.
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.
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.