The Update tab is geared to display packages which have updates available while the consolidation tab is geared to display discrepancies between projects where both consume the same nuget package but are targeting different versions.

Sometimes the versions installed into projects within a solution can drift apart and it is necessary to consolidate the versions in use.

See https://docs.nuget.org/release-notes/nuget-3.0-preview for more information.

According to this [blog][1], it simply makes it easier to update different versioned NuGet packages across your projects



  [1]: http://ericphan.net/blog/2016/1/22/consolidating-nuget-package-versions

Consolidate has now been documented here: [NuGet Package Manager UI -&gt; Consolidate tab][1]

---

Tthanks to @kraigb to getting this into the official docs; reference: [GitHub Issue][2]


  [1]: https://docs.microsoft.com/en-us/nuget/tools/package-manager-ui#consolidate-tab
  [2]: https://github.com/NuGet/docs.microsoft.com-nuget/issues/498

I&#39;m using json.net (Newtonsoft&#39;s JsonSerializer). I need to customize serialization in order to meet following requirements:

 1. property names must start with lower case letter.
 2. Dictionary&lt;string, T&gt; must be serialized into jsonp where keys will be used for property names. LowerCase rule does not apply for dictionary keys.

for example:

    var product = new Product();
    procuct.Name = &quot;Product1&quot;;
    product.Items = new Dictionary&lt;string, Item&gt;();
    product.Items.Add(&quot;Item1&quot;, new Item { Description=&quot;Lorem Ipsum&quot; });

must serialize into:

    {
      name: &quot;Product1&quot;,
      items : {
        &quot;Item1&quot;: {
           description : &quot;Lorem Ipsum&quot;
        }
      }
    }

notice that property Name serializes into &quot;name&quot;, but key Item1 serializes into &quot;Item1&quot;;

I have tried to create CustomJsonWriter to serialize property names, but it changes also dicionary keys.

    public class CustomJsonWriter : JsonTextWriter
    {
        public CustomJsonWriter(TextWriter writer) : base(writer)
        {
            
        }
        public override void WritePropertyName(string name, bool escape)
        {
            if (name != &quot;$type&quot;)
            {
                name = name.ToCamelCase();
            }
            base.WritePropertyName(name, escape);
        }
    }


Newtonsoft JsonSerializer - Lower case properties and dictionary

It appears that I have data in the format of a list of NumPy arrays (`type() = np.ndarray`):
    
    [array([[ 0.00353654]]), array([[ 0.00353654]]), array([[ 0.00353654]]), 
    array([[ 0.00353654]]), array([[ 0.00353654]]), array([[ 0.00353654]]), 
    array([[ 0.00353654]]), array([[ 0.00353654]]), array([[ 0.00353654]]), 
    array([[ 0.00353654]]), array([[ 0.00353654]]), array([[ 0.00353654]]),
    array([[ 0.00353654]])]

I am trying to put this into a polyfit function:

    m1 = np.polyfit(x, y, deg=2)

However, it returns the error: `TypeError: expected 1D vector for x`

I assume I need to flatten my data into something like:

    [0.00353654, 0.00353654, 0.00353654, 0.00353654, 0.00353654, 0.00353654 ...]

I have tried a list comprehension which usually works on lists of lists, but this as expected has not worked:

    [val for sublist in risks for val in sublist]

What would be the best way to do this?


Flattening a list of NumPy arrays?

In NuGet for Visual Studio 2015, what is the difference between **consolidate** and **update** actions? In both cases I select a specific version that I want to use in selected projects.

Nuget consolidate vs update

In NuGet for Visual Studio 2015, what is the difference between consolidate and update actions? In both cases I select a specific version that I want to use in selected projects.

After updating to VS 2015 update 1, if I run a web project (MVC), stop the application, then try to run it again, VS stops and pops up a dialog claiming 

