The solution is to use `AppendTargetFrameworkToOutputPath` https://www.tabsoverspaces.com/233608-stopping-msbuild-appending-targetframework-to-outputpath/

    &lt;AppendTargetFrameworkToOutputPath&gt;false&lt;/AppendTargetFrameworkToOutputPath&gt;

The answer above is right, but you may also want to remove the runtime identifier:

    &lt;AppendTargetFrameworkToOutputPath&gt;false&lt;/AppendTargetFrameworkToOutputPath&gt;
    &lt;AppendRuntimeIdentifierToOutputPath&gt;false&lt;/AppendRuntimeIdentifierToOutputPath&gt;



I have a text file that I want to read. I want to know if one of the lines contains `[` so I tried :

    if(array[i] == &quot;[&quot;)

But this isn&#39;t working.

How can I check if a string contains a certain character?

How to check if a string contains a char?

I have a query like this (simplified):

&lt;!-- language-all: lang-javascript --&gt;

    db.collection.aggregate([
      { $match: { main_id: ObjectId(&quot;58f0f67f50c6af16709fd2c7&quot;) } }, 
      {
        $group: {
          _id: &quot;$name&quot;,
          count: { $sum: 1 },
          sum: { $sum: { $add: [&quot;$P31&quot;, &quot;$P32&quot;] } }
        }
      }
    ])

I do this query from Java, and I want to map it on my class, but I don&#39;t want `_id` to be mapped on `name` field. Because if I do something like this:

&lt;!-- language-all: lang-java --&gt;

    @JsonProperty(&quot;_id&quot;)
    private String name;

then when I save this data back to mongo (after some modification) the data is saved with name as `_id` while I want a real Id to be generated.

So, how can I **rename** `_id` after `$group` operation?


Is it possible to rename _id field after mongo&#39;s group aggregation?

Setting `OutputPath` in the new Visual Studio 2017 project format automatically adds the target framework in the path. For example, if I have these set in the project file:

    &lt;TargetFramework&gt;net462&lt;/TargetFramework&gt;
    &lt;OutputPath&gt;/build/debug/&lt;OutputPath&gt;

The actual output folder will resolve to `/build/debug/net462/`, not `/build/debug/` like in the older versions.
How do I solve this without workarounds like moving things around with post build actions?




How do I set `OutputPath` in a Visual Studio 2017 project (new .csproj file format) without the target framework cluttering the resolved path?

Setting <code>OutputPath</code> in the new Visual Studio 2017 project format automatically adds the target framework in the path. For example, if I have these set in the project file:
<pre><code class="hljs language-php-template">&#x3C;TargetFramework>net462&#x3C;/TargetFramework>
&#x3C;OutputPath>/build/debug/&#x3C;OutputPath>
</code></pre>
The actual output folder will resolve to <code>/build/debug/net462/</code>, not <code>/build/debug/</code> like in the older versions.
How do I solve this without workarounds like moving things around with post build actions?

I&#39;m trying to filter on the initial query. I have nested include leafs off a model. I&#39;m trying to filter based on a property on one of the includes. For example:

```cs
using (var context = new BloggingContext())
{
    var blogs = context.Blogs
        .Include(blog =&gt; blog.Posts)
            .ThenInclude(post =&gt; post.Author)
        .ToList();
}
```

How can I also say `.Where(w =&gt; w.post.Author == &quot;me&quot;)`?

Filtering on Include in EF Core

I use api controller in ASP.net web API and i need to pass value to post method by [FromBody] type..

     [HttpPost]
     public HttpResponseMessage Post( [FromBody]string name)
     {
         ....
     }
i use &lt;b&gt;Postman&lt;/b&gt; plugin but when send to post method value of &lt;b&gt;name&lt;/b&gt; always is &lt;b&gt;null&lt;/b&gt;.. follow this image:
[![enter image description here][1]][1]


and in Post methods :
[![enter image description here][2]][2]


  [1]: https://i.stack.imgur.com/1X3Ce.png
  [2]: https://i.stack.imgur.com/rYdcI.png

why this happend?!

Null value when Pass values [FromBody] to post method by Postman plugin

My project has a folder structure to the tune of:
 
* Project,
* Project/data
* Project/Engine
* Project/Server
* project/front-end

In the server (running in the Project/Server folder) I refer to the folder like this:

    var rootFolder = Directory.GetCurrentDirectory();
    rootFolder = rootFolder.Substring(0,
                rootFolder.IndexOf(@&quot;\Project\&quot;, StringComparison.Ordinal) + @&quot;\Project\&quot;.Length);
    PathToData = Path.GetFullPath(Path.Combine(rootFolder, &quot;Data&quot;));

    var Parser = Parser();
    var d = new FileStream(Path.Combine(PathToData, $&quot;{dataFileName}.txt&quot;), FileMode.Open);
    var fs = new StreamReader(d, Encoding.UTF8);
          
On my windows machine this code works fine since `Directory.GetCurrentDirectory()` reffered to the current folder, and doing

    rootFolder.Substring(0, rootFolder.IndexOf(@&quot;\Project\&quot;, StringComparison.Ordinal) + @&quot;\Project\&quot;.Length); 

gets me the root folder of the project (not the bin or debug folders). 
But when I ran it on a mac it got &quot;`Directory.GetCurrentDirectory()`&quot; sent me to /usr/&lt;username&gt;/[something else]. It didn&#39;t refer to the folder where my project lies.

What is the correct way to find relative paths in my project? Where should I store the data folder in a way that it is easily accessible to all the sub projects in the solution - specifically to the kestrel server project? I prefer to not have to store it in the wwwroot folder because the data folder is maintained by a different member in the team, and I just want to access the latest version. What are my options?

How to get root directory of project in asp.net core. Directory.GetCurrentDirectory() doesn&#39;t seem to work correctly on a mac

I have two format of JSON which I want to Deserialize to one class.
I know we can&#39;t apply two `[JsonProperty]` attribute to one property.

Can you please suggest me a way to achieve this?

    string json1 = @&quot;
        {
            &#39;field1&#39;: &#39;123456789012345&#39;,
            &#39;specifications&#39;: {
                &#39;name1&#39;: &#39;HFE&#39;
            }
        }&quot;;

    string json2 = @&quot;
        {
            &#39;field1&#39;: &#39;123456789012345&#39;,
            &#39;specifications&#39;: {
                &#39;name2&#39;: &#39;HFE&#39;
            }
        }&quot;;

    public class Specifications
    {
        [JsonProperty(&quot;name1&quot;)]
        public string CodeModel { get; set; }
    }

    public class ClassToDeserialize
    {
        [JsonProperty(&quot;field1&quot;)]
        public string Vin { get; set; }

        [JsonProperty(&quot;specification&quot;)]
        public Specifications Specifications { get; set; }        
    }



I want `name1` and `name2` both to be deserialize to `name1` property of specification class.


multiple JsonProperty Name assigned to single property

I&#39;m trying to write a plugin system with .NET Core, and one of my requirements are to be able to distribute the plugin DLL along with its dependencies to the user for install.

However, I can&#39;t figure out how to include my NuGet dependencies as a build artifact and have them output to the build folder, without having to use `dotnet publish` as a hack. Is there some way I can specify this in the .csproj file (project file)?


How do I get .NET Core projects to copy NuGet references to the build output?

In &quot;old school&quot; MSBuild projects - as still used by Windows Forms in VS2017 for example - files could be &quot;nested&quot; via a `DependentUpon` item in the csproj file.

I used this to group unit tests together in Noda Time, e.g.

    &lt;Compile Include=&quot;LocalDateTest.PeriodArithmetic.cs&quot;&gt;
      &lt;DependentUpon&gt;LocalDateTest.cs&lt;/DependentUpon&gt;
    &lt;/Compile&gt;

That led to easily-navigable tests:

[![Nested tests][1]][1]

I knowingly &quot;lost&quot; this feature when moving to `project.json` for .NET Core, but had hoped it would return when converting to MSBuild. However, it looks like MSBuild projects based on the .NET Core SDK (root element `&lt;Project Sdk=&quot;Microsoft.NET.Sdk&quot;&gt;`) don&#39;t get the same treatment in Visual Studio 2017, even if an `ItemGroup` is added manually with the same elements as the &quot;old school&quot; project.

