-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
UpgradeProject crashes IDE with "Unable to check out the files from source control" #18199
Comments
@jcouv What edit is being made to that file? I wouldn't expect a change there. |
I wouldn't expect that file to be editted in any way. I'm not even sure what that file is. |
@jasonmalinowski - what are your thoughts here? |
@Pilchie: I would think we shouldn't crash? 😄 @jcouv: when you build a project the runtime wants to have an assembly level attribute defined that will say what framework you were targeting. This allows for various things to be done, like identifying if a given assembly can run on a given framework, maybe using it to know which backcompat shims to apply, etc. (This mechanism is less meaningful these days, but whatever.) Since frameworks are a figment of the imagination from the perspective of the compiler, there are MSBuild targets that generate these files that get included as an input to the compiler that you don't see in your project file. You'll see them on the command line though being passed in. They're files that are in temp and are never editable and should never be changed, so it's very odd you're seeing an effort to ensure they're editable in the first place. |
@jcouv Can you start by looking at the new solution and seeing why it thinks there are edits to that file? |
I wasn't able to repro live any more, so I looked at the dump. But I couldn't trace back further than the part that has new project and old project (I don't have dump information for the logic that produced the new project). |
I just ran into this again (twice). I saved a new dump file on my share (jcouvdev look for this bug's number), in the |
I found this issue through Google so I'm not sure if this is the correct place to report, but I'm experiencing the exact same problem. Trying to use Since the error mentions source control - the repo is in SVN and I use Ankh SVN as a Source Control plugin. I would be happy to provide any extra info but I don't know where to look. ActivityLog.xml has nothing interesting (it's on Verbose). |
I'm getting this every now and then when trying out #25875 but not consistently. The solution only has 1 project and is not in source control. |
Can this issue relate with Bug 397716: [Watson] clr20r3: CLR_EXCEPTION_System.Exception_80131500_Microsoft.VisualStudio.LanguageServices.dll!Microsoft.VisualStudio.LanguageServices.Implementation.ProjectSystem.VisualStudioWorkspaceImpl.EnsureEditableDocuments Callstacks look close but not same. |
@ivanbasov I'd say there's a pretty good likelihood these are the same. |
@JieCarolHu I'm currently seeing this in VS 15.7.2. Can you advise when this fix will be available? |
@StuartQ The fix should be available in 15.8 Preview 2 |
I’m getting a crash when using the UpgradeProject fixer.
It comes from
void EnsureEditableDocuments(IEnumerable<DocumentId> documents)
The input is a single document, which apparently has a null path.
I see a few possible interpretations, but I don’t know what’s the proper expectations:
I have a repro project and a minidump if needed.
[0] = (DocumentId, #15fef80d-55d3-442e-91f5-88ec51476497 - C:\Users\jcouv\AppData\Local\Temp\.NETFramework,Version=v4.6.AssemblyAttributes.cs)
The result from QueryEditFiles is
-2147467261
.The text was updated successfully, but these errors were encountered: