Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Willow Web Workload] Creating Razor v3 WSP hangs #3241

Closed
rrelyea opened this issue Jul 28, 2016 · 2 comments
Closed

[Willow Web Workload] Creating Razor v3 WSP hangs #3241

rrelyea opened this issue Jul 28, 2016 · 2 comments
Assignees
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Product:VS.Client Type:Bug
Milestone

Comments

@rrelyea
Copy link
Contributor

rrelyea commented Jul 28, 2016

Tracking TFS Bug: 245277:[Willow Web Workload] Creating Razor v3 WSP hangs

Likely want fix in dev and release-3.5.0-rc branches.

@rrelyea rrelyea added Priority:1 High priority issues that must be resolved in the current sprint. Product:VS.Client Type:Bug labels Jul 28, 2016
@rrelyea rrelyea added this to the 3.5 RTM milestone Jul 28, 2016
@joelverhagen
Copy link
Member

Repro steps:

  1. VS15 Willow install, build 15.0.25527.0
  2. NuGet 3.5.0.1657
  3. File > New Website
  4. ASP.NET Web Site (Razor v3)

The template wizard hangs when installing Microsoft.Net.Compilers (version 1.0.0) to the website.

@joelverhagen
Copy link
Member

More details.

  • We have only been able to repro it on one VM and only on one user under that VM (@joeloff). A different user on the same VM did not repro.
  • The VM was Windows 10 Enterprise (build 10240), 32-bit OS. 2 cores with 4 GB RAM.

The project creation seemed to hang in NuGet code while adding binding redirects.

The issue was fixed on @joeloff's profile by clearing the MEF cache (instructions followed).

Since we cannot repro on any other machine and clearing the MEF cache fixed the problem, we are thinking this is some bad MEF state that cannot be hit by customers. Therefore, we are closing this bug but keeping the VM snapshot around just in case this problem crops up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:1 High priority issues that must be resolved in the current sprint. Product:VS.Client Type:Bug
Projects
None yet
Development

No branches or pull requests

2 participants