ASP.NET Core projects receive automatic nesting for minified CSS and Javascript, but it&#39;s not clear how to apply that to C# in .NET Core library projects.


  [1]: https://i.stack.imgur.com/mXuFy.png

Can files be nested in VS2017 Solution Explorer for .NET Core (non-ASP.NET Core) projects?

I&#39;m  trying to upgrade our buildserver (jenkins) from Visual Studio 2015 to 2017. We&#39;re building via MS-Build. I&#39;ve downloaded and installed MS-Buld tools as described in this [answer][1]. If I compile my projects I get an error that `Microsoft.WebApplication.targets` was not found.

Detailed error:

     error MSB4226: The imported project &quot;C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications\Microsoft.WebApplication.targets&quot;


I performed a find in the MS-Build directory:

&lt;!-- begin snippet: js hide: false console: true babel: false --&gt;

&lt;!-- language: lang-js --&gt;

    PS C:\Program Files (x86)\MSBuild&gt; dir -Recurse -Filter &quot;Microsoft.WebApplication.targets&quot;


        Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\WebApplications


    Mode                LastWriteTime         Length Name                                                                                                                                                                                                            
    ----                -------------         ------ ----                                                                                                                                                                                                            
    -a----       11.01.2012     00:23          19654 Microsoft.WebApplication.targets                                                                                                                                                                                


        Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\WebApplications


    Mode                LastWriteTime         Length Name                                                                                                                                                                                                            
    ----                -------------         ------ ----                                                                                                                                                                                                            
    -a----       22.07.2013     01:25          19995 Microsoft.WebApplication.targets                                                                                                                                                                                


        Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications


    Mode                LastWriteTime         Length Name                                                                                                                                                                                                            
    ----                -------------         ------ ----                                                                                                                                                                                                            
    -a----       06.07.2015     21:55          20118 Microsoft.WebApplication.targets                                                                                                                                                                                


        Directory: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\WebApplications


    Mode                LastWriteTime         Length Name                                                                                                                                                                                                            
    ----                -------------         ------ ----                                                                                                                                                                                                            
    -a----       22.07.2013     01:25          19995 Microsoft.WebApplication.targets

&lt;!-- end snippet --&gt;


As can be seen the file exists for old compiler versions, but for v15.0 it is missing. 

I also have installed Visual Studio 2017 on the build-server. The project succeeds to build if I compile with Visual Studio 2017.

Any hints how to solve this problem? One possible solution is to generate a symbolic link from `C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v15.0\WebApplications` point to the old v14.0 files (located under `C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\WebApplications`).

Thx

  [1]: https://stackoverflow.com/questions/42696948/how-can-i-install-the-vs2017-version-of-msbuild-on-a-build-server-without-instal

MS-Build 2017 &quot;Microsoft.WebApplication.targets &quot; is missing

I&#39;m trying to set up a build server for .NET, but can&#39;t figure out where MSBuild.exe is installed.

I&#39;m trying to install MSBuild using the Microsoft Build Tools 2013:
https://www.microsoft.com/en-us/download/details.aspx?id=40760

Where is MSBuild.exe installed in Windows when installed using BuildTools_Full.exe?

I have an ASP.NET Core project that builds properly with Visual Studio, but it doesn&#39;t build under MSBuild.

It doesn&#39;t find all the common libraries (system, etc.).

