Skip to content
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

Error on opening create project with vs2017rc #563

Closed
caste1969 opened this issue Jan 6, 2017 · 6 comments
Closed

Error on opening create project with vs2017rc #563

caste1969 opened this issue Jan 6, 2017 · 6 comments

Comments

@caste1969
Copy link

I create a new project from cmd using yo aspnetcore-spa, with target vs2017. But when I try to open the generated project I got an error like this: value cannot be null, parameter name:key.
Visual studio generate this dump for the error:

=====================
07/01/2017 00:08:45
Recoverable
System.AggregateException: One or more errors occurred. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.Collections.Generic.Dictionary2.FindEntry(TKey key) at System.Collections.Generic.Dictionary2.get_Item(TKey key)
at Microsoft.VisualStudio.ProjectSystem.Designers.PhysicalProjectTreeProvider.ResolveDependentItems(Dictionary2 pendingItemsByDirectory) at Microsoft.VisualStudio.ProjectSystem.Designers.PhysicalProjectTreeProvider.GenerateOriginalTree(ConfiguredProjectExports configuredProjectExports, CancellationToken cancellationToken) at Microsoft.VisualStudio.ProjectSystem.Designers.PhysicalProjectTreeProvider.<GenerateOriginalTreeAsync>d__117.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.TreeUpdateSubmission.<UpdateTree>d__25.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass95_0.<<Initialize>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass102_0.<<SubmitTreeUpdateAsync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass114_0.<<SubmitTreeUpdateHelperAsync>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass102_0.<<SubmitTreeUpdateAsync>b__0>d.MoveNext() --- End of inner exception stack trace --- ---> (Inner Exception #0) System.ArgumentNullException: Value cannot be null. Parameter name: key at System.Collections.Generic.Dictionary2.FindEntry(TKey key)
at System.Collections.Generic.Dictionary2.get_Item(TKey key) at Microsoft.VisualStudio.ProjectSystem.Designers.PhysicalProjectTreeProvider.ResolveDependentItems(Dictionary2 pendingItemsByDirectory)
at Microsoft.VisualStudio.ProjectSystem.Designers.PhysicalProjectTreeProvider.GenerateOriginalTree(ConfiguredProjectExports configuredProjectExports, CancellationToken cancellationToken)
at Microsoft.VisualStudio.ProjectSystem.Designers.PhysicalProjectTreeProvider.d__117.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.TreeUpdateSubmission.d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass95_0.<b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass102_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass114_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.ProjectSystem.ProjectTreeProviderBase.<>c__DisplayClass102_0.<b__0>d.MoveNext()<---

===================

Many thanks
caste

@SteveSandersonMS
Copy link
Member

That's strange. It doesn't happen on my installation of VS2017RC. Is it possible that you have any add-ins installed?

Do you have any more information that would enable me to reproduce this error? I'm not sure I can do anything to investigate and fix this without being able to reproduce it.

@caste1969
Copy link
Author

caste1969 commented Jan 7, 2017

HI Steve, many thanks for your quickly replay.
Perhaps it's depending on the version of visual studio. I'm using this version:

Microsoft Visual Studio Enterprise 2017 RC
Version 15.0.26020.0 D15REL
Microsoft .NET Framework
Version 4.6.01586

Installed Version: Enterprise

Architecture Diagrams and Analysis Tools 00369-50000-00000-AA079
Microsoft Architecture Diagrams and Analysis Tools

Visual Basic 2017 RC 00369-50000-00000-AA079
Microsoft Visual Basic 2017 RC

Visual C# 2017 RC 00369-50000-00000-AA079
Microsoft Visual C# 2017 RC

Visual C++ 2017 RC 00369-50000-00000-AA079
Microsoft Visual C++ 2017 RC

Application Insights Tools for Visual Studio Package 8.4.01118.2
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2016 15.0.21206.0
ASP.NET and Web Tools 2016

ASP.NET Web Frameworks and Tools 2013 5.2.41123.0
For additional information, visit https://www.asp.net/

Azure App Service Tools v2.9.6 15.0.21130.0
Azure App Service Tools v2.9.6

Azure Data Lake Node 1.0
This package contains the Data Lake integration nodes for Server Explorer.

Azure Data Lake Tools for Visual Studio 2.2.3100.0
Microsoft Azure Data Lake Tools for Visual Studio

Common Azure Tools 1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

JavaScript Language Service 2.0
JavaScript Language Service

JavaScript Project System 2.0
JavaScript Project System

KofePackagePackage Extension 1.0
KofePackagePackage Visual Studio Extension Detailed Info

Microsoft Azure Hive Query Language Service 2.2.3100.0
Language service for Hive query

Microsoft Azure Tools 2.9
Microsoft Azure Tools for Microsoft Visual Studio vNext - v2.9.41121.2

Microsoft Continuous Delivery Tools for Visual Studio 0.1
Simplifying the configuration of continuous build integration and continuous build delivery from within the Visual Studio IDE.

Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package

Node.js Tools 1.3.41102.00
Adds support for developing and debugging Node.js apps in Visual Studio

Node.js Tools - Profiling 1.3.41102.00
Profiling support for Node.js projects.

NuGet Package Manager 4.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

SQL Server Data Tools 15.1.61124.0
Microsoft SQL Server Data Tools

ToolWindowHostedEditor 1.0
Hosting json editor into a tool window

TSCPackage Extension 1.0
TSCPackage Visual Studio Extension Detailed Info

TypeScript 2.1.3.0
TypeScript tools for Visual Studio

@MarkPieszak
Copy link
Contributor

@caste1969 Can you keep TypeScript at 2.0.x, 2.1 currently has some issues with ng that will be fixed in the upcoming ng4.x releases. It might not the problem for you, but it's worth a shot!

@mike-morr
Copy link

I am getting the same thing with the React (no Redux). I am on the same build of Visual Studio as OP.

@SteveSandersonMS
Copy link
Member

Strange. I'm now on the same version of VS2017RC as you, and still don't get such an error.

Three things you could try to hopefully narrow this down:

  • Does the same problem still occur for you if you use the latest (0.7.3) version of generator-aspnetcore-spa? It has a few tweaks to the csproj that might be relevant (e.g., excluding the .git dir).
  • Which .NET Core SDK versions you have installed on your machine? Look in C:\Program Files\dotnet\sdk.
  • Does it still happen for you if you use the VS 2017RC Professional or Community editions?

@caste1969
Copy link
Author

Hi , the problem was the version of generator-aspnetcore-spa, I use 0.7.2. With 0.7.3 it works perfectly.
Many thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants