Missing assembly references and/or directives “The type or namespace name could not be found”Should 'using' directives be inside or outside the namespace?The located assembly's manifest definition does not match the assembly referenceMetadata file '.dll' could not be foundGetting “type or namespace name could not be found” but everything seems ok?The type or namespace name could not be foundType or namespace name does not existThe type or namespace MongoServer could not be foundType or namespace name could not be found (missing using directive or assembly reference?)Not able to see Add->Existing Project as Azure Web Job Option when I right click on Web project in Solution Explorer of Visual Studio 2017Timeout error when connecting to CosmosDB with MongoDB API

Why am I Seeing A Weird "Notch" on the Data Line For Some Logical 1s?

Extreme flexible working hours: how to get to know people and activities?

What are neighboring ports?

Getting UPS Power from One Room to Another

Is it a bad idea to to run 24 tap and shock lands in standard

How to learn Linux system internals

Proving that a Russian cryptographic standard is too structured

How can I remove material from this wood beam?

Bb13b9 confusion

Fermat's statement about the ancients: How serious was he?

What are some really overused phrases in French that are common nowadays?

Scientist couple raises alien baby

Is using 'echo' to display attacker-controlled data on the terminal dangerous?

Why Does Mama Coco Look Old After Going to the Other World?

Who won a Game of Bar Dice?

Ability To Change Root User Password (Vulnerability?)

A word that means "blending into a community too much"

The Frozen Wastes