&gt; You are debugging a Release build of `&lt;myproject.dll&gt;`.
&gt; 
&gt; Using Just My Code with release builds using compiler optimizations results in a degraded debugging experience (e.g. breakpoints won&#39;t be hit).

The problem is I&#39;m _not running a release build._ I&#39;m clearly running the (same) debug build I just ran! Why does VS think I&#39;m running a release build? 

Cleaning the solution and re-running clears the error message, so something is hosed somewhere.

VS 2015 Update 1 - Claiming I am debugging a release build

I installed [Visual Studio Update 1][1] yesterday and now when running ASP.NET services locally on IIS (not the express version). I am seeing hundreds of requests per second to the address 

     http://localhost:49155/vshub/ca9dea4b016f45c68a6a8c1a07809eb4/DataWarehouseModule/dataWarehouse/getStatus/ 

What is causing this and is it preventable?


  [1]: https://www.visualstudio.com/en-us/news/vs2015-update1-vs.aspx

Visual Studio 2015 Update 1 spamming localhost

How can I get a proper syntax highlighting in Visual Studio 2015 for JSX with ES2015 code?

[![ES2015 code][1]][1]

It works fine if I remove the `import` and `export` keywords:
[![Without import/export][2]][2]

I just updated to Visual Studio 2015 Enterprise Update 1 but it still remains the same.

  [1]: http://i.stack.imgur.com/Al2XM.png
  [2]: http://i.stack.imgur.com/t5LwV.png


Visual Studio 2015 JSX/ES2015 syntax highlighting

When changing startup project for the solution from project A (initial startup) to project B (newly added project) the change of the startup project does not appear to be saved. 

When running F5 VS always change back to original setting of project A. 

I have checked the settings and also options build and run (for new solutions use the currently selected project as startup project) is not checked.

I have tried to delete the .suo file and so far no luck so any other ideas whats going on ?  
 

Visual Studio 2015 keeps switching startup project

I have installed Visual Studio 2015 Professional Edition, and my computer specs are Intel i7-3770 CPU 3.40&amp;nbsp;GHz, 8 GB RAM, and Windows 7 Enterprise 64-bit.

I want to upgrade my project to .NET 4.6 which is written in Visual studio 2005 .NET 2.0, but I have a serious problem about speed. After I open my project (huge project) in Visual Studio 2015 it is going crazy. Building, debugging, opening menus are too slow. Sometimes I got &quot;not responding&quot; message. Is it about Windows&amp;nbsp;7 or can you give me any advice about my speed problem?


Visual Studio 2015 is extremely slow

I&#39;m trying to validate that [Protocol Buffers][1] is going to work with the new portable runtimes from the ASP.NET team and ideally most other modern environments. The 3.0.0-alpha4 build was created a while ago using profile259, so I would expect some changes to be required in some cases, but I thought I&#39;d give it a try. I&#39;m aware of [Oren Novotny&#39;s post about targeting .NET Core][2], and expected to have to make some changes to the [Google.Protobuf nuspec file][3], but the error I&#39;m running into has me stumped.

DNX version: 1.0.0-rc1-update1

The scenario I&#39;m currently trying to test is a console app targeting dnx451. I have a very simple sample app:

    using Google.Protobuf.WellKnownTypes;
    using System;
    
    public class Program
    {
        public static void Main(string[] args)
        {
            Duration duration = new Duration { Seconds = 100, Nanos = 5555 };
            Console.WriteLine(duration);
        }
    }

... and a tiny `project.json`:

    {
      &quot;compilationOptions&quot;: { &quot;emitEntryPoint&quot;: true },
      &quot;dependencies&quot;: { &quot;Google.Protobuf&quot;: &quot;3.0.0-alpha4&quot; },
    
      &quot;frameworks&quot;: {
        &quot;dnx451&quot;: { }
      }
    }

Note that I&#39;m not even using `dnxcore*` here - ironically, I got *that* to work without issues.

`dnu restore` works fine; `dnx run` fails with:

&gt; Error: c:\Users\Jon\Test\Projects\protobuf-coreclr\src\ProtobufTest\Program.cs(9,9): DNX,Version=v4.5.1 error CS0012: The type &#39;Object&#39; is defined in an assembly that is not referenced. You must add a reference to assembly &#39;System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&#39;.

The following changes result in the same error:

- Explicitly adding a dependency to `&quot;System.Runtime&quot;: &quot;4.0.0&quot;` in the `dependencies` section for the framework
- Explicitly adding a dependency to `&quot;System.Runtime&quot;: &quot;4.0.0-beta-23109&quot;` in the `dependencies` section for the framework, and likewise for `4.0.10-beta-*`, `4.0.20-beta-*` and `4.0.21-beta*`.
- Adding dependencies to `System.Runtime` within the NuGet package (locally) and rebuilding against that - `project.lock.json` was updated to include System.Runtime v4.0.0, but the same error occurred
- Ditto including a `lib\dotnet` directory in the package, as well as the dependencies

Steps that *did* work (independently, and with no `dependencies` entries), but confuse me:

- Changing the `Console.WriteLine` call to just `Console.WriteLine(&quot;foo&quot;)` (but no other changes)
- Changing the type of the `duration` variable to `object` instead of `Duration`
- Removing all hint of Protocol Buffers entirely, and instead using `TimeSpan` or similar
- Adding the following to project.json in the `dnx451` section:

        &quot;frameworkAssemblies&quot;: {
          &quot;System.Runtime&quot;: &quot;&quot;
        }

Ultimately, I don&#39;t want users to have to do this - at least, not for the sake of Protocol Buffers. I&#39;m assuming this is *something* to do with how we&#39;re building Protocol Buffers, but as I don&#39;t understand the cause properly, it&#39;s hard to fix.

I expect that if I could work out a way of making a `dependencies` entry work, I could then add that dependency into Protocol Buffers itself, which would be fine - but as having a dependency on System.Runtime v4.0.0 in the project.lock file doesn&#39;t seem to help, I must be missing something :(

  [1]: https://github.com/google/protobuf
  [2]: https://oren.codes/2015/07/29/targeting-net-core/
  [3]: https://github.com/google/protobuf/blob/master/csharp/src/Google.Protobuf/Google.Protobuf.nuspec

Unable to resolve assembly reference issue without frameworkAssemblies

When I try to build my solution, I get the following error message:

&gt; Severity	Code	Description	Project	File	Line	Suppression State
&gt; Error		This project references NuGet package(s) that are missing on
&gt; this computer. Use NuGet Package Restore to download them.  For more
&gt; information, see http://go.microsoft.com/fwlink/?LinkID=322105. The
&gt; missing file is
&gt; ..\packages\Microsoft.Net.Compilers.1.1.1\build\Microsoft.Net.Compilers.props.	MusicKarma	C:\Users\Bryan\Documents\Visual
&gt; Studio 2015\Projects\MusicKarma\MusicKarma.csproj	268

When I look In my packages folder, I can find I file named Microsoft.Net.Compilers.props

I have tried to use Nuget Restore, but it keeps saying that I have all the packages.

This happens when I take this project from TFS to one of my computers.



Build error, This project references NuGet

I&#39;m working on a Xamarin Forms project.  I want to target Android and Windows 10 UWP.  

When I try to clean up the PCL by removing &quot;Windows 8&quot;, &quot;Windows Phone Silverlight 8&quot;, &quot;Windows Phone 8.1&quot;, &quot;Xamarin.ios&quot;, and &quot;Xamarin.ios (classic)&quot; from the PCL targets, I get the following nasty...

I&#39;m really just trying to remove WP8 as I don&#39;t care about targeting it.

&gt; The project&#39;s targets cannot be changed.  The selected targets require
&gt; the project to opt-into NuGet 3.0 support, however, Visual Studio
&gt; cannot automatically do this for you.  Please uninstall all NuGet
&gt; packages and try again.

How do you get a project to opt-into NuGet 3.0? 
Something else I should try?

environ: Xamarin Forms, VS2015

[![enter image description here][1]][1]

Thanks....


  [1]: http://i.stack.imgur.com/wBfST.png

Remove ios, windows8, and wp8 from Xamarin Forms PCL - nuget 3.0 opt-into error?

I [installed .net core from this site][1].  Playing with it led to a number of related package management questions:

 1. The `dotnet restore` command proceeded to &quot;install&quot; .net core NuGet packages.  Where were those packages &quot;installed&quot;?  A new folder was not created.
 2. The `dotnet restore` for the &quot;hello world&quot; minimal example required about a hundred NuGet packages, where 99% were presumably irrelevant to the &quot;hello world&quot; app.  Granted, a .net native build will remove all that is not needed - but I expected that the `restore` also would have grabbed very little (three or four packages, not a hundred).  Why this behavior?
 3. I created a second &quot;hello world&quot; project and again ran `dotnet restore`.  This time no packages were installed at all.  It seems all the packages installed the first time-around went into some global location to be shared.  I thought .Net Core didn&#39;t work that way.  I thought .Net Core projects kept all their dependencies locally.  The only framework I targeted was `dnxcore50`.  Why this behavior? 
 4. I would like to &quot;uninstall&quot; all these global packages, and try again (just for learning purposes).  How might that be accomplished?  Remember, as stated in question #1, I don&#39;t know where all those files were installed.
 5. Almost all of the packages installed via the `restore` command were listed as beta.  Odd.  I thought .Net Core was in RC1, not beta.  Confused by this.  Why this behavior?

I&#39;m also curious of what documentation could/would have explained all this to me.  I tried googling for each of these questions, and found nothing (perhaps just horrible google-fu?).

  [1]: https://dotnet.github.io/getting-started/


.Net Core and NuGet

I have a .net solution with approx 30 projects, all of them targeting .Net Framework 4.5. and each referencing at least 3-4 NuGet packages.

We now need to update them to .Net Framework 4.6.1. So here&#39;s what I need to know:

1. Do I need to re-target the NuGet packages as well or can I skip that since this will be an &#39;in-place&#39; upgrade?
2. If yes, can I just update the packages.config file for each project by replacing targetFramework=&quot;net45&quot; with targetFramework=&quot;net461&quot; for each NuGet package? I&#39;ve seen a few threads recommending uninstall and then reinstall the package via &#39;update-package&#39; command. I tried that today but it I ended up with a few errors.


Content Type	Original Author	Original Content on Stackoverflow
Question	yatskovsky	View Question on Stackoverflow
Solution 1 - Visual Studio-2015	Jordan Brooker	View Answer on Stackoverflow
Solution 2 - Visual Studio-2015	iwhp	View Answer on Stackoverflow
Solution 3 - Visual Studio-2015	Mohamed Badr	View Answer on Stackoverflow
Solution 4 - Visual Studio-2015	spottedmahn	View Answer on Stackoverflow

Nuget consolidate vs update

Visual Studio-2015 Problem Overview

Visual Studio-2015 Solutions

Solution 1 - Visual Studio-2015

Solution 2 - Visual Studio-2015

Solution 3 - Visual Studio-2015

Solution 4 - Visual Studio-2015

Flattening a list of NumPy arrays?

Newtonsoft JsonSerializer - Lower case properties and dictionary

Attributions