What is Microsoft.VisualStudio.Azure.Containers.Tools.Targets package? - azure

When I create a project in .NET Core 2.1. These is the package Microsoft.VisualStudio.Azure.Containers.Tools.Targets is already included in my project. I can't find any documents for that.
Can anyone tell me what is it?
Thanks in advance.

Microsoft.VisualStudio.Azure.Containers.Tools.Targets package is added in VS2017 when Docker Support is selected for the project. It enabled Visual Studio Tooling for Docker file.
Removing this package may give you errors if you intend to Dockerize your project/application in Visual Studio 2017.

Related

How to create nuget package for xamarin.ios

I have created a Xamarin.iOS UI component without core project, only a Xamarin.iOS project, and I would like to package it with nuget which I can use across several projects. But I can't handle it.
I'm looking for proper steps for creating a Nuget Package based on my Xamarin solution.
The only thing I found is this command line nuget pack your.nuspec.
Obviously I'm on mac.
Thank's
Anthony;
Easiest way to make a nuget for ios - Visual studio for Mac.
Open project settings in ios settings page and enable "create package when building the project".
Then go to the Metadata and fill it. After that choose release mode and build, and finally check output directory(yourprojectname/bin/release).

Opening Azure DataFactory Projects in VS2015

I am working on a solution that apparently was created in VS2013. I have VS2015 installed. There are a number of .dfproj files included in the solution. When I attempt to load the solution it tells me that .dfproj files are unsupported. I have the latest Azure SDK installed. I also located a download for the "Azure Data Factory Visual Studio Tools", however when I attempt to install it, it tells that it is incompatible with VS2015. I have been unable to locate a version of those tools intended for 2015. If someone could point me in the right direction to solve this dilemma, I would be greatly appreciative.
I hope, I am not too late to answer your question.(almost two years)..
I faced similar issue as you mentioned in question. In my case I was unable to open .dfproj file. I downloaded Microsoft Azure DataFactory Tools for Visual Studio 2015 from Microsoft market place. Installed it to my machine. Now .dfproj file is loading.
Microsoft VS Professional 2015
VS2015 version: 14.0.25431 update 3

Visual Studio 2015 can't start IIS Express

When I am trying to run an ASP.Net Core project in Visual Studio 2015, a Microsoft Visual Studio dialog appears "The project doesn't know how to run the profile IIS Express".
Does anyone know anything about this message, or how to fix it? I've searched Google and the MSDN. There's nothing in the build logs, or the Windows event log.
This dialog showed up for me when I had migrated a project from dotnet RC1 to RC2.
Before the fix I could still run it using dotnet run and from Visual Studio choosing the profile other than "IIS Express".
I had misread this guide and forgot the .Web
\DNX\Microsoft.DNX.targets –> \DotNet.Web\Microsoft.DotNet.Web.targets
After fixing this and restarting Visual Studio(not sure if needed) I could run the project using the IIS Express profile.
Should also be noted that as per the comments, adding .Web in the top level node is required in the xproj. <Project Sdk="Microsoft.NET.Sdk"> should be <Project Sdk="Microsoft.NET.Sdk.Web">.
In my case the issue was solved after added the ASP.NET and web development tool extension to my VS instalation.
To clarify the answer from hultqvist, it is a problem with the xproj. To fix it, edit the xproj directly and change this
<Import Project="$(VSToolsPath)\DotNet\Microsoft.DotNet.targets"
Condition="'$(VSToolsPath)' != ''" />
to this
<Import Project="$(VSToolsPath)\DotNet.Web\Microsoft.DotNet.Web.targets"
Condition="'$(VSToolsPath)' != ''" />
That is, insert Web twice.
There is an associated issue in the aspnet tooling repo.
I had the same issue and found a very simple solution for Visual Studio 2017. In Visual Studio 2017 go to Solution Explorer then right click on your project file. In the menu you will see "Set as StartUp Project". If you can select it then select it. Now run your project again.
I had a similar issue but with "MyProjectName" instead of IIS Express.
In my case, I was trying to start as a standalone application, so I cleaned the launchSettings.json
I inadvertently changed the "commandName" parameter from "Project" to "MyProjectName" and that caused the popup to show up.
Resetting it back to "Project" solved my issue, silly me 😁
I had a similar issue, In my case ASP.NET and web development is enabled but Development time IIS support is not checked in the optional sections.
Once I enable the Development time IIS support solved my issue.
You can get this error with RTM if <BaseIntermediateOutputPath gets corrupted or is incorrect in your .xproj file.
I had this same issue and after digging around for a while I discovered that I had dotnet preview v1.0.0-preview2 installed under Programs Files (x86) and a non-preview version in x64. I think VS is launching the x86 (preview) version but expecting to see the full version. To fix this, I did the following.
from programs and feature uninstall every visible dotnet core. (note: this did not remove the x86 preview)
go to https://www.microsoft.com/net/download/core#/sdk and install BOTH x86 and x64 SDK packages
open command line and from the root directory check run: dotnet --version (at the time of writting it was 1.0.4
fire up .net core project in VS 2017 and run.
When I did all of the above, I was able to start up the site in IIS Express from VS.
This happened to me after a failed update of visual studio 2017 15.9.4
Setup completed with warnings and when I checked the problems saw that .NET core SDK 2.1 installation is failed.
I will try to install it manually.
Otherwise currently the only solution I found is to uninstall visual studio and re-install it.
In visual Studio 2017, i fixed this error by doing the following two steps.
I went to add or remove a program in windows, and deleted everything ending with ".net". I then reinstalled them in the visual studio installer. Then loading the project again produced a new error, which condiosluzverde provided the solution to here:
How Can I Fix the Microsoft Visual Studio Error: "Package Did Not Load Correctly"?
Same thing happened to me, my project was working fine. I didn't do any RC1 to RC2 update & this popup appeared from nowhere.
I fixed the problem by updating visual studio. You can also consider repairing VS.

I cannot see all versions of a NuGet Pacakge

I am doing some investigation of NuGet to determine if I can use it to distribute various software components. All of these components are C++ based so I'm using CoApp PowerShell Tools to create the NuGet package files. I have placed these .nupkg files on a network folder for distribution. However, when accessing the packages via Visual Studio 2012, I can only see the latest version. Is there a way to view all of the versions of a particular package?
Here is the network folder:
Here is what I see in Visual Studio 2012:
You're supposed to only see the latest version. If you want to install a specific version, you'll have to use the Package Manager Console.
Install-Package SYS_STANDARDS -Version 1.3.1.0
If that isn't acceptable for your requirements, then Nuget isn't the best way to distribute your code.
Newer versions of Visual Studio have a drop down menu that can be opened to view and select different versions of a package

Android studio doesn't create project structure

I am new to Android studio. I tried to create my first project and there is no project structure only gradle files. What am I doing wrong? I keep getting these files with creation of another new project.
Update SDK via Android SDK Manager. You need all packages in Tools to be installed.
But even after doing so, I can't make it to auto generate resources. So I continue to deal with it...
I found what was my problem. I updated Android studio from version 1.x to 2.x. On official site is written that if you try to install version 2.x into same location Android studio might not work properly and there could be some unexpected behavior.
So just removing Android studio and then reinstaling it, worked perfectly.

Resources