There is VSCommands add-in which allow you to configure dependant files directly from IDE Link updated, previous was http://mokosh.co.uk/vscommands FYI: When VSCommands is installed, just select all the files you want to be Dependant and the root file, then Right Click -> Group Items… and VSCommands will ask which of the files you would like … Read more
I think the problem is that your XML file has a default namespace xmlns=”http://schemas.microsoft.com/developer/msbuild/2003″. This causes problems with XPath. So you XPath //ProjectReference will return 0 nodes. There are two ways to solve this: Use a namespace manager. Use namespace agnostic XPath. Here’s is how you could use a namespace manager: $nsmgr = New-Object System.Xml.XmlNamespaceManager … Read more
I’m editing my answer to make it clear that you don’t need to upgrade your .csproj file. As Drew commented below there are benefits to doing so. However, VS2017 will continue to work with the classic csproj file just fine. In addition there is nothing in VS2017 that will perform the upgrade for you. If … Read more
The simplest way since only ONE HintPath can be used is to use the all-so-nice Condition attribute like this: <Reference Include=”TheAssembly”> <HintPath Condition=”Exists(‘..\My\Assembly\Path’)”>..\My\Assembly\Path\TheAssembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\My\Assembly\Path’)”>..\..\My\Assembly\Path\TheAssembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\..\My\Assembly\Path’)”>..\..\..\My\Assembly\Path\TheAssembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\..\..\My\Assembly\Path’)”>..\..\..\..\My\Assembly\Path\TheAssembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\..\..\..\My\Assembly\Path’)”>..\..\..\..\..\My\Assembly\Path\TheAssembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\..\..\..\..\My\Assembly\Path’)”>..\..\..\..\..\..\My\Assembly\Path\TheAssembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\..\..\..\..\..\My\Assembly\Path’)”>..\..\..\..\..\..\..\My\Assembly\Path\TheAssembly.dll</HintPath> etc… </Reference> So the answer to the question would be this: <Reference Include=”assembly”> <HintPath Condition=”Exists(‘..\..\csharp\bin’)”>..\..\csharp\bin\assembly.dll</HintPath> <HintPath Condition=”Exists(‘..\..\..\..\foo\sdk\csharp\bin’)”>..\..\..\..\foo\sdk\csharp\bin\assembly.dll</HintPath> </Reference> If multiple … Read more
In my case, the tools folder didn’t exist inside %USERPROFILE%\.dotnet\ so I had to run the command dotnet tool install –global dotnet-ef to install dotnet ef. Then I was able to run dotnet ef… This was the result of the above install command:
The CSPROJ file, saved in XML format, stores all the references for your project including your compilation options. There is also an SLN file, which stores information about projects that make up your solution. If you are using Visual Studio and you have the need to view or edit your CSPROJ file, while in Visual … Read more
Here’s a list of project type GUIDs: 8BB2217D-0F2D-49D1-97BC-3654ED321F3B ASP.NET 5 603C0E0B-DB56-11DC-BE95-000D561079B0 ASP.NET MVC 1 F85E285D-A4E0-4152-9332-AB1D724D3325 ASP.NET MVC 2 E53F8FEA-EAE0-44A6-8774-FFD645390401 ASP.NET MVC 3 E3E379DF-F4C6-4180-9B81-6769533ABE47 ASP.NET MVC 4 349C5851-65DF-11DA-9384-00065B846F21 ASP.NET MVC 5 / Web Application FAE04EC0-301F-11D3-BF4B-00C04F79EFBC C# 9A19103F-16F7-4668-BE54-9A1E7A4F7556 C# (forces use of SDK project system) 8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942 C++ 13B669BE-BB05-4DDF-9536-439F39A36129 CPS barebones project A9ACE9BB-CECE-4E62-9AA4-C7E7C5BD2124 Database 4F174C21-8C12-11D0-8340-0000F80270F8 Database C8D11400-126E-41CD-887F-60BD40844F9E Database … Read more
I believe @Dmytrii gets it right on one hand – you want to use the “link” feature. However, he’s only partly correct when saying you can’t link to a directory tree. While this is, indeed, true when trying to add the links using Visual Studio’s GUI, MSBuild supports this. If you want to preserve the … Read more
You need to manually edit the project file and add s to the default TargetFramework and basically change it to TargetFrameworks. Then you mention the Moniker with a ; separator. Also you can put the Nuget package references in a conditional ItemGroup manually or using VS Nuget Package Manager. Here is what your .csproj should … Read more
Old thread, I know, but I found a way to do this that I keep forgetting, and on my search to find it one last time, I stumbled upon this question. The best way I’ve found to this is is to use the BeforeBuild target in the .csproj file. <Target Name=”BeforeBuild”> <ItemGroup> <Content Include=”**\*.less” /> … Read more