I&#39;m using TeamCity and part of the build process is a `nuget restore`.

I tried to do the same steps as TeamCity, but manually with MSBuild, and it failed, not finding the libraries.

I added a `dotnet restore` step and then it worked.

So, what is the difference between a `nuget restore` and a `dotnet restore`?


&#39;dotnet restore&#39; vs. &#39;nuget restore&#39; with TeamCity

I just installed Windows 10 Creators Update (version 10.0.15063).

I have multiple versions of Visual Studio installed (2012, 2013, 2015 and 2017). I installed VS 2017 only a couple weeks ago.

### Problem

CMake (version 3.8.1) no longer finds the C/C++ compiler when run inside a &quot;VS2015 x64 Native Command Prompt&quot; (it _does_ work properly when run inside a VS 2017 command prompt).

### Reproduction

Content of `CMakeLists.txt`:

&lt;!-- language: lang-none --&gt;

    project (test)
    add_executable (test test.cpp)

(Content of `test.cpp` is irrelevant.)

CMake invocation, in a VS2015 x64 Native Command Prompt:

&lt;!-- language: lang-none --&gt;

    &gt; mkdir build
    &gt; cd build
    &gt; cmake -G &quot;Visual Studio 14 2015 Win64&quot; ..

CMake output:

&lt;!-- language: lang-none --&gt;

    -- The C compiler identification is unknown
    -- The CXX compiler identification is unknown
    CMake Error at CMakeLists.txt:1 (project):
      No CMAKE_C_COMPILER could be found.

    CMake Error at CMakeLists.txt:1 (project):
      No CMAKE_CXX_COMPILER could be found.

    -- Configuring incomplete, errors occurred!
    See also &quot;D:/dev/cmaketest/build/CMakeFiles/CMakeOutput.log&quot;.
    See also &quot;D:/dev/cmaketest/build/CMakeFiles/CMakeError.log&quot;.

### Analysis

The reason of the failure is clear when looking at `CMakeFiles/CMakeError.log`:

&lt;!-- language: lang-none --&gt;

    ClCompile:
      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\CL.exe /c /nologo /W0 /WX- /Od /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo&quot;Debug\\&quot; /Fd&quot;Debug\vc140.pdb&quot; /Gd /TC /errorReport:queue CMakeCCompilerId.c
      CMakeCCompilerId.c
    Link:
      C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\x86_amd64\link.exe /ERRORREPORT:QUEUE /OUT:&quot;.\CompilerIdC.exe&quot; /INCREMENTAL:NO /NOLOGO kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /MANIFEST /MANIFESTUAC:&quot;level=&#39;asInvoker&#39; uiAccess=&#39;false&#39;&quot; /manifest:embed /PDB:&quot;.\CompilerIdC.pdb&quot; /SUBSYSTEM:CONSOLE /TLBID:1 /DYNAMICBASE /NXCOMPAT /IMPLIB:&quot;.\CompilerIdC.lib&quot; /MACHINE:X64 Debug\CMakeCCompilerId.obj
    LINK : fatal error LNK1158: cannot run &#39;rc.exe&#39; [D:\dev\cmaketest\build\CMakeFiles\3.8.1\CompilerIdC\CompilerIdC.vcxproj]

`rc.exe` (Resource Compiler) is not found. Indeed, in the same VS 2015 command prompt:

&lt;!-- language: lang-none --&gt;

    &gt; where rc.exe
    INFO: Could not find files for the given pattern(s).

While it _is_ found in a VS 2013 command prompt:

&lt;!-- language: lang-none --&gt;

    &gt; where rc.exe
    C:\Program Files (x86)\Windows Kits\8.1\bin\x64\rc.exe
    C:\Program Files (x86)\Windows Kits\8.1\bin\x86\rc.exe

and a VS 2017 command prompt:

&lt;!-- language: lang-none --&gt;

    &gt; where rc.exe
    C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64\rc.exe