Why am I getting a strange double quote (“) in Open Office instead of the ordinary one (")?

How do free-speech protections in the United States apply in public to corporate misrepresentations?

How to publish items after pipeline is finished?

How come the nude protesters were not arrested?

Can I utilise a baking stone to make crepes?

Why did Intel abandon unified CPU cache?



Missing assembly references and/or directives “The type or namespace name could not be found”


Should 'using' directives be inside or outside the namespace?The located assembly's manifest definition does not match the assembly referenceMetadata file '.dll' could not be foundGetting “type or namespace name could not be found” but everything seems ok?The type or namespace name could not be foundType or namespace name does not existThe type or namespace MongoServer could not be foundType or namespace name could not be found (missing using directive or assembly reference?)Not able to see Add->Existing Project as Azure Web Job Option when I right click on Web project in Solution Explorer of Visual Studio 2017Timeout error when connecting to CosmosDB with MongoDB API






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















Referencing this Azure Cosmos Db Tutorial (https://docs.microsoft.com/en-us/azure/cosmos-db/create-mongodb-dotnet), released three months ago and apparently already out of date.



I followed the instructions: cloned the sample app files, updated my connection string, installed the MongoDB.Driver through the Nuget package manager and ran the app. The build (in Visual Studio 2017) failed due to several CS0246 & CS0234 errors in 2 of the app files. See screenshot



here



I'm not a C# developer. I suspect either the MongoDB API has changed or the MongoDB.Driver is out of date. The error implies a directive or assembly reference is missing.



Either way, this is an issue in the underlying app files which were written by Microsoft and not me. See screenshot here. Does anyone have any recommendations on how I can troubleshoot these errors and successfully run the app? Maybe I need to install an older legacy version of MongoDB.Driver?










share|improve this question






















  • Did you disable the automatic download and update of NuGet packages?

    – Steve
    Mar 24 at 19:29











  • No I did not. I followed the tutorial step-by-step and didn't change any of the auto-update policies in visual studio 2017. do you recommend disabling?

    – emalcolmb
    Mar 24 at 19:35











  • No, if you look at the reference node in the solution explorer did you notice some missing reference? Something has not been correctly downloaded from the NuGet repository. You can check the TOOLS->NuGet Package Manager->Manage NuGet package for Solution and try to update any missing packages

    – Steve
    Mar 24 at 19:39











  • I've already installed & updated the MongoDB.Driver to the latest version. I'm looking at the NuGet package right now and its installed and fully updated.

    – emalcolmb
    Mar 24 at 19:43












  • Can you show all nuget packages installed in your project? trying installing nuget.org/packages/mongodb.bson at least first reference issue should go away.

    – Hemant Sakta
    Mar 24 at 20:20

















0















Referencing this Azure Cosmos Db Tutorial (https://docs.microsoft.com/en-us/azure/cosmos-db/create-mongodb-dotnet), released three months ago and apparently already out of date.



I followed the instructions: cloned the sample app files, updated my connection string, installed the MongoDB.Driver through the Nuget package manager and ran the app. The build (in Visual Studio 2017) failed due to several CS0246 & CS0234 errors in 2 of the app files. See screenshot



here



I'm not a C# developer. I suspect either the MongoDB API has changed or the MongoDB.Driver is out of date. The error implies a directive or assembly reference is missing.



Either way, this is an issue in the underlying app files which were written by Microsoft and not me. See screenshot here. Does anyone have any recommendations on how I can troubleshoot these errors and successfully run the app? Maybe I need to install an older legacy version of MongoDB.Driver?










share|improve this question






















  • Did you disable the automatic download and update of NuGet packages?

    – Steve
    Mar 24 at 19:29











  • No I did not. I followed the tutorial step-by-step and didn't change any of the auto-update policies in visual studio 2017. do you recommend disabling?

    – emalcolmb
    Mar 24 at 19:35











  • No, if you look at the reference node in the solution explorer did you notice some missing reference? Something has not been correctly downloaded from the NuGet repository. You can check the TOOLS->NuGet Package Manager->Manage NuGet package for Solution and try to update any missing packages

    – Steve
    Mar 24 at 19:39











  • I've already installed & updated the MongoDB.Driver to the latest version. I'm looking at the NuGet package right now and its installed and fully updated.

    – emalcolmb
    Mar 24 at 19:43












  • Can you show all nuget packages installed in your project? trying installing nuget.org/packages/mongodb.bson at least first reference issue should go away.

    – Hemant Sakta
    Mar 24 at 20:20













0












0








0








Referencing this Azure Cosmos Db Tutorial (https://docs.microsoft.com/en-us/azure/cosmos-db/create-mongodb-dotnet), released three months ago and apparently already out of date.



I followed the instructions: cloned the sample app files, updated my connection string, installed the MongoDB.Driver through the Nuget package manager and ran the app. The build (in Visual Studio 2017) failed due to several CS0246 & CS0234 errors in 2 of the app files. See screenshot



here



I'm not a C# developer. I suspect either the MongoDB API has changed or the MongoDB.Driver is out of date. The error implies a directive or assembly reference is missing.



Either way, this is an issue in the underlying app files which were written by Microsoft and not me. See screenshot here. Does anyone have any recommendations on how I can troubleshoot these errors and successfully run the app? Maybe I need to install an older legacy version of MongoDB.Driver?










share|improve this question














Referencing this Azure Cosmos Db Tutorial (https://docs.microsoft.com/en-us/azure/cosmos-db/create-mongodb-dotnet), released three months ago and apparently already out of date.



I followed the instructions: cloned the sample app files, updated my connection string, installed the MongoDB.Driver through the Nuget package manager and ran the app. The build (in Visual Studio 2017) failed due to several CS0246 & CS0234 errors in 2 of the app files. See screenshot



here



I'm not a C# developer. I suspect either the MongoDB API has changed or the MongoDB.Driver is out of date. The error implies a directive or assembly reference is missing.



Either way, this is an issue in the underlying app files which were written by Microsoft and not me. See screenshot here. Does anyone have any recommendations on how I can troubleshoot these errors and successfully run the app? Maybe I need to install an older legacy version of MongoDB.Driver?







c# mongodb visual-studio-2017 azure-cosmosdb azure-cosmosdb-mongoapi






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 24 at 19:25









emalcolmbemalcolmb

529




529












  • Did you disable the automatic download and update of NuGet packages?

    – Steve
    Mar 24 at 19:29











  • No I did not. I followed the tutorial step-by-step and didn't change any of the auto-update policies in visual studio 2017. do you recommend disabling?

    – emalcolmb
    Mar 24 at 19:35











  • No, if you look at the reference node in the solution explorer did you notice some missing reference? Something has not been correctly downloaded from the NuGet repository. You can check the TOOLS->NuGet Package Manager->Manage NuGet package for Solution and try to update any missing packages

    – Steve
    Mar 24 at 19:39











  • I've already installed & updated the MongoDB.Driver to the latest version. I'm looking at the NuGet package right now and its installed and fully updated.

    – emalcolmb
    Mar 24 at 19:43












  • Can you show all nuget packages installed in your project? trying installing nuget.org/packages/mongodb.bson at least first reference issue should go away.

    – Hemant Sakta
    Mar 24 at 20:20

















  • Did you disable the automatic download and update of NuGet packages?

    – Steve
    Mar 24 at 19:29











  • No I did not. I followed the tutorial step-by-step and didn't change any of the auto-update policies in visual studio 2017. do you recommend disabling?

    – emalcolmb
    Mar 24 at 19:35











  • No, if you look at the reference node in the solution explorer did you notice some missing reference? Something has not been correctly downloaded from the NuGet repository. You can check the TOOLS->NuGet Package Manager->Manage NuGet package for Solution and try to update any missing packages

    – Steve
    Mar 24 at 19:39











  • I've already installed & updated the MongoDB.Driver to the latest version. I'm looking at the NuGet package right now and its installed and fully updated.

    – emalcolmb
    Mar 24 at 19:43












  • Can you show all nuget packages installed in your project? trying installing nuget.org/packages/mongodb.bson at least first reference issue should go away.

    – Hemant Sakta
    Mar 24 at 20:20
















Did you disable the automatic download and update of NuGet packages?

– Steve
Mar 24 at 19:29





Did you disable the automatic download and update of NuGet packages?

– Steve
Mar 24 at 19:29













No I did not. I followed the tutorial step-by-step and didn't change any of the auto-update policies in visual studio 2017. do you recommend disabling?

– emalcolmb
Mar 24 at 19:35





No I did not. I followed the tutorial step-by-step and didn't change any of the auto-update policies in visual studio 2017. do you recommend disabling?

– emalcolmb
Mar 24 at 19:35













No, if you look at the reference node in the solution explorer did you notice some missing reference? Something has not been correctly downloaded from the NuGet repository. You can check the TOOLS->NuGet Package Manager->Manage NuGet package for Solution and try to update any missing packages

– Steve
Mar 24 at 19:39





No, if you look at the reference node in the solution explorer did you notice some missing reference? Something has not been correctly downloaded from the NuGet repository. You can check the TOOLS->NuGet Package Manager->Manage NuGet package for Solution and try to update any missing packages

– Steve
Mar 24 at 19:39













I've already installed & updated the MongoDB.Driver to the latest version. I'm looking at the NuGet package right now and its installed and fully updated.

– emalcolmb
Mar 24 at 19:43






I've already installed & updated the MongoDB.Driver to the latest version. I'm looking at the NuGet package right now and its installed and fully updated.

– emalcolmb
Mar 24 at 19:43














Can you show all nuget packages installed in your project? trying installing nuget.org/packages/mongodb.bson at least first reference issue should go away.

– Hemant Sakta
Mar 24 at 20:20





Can you show all nuget packages installed in your project? trying installing nuget.org/packages/mongodb.bson at least first reference issue should go away.

– Hemant Sakta
Mar 24 at 20:20












2 Answers
2






active

oldest

votes


















0














I downloaded the sample app from https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/archive/master.zip and it is currently indeed in an inconsistent state and it should be fixed by MS.



The problem



Project references dlls which cannot be found:



enter image description here



The cause is that Nuget is asked to download MongoDB.BSon 2.6.1, but project references are searching the 2.3.0 folders.



 <Reference Include="MongoDB.Driver, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
<HintPath>..packagesMongoDB.Driver.2.3.0libnet45MongoDB.Driver.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="MongoDB.Driver.Core, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
<HintPath>..packagesMongoDB.Driver.Core.2.3.0libnet45MongoDB.Driver.Core.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="MongoDB.Driver.Legacy, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
<HintPath>..packagesmongocsharpdriver.2.3.0libnet45MongoDB.Driver.Legacy.dll</HintPath>
<Private>True</Private>
</Reference>


I reported the issue to MS, you can track it here: https://github.com/MicrosoftDocs/azure-docs/issues/28204



The fix



You could wait for MS to fix it -or- fix the broken references yourself:



  1. Remove the invalid MongoDB.* assembly references.

  2. Readd the references from folders nuget has downloaded:

    • ..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll

    • ..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll

    • ..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll


  3. Compile to verify

You can also simplify the above process by just opening MyTaskListApp.csproj file and making the edits there:



<Reference Include="MongoDB.Bson">
<HintPath>..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll</HintPath>
</Reference>
<Reference Include="MongoDB.Driver">
<HintPath>..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll</HintPath>
</Reference>
<Reference Include="MongoDB.Driver.Core">
<HintPath>..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll</HintPath>
</Reference>





share|improve this answer
































    0














    Thanks for your feedback. This is an issue in the csproj file. For which pull request has already been raised.
    You can refer the pull request to check the ETA for this fix.



    https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/pull/8



    Hope it helps.






    share|improve this answer























      Your Answer






      StackExchange.ifUsing("editor", function ()
      StackExchange.using("externalEditor", function ()
      StackExchange.using("snippets", function ()
      StackExchange.snippets.init();
      );
      );
      , "code-snippets");

      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "1"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55327644%2fmissing-assembly-references-and-or-directives-the-type-or-namespace-name-could%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      I downloaded the sample app from https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/archive/master.zip and it is currently indeed in an inconsistent state and it should be fixed by MS.



      The problem



      Project references dlls which cannot be found:



      enter image description here



      The cause is that Nuget is asked to download MongoDB.BSon 2.6.1, but project references are searching the 2.3.0 folders.



       <Reference Include="MongoDB.Driver, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
      <HintPath>..packagesMongoDB.Driver.2.3.0libnet45MongoDB.Driver.dll</HintPath>
      <Private>True</Private>
      </Reference>
      <Reference Include="MongoDB.Driver.Core, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
      <HintPath>..packagesMongoDB.Driver.Core.2.3.0libnet45MongoDB.Driver.Core.dll</HintPath>
      <Private>True</Private>
      </Reference>
      <Reference Include="MongoDB.Driver.Legacy, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
      <HintPath>..packagesmongocsharpdriver.2.3.0libnet45MongoDB.Driver.Legacy.dll</HintPath>
      <Private>True</Private>
      </Reference>


      I reported the issue to MS, you can track it here: https://github.com/MicrosoftDocs/azure-docs/issues/28204



      The fix



      You could wait for MS to fix it -or- fix the broken references yourself:



      1. Remove the invalid MongoDB.* assembly references.

      2. Readd the references from folders nuget has downloaded:

        • ..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll

        • ..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll

        • ..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll


      3. Compile to verify

      You can also simplify the above process by just opening MyTaskListApp.csproj file and making the edits there:



      <Reference Include="MongoDB.Bson">
      <HintPath>..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll</HintPath>
      </Reference>
      <Reference Include="MongoDB.Driver">
      <HintPath>..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll</HintPath>
      </Reference>
      <Reference Include="MongoDB.Driver.Core">
      <HintPath>..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll</HintPath>
      </Reference>





      share|improve this answer





























        0














        I downloaded the sample app from https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/archive/master.zip and it is currently indeed in an inconsistent state and it should be fixed by MS.



        The problem



        Project references dlls which cannot be found:



        enter image description here



        The cause is that Nuget is asked to download MongoDB.BSon 2.6.1, but project references are searching the 2.3.0 folders.



         <Reference Include="MongoDB.Driver, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
        <HintPath>..packagesMongoDB.Driver.2.3.0libnet45MongoDB.Driver.dll</HintPath>
        <Private>True</Private>
        </Reference>
        <Reference Include="MongoDB.Driver.Core, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
        <HintPath>..packagesMongoDB.Driver.Core.2.3.0libnet45MongoDB.Driver.Core.dll</HintPath>
        <Private>True</Private>
        </Reference>
        <Reference Include="MongoDB.Driver.Legacy, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
        <HintPath>..packagesmongocsharpdriver.2.3.0libnet45MongoDB.Driver.Legacy.dll</HintPath>
        <Private>True</Private>
        </Reference>


        I reported the issue to MS, you can track it here: https://github.com/MicrosoftDocs/azure-docs/issues/28204



        The fix



        You could wait for MS to fix it -or- fix the broken references yourself:



        1. Remove the invalid MongoDB.* assembly references.

        2. Readd the references from folders nuget has downloaded:

          • ..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll

          • ..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll

          • ..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll


        3. Compile to verify

        You can also simplify the above process by just opening MyTaskListApp.csproj file and making the edits there:



        <Reference Include="MongoDB.Bson">
        <HintPath>..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll</HintPath>
        </Reference>
        <Reference Include="MongoDB.Driver">
        <HintPath>..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll</HintPath>
        </Reference>
        <Reference Include="MongoDB.Driver.Core">
        <HintPath>..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll</HintPath>
        </Reference>





        share|improve this answer



























          0












          0








          0







          I downloaded the sample app from https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/archive/master.zip and it is currently indeed in an inconsistent state and it should be fixed by MS.



          The problem



          Project references dlls which cannot be found:



          enter image description here



          The cause is that Nuget is asked to download MongoDB.BSon 2.6.1, but project references are searching the 2.3.0 folders.



           <Reference Include="MongoDB.Driver, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
          <HintPath>..packagesMongoDB.Driver.2.3.0libnet45MongoDB.Driver.dll</HintPath>
          <Private>True</Private>
          </Reference>
          <Reference Include="MongoDB.Driver.Core, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
          <HintPath>..packagesMongoDB.Driver.Core.2.3.0libnet45MongoDB.Driver.Core.dll</HintPath>
          <Private>True</Private>
          </Reference>
          <Reference Include="MongoDB.Driver.Legacy, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
          <HintPath>..packagesmongocsharpdriver.2.3.0libnet45MongoDB.Driver.Legacy.dll</HintPath>
          <Private>True</Private>
          </Reference>


          I reported the issue to MS, you can track it here: https://github.com/MicrosoftDocs/azure-docs/issues/28204



          The fix



          You could wait for MS to fix it -or- fix the broken references yourself:



          1. Remove the invalid MongoDB.* assembly references.

          2. Readd the references from folders nuget has downloaded:

            • ..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll

            • ..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll

            • ..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll


          3. Compile to verify

          You can also simplify the above process by just opening MyTaskListApp.csproj file and making the edits there:



          <Reference Include="MongoDB.Bson">
          <HintPath>..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll</HintPath>
          </Reference>
          <Reference Include="MongoDB.Driver">
          <HintPath>..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll</HintPath>
          </Reference>
          <Reference Include="MongoDB.Driver.Core">
          <HintPath>..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll</HintPath>
          </Reference>





          share|improve this answer















          I downloaded the sample app from https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/archive/master.zip and it is currently indeed in an inconsistent state and it should be fixed by MS.



          The problem



          Project references dlls which cannot be found:



          enter image description here



          The cause is that Nuget is asked to download MongoDB.BSon 2.6.1, but project references are searching the 2.3.0 folders.



           <Reference Include="MongoDB.Driver, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
          <HintPath>..packagesMongoDB.Driver.2.3.0libnet45MongoDB.Driver.dll</HintPath>
          <Private>True</Private>
          </Reference>
          <Reference Include="MongoDB.Driver.Core, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
          <HintPath>..packagesMongoDB.Driver.Core.2.3.0libnet45MongoDB.Driver.Core.dll</HintPath>
          <Private>True</Private>
          </Reference>
          <Reference Include="MongoDB.Driver.Legacy, Version=2.3.0.157, Culture=neutral, processorArchitecture=MSIL">
          <HintPath>..packagesmongocsharpdriver.2.3.0libnet45MongoDB.Driver.Legacy.dll</HintPath>
          <Private>True</Private>
          </Reference>


          I reported the issue to MS, you can track it here: https://github.com/MicrosoftDocs/azure-docs/issues/28204



          The fix



          You could wait for MS to fix it -or- fix the broken references yourself:



          1. Remove the invalid MongoDB.* assembly references.

          2. Readd the references from folders nuget has downloaded:

            • ..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll

            • ..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll

            • ..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll


          3. Compile to verify

          You can also simplify the above process by just opening MyTaskListApp.csproj file and making the edits there:



          <Reference Include="MongoDB.Bson">
          <HintPath>..packagesMongoDB.Bson.2.6.1libnet45MongoDB.Bson.dll</HintPath>
          </Reference>
          <Reference Include="MongoDB.Driver">
          <HintPath>..packagesMongoDB.Driver.2.6.1libnet45MongoDB.Driver.dll</HintPath>
          </Reference>
          <Reference Include="MongoDB.Driver.Core">
          <HintPath>..packagesMongoDB.Driver.Core.2.6.1libnet45MongoDB.Driver.Core.dll</HintPath>
          </Reference>






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Mar 28 at 8:49

























          answered Mar 28 at 8:36









          Imre PühvelImre Pühvel

          2,17512228




          2,17512228























              0














              Thanks for your feedback. This is an issue in the csproj file. For which pull request has already been raised.
              You can refer the pull request to check the ETA for this fix.



              https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/pull/8



              Hope it helps.






              share|improve this answer



























                0














                Thanks for your feedback. This is an issue in the csproj file. For which pull request has already been raised.
                You can refer the pull request to check the ETA for this fix.



                https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/pull/8



                Hope it helps.






                share|improve this answer

























                  0












                  0








                  0







                  Thanks for your feedback. This is an issue in the csproj file. For which pull request has already been raised.
                  You can refer the pull request to check the ETA for this fix.



                  https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/pull/8



                  Hope it helps.






                  share|improve this answer













                  Thanks for your feedback. This is an issue in the csproj file. For which pull request has already been raised.
                  You can refer the pull request to check the ETA for this fix.



                  https://github.com/Azure-Samples/azure-cosmos-db-mongodb-dotnet-getting-started/pull/8



                  Hope it helps.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 28 at 9:43









                  angoyal-msftangoyal-msft

                  632




                  632



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Stack Overflow!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55327644%2fmissing-assembly-references-and-or-directives-the-type-or-namespace-name-could%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

                      용인 삼성생명 블루밍스 목차 통계 역대 감독 선수단 응원단 경기장 같이 보기 외부 링크 둘러보기 메뉴samsungblueminx.comeh선수 명단용인 삼성생명 블루밍스용인 삼성생명 블루밍스ehsamsungblueminx.comeheheheh

                      155 수학 과학 기타 둘러보기 메뉴eh추가해eh문서를 완성해