Checking the content of the `PATH` environment variables in various VS command prompts:

- Inside a VS 2013 command prompt, `PATH` contains

    &lt;!-- language: lang-none --&gt;

        C:\Program Files (x86)\Windows Kits\8.1\bin\x64

- Inside a VS 2017 command prompt, `PATH` contains

    &lt;!-- language: lang-none --&gt;

        C:\Program Files (x86)\Windows Kits\10\bin\x64
        C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\x64

- But inside a VS 2015 command prompt, `PATH` only contains

    &lt;!-- language: lang-none --&gt;

        C:\Program Files (x86)\Windows Kits\10\bin\x64

  which does not contain `rc.exe`.

### Questions

1. Is this a known issue or is it specific to my system?

2. What could Windows 10 Creators Update possibly install, uninstall or alter in the system (perhaps something related to Windows SDKs) that would trigger this problem?

3. What is a clean way to resolve this?

Edit: Installed VS 2017 components:

[![VS 2017 components installed][1]][1]


  [1]: https://i.stack.imgur.com/SqSCn.png

rc.exe no longer found in VS 2015 Command Prompt

Does anyone know of a sanctioned way to update Node within Visual Studio 2017? I&#39;ve got Node 6 set up on my development PC but VS2017 appears to come with a bundled copy of Node 5, which means that running ```npm install``` on my command line sets up various packages like ```node-sass``` with bindings for Node 6, so when I then run gulp tasks from the VS Task Runner things fall over due to the mismatched versions. 

I found the VS Node install at ```C:\Program Files (x86)\Microsoft Visual Studio 14.0\Web\External``` but I&#39;m a little reluctant to just hack about and replace it. Anyone got any experience of upgrading this? I know I can sync by downgrading the version on my PC but that seems backwards. 

Update Node Version in Visual Studio 2017

If I set environment variables for a .Net Core web project in Visual Studio 2017 using the project properties page, I can read the value of the variable using `Environment.GetEnvironmentVariable`; however, when I set the environment variable for my xUnit testing project and then debug the test, `Environment.GetEnvironmentVariable` always returns null.  Is there something about the fact that it is a testing project that should prevent the variable from being used the same as with the web project?  If so, is there a way that I can set the environment variables for a test project?  Thank you.

Should GetEnvironmentVariable Work in xUnit Test?

I have a dotnet core app that is targetting Microsoft.NETCore.App 1.1.2. I created a test project to test against that project but when building I noticed this warning:
[![enter image description here][1]][1]

I open the NuGet Package Manager and see that warning is correct, the project being tested has a different version of Microsoft.NETCore.App:
[![enter image description here][2]][2]
[![enter image description here][3]][3]

My problem is that Visual Studio is not letting me update that version, so I&#39;m confused on how to solve this issue:
[![enter image description here][4]][4]
Ideally I would just click the dropdown and select the right version but Visual Studio claims that it cannot do this because of &quot;additional constraints in the project or packages.config&quot;. How am I supposed to update that package? What &quot;additional constraints&quot; is Visual Studio referring to?


  [1]: https://i.stack.imgur.com/bOqUI.png
  [2]: https://i.stack.imgur.com/XqkkI.png
  [3]: https://i.stack.imgur.com/mT0pq.png
  [4]: https://i.stack.imgur.com/cbxqp.png

Content Type	Original Author	Original Content on Stackoverflow
Question	aksu	View Question on Stackoverflow
Solution 1 - C#	aksu	View Answer on Stackoverflow
Solution 2 - C#	Jon	View Answer on Stackoverflow

How do I set `OutputPath` in a Visual Studio 2017 project (new .csproj file format) without the target framework cluttering the resolved path?

C# Problem Overview

C# Solutions

Solution 1 - C#

Solution 2 - C#

Is it possible to rename _id field after mongo's group aggregation?

How to check if a string contains a char?

Attributions