Do current NBGV versions work with old csproj files?

• Created a new Framework console app project in VS2017 targeting net462 (old-style csproj, not SDK)
• Did nbgv install (v.2.3.38)
• Deleted the version info from AssemblyInfo.cs
• Committed everything
• Ran msbuild.

I did not see any any version info embedded in the exe. Is this a known issue? Does Directory.build.props not get picked up by msbuild for old-style csproj files?

[AArnott]

Ah, I suspect you’re right on all of it. I think I can expound on part of it: the old style csproj projects are opened by the csproj.dll project system, which isn’t as dynamic as the project system that opens the new SDK style projects (which is CPS). Nevertheless, I’ve heard from the folks who own the csproj.dll project system that they still want NuGet to be a great experience with it, so if you file the bug, I suspect they’ll be interested in it (at least mildly).

[asherber]

Thanks – I’ll bring it up over there, but I’ll mention it here as well since you know more about how these things interact than I do.

The issue seems to be with how VS caches some information. Here are repeatable steps:

1. Create project in VS, build.
2. nbgv install
3. Build solution in VS – no version info
4. Rebuild solution in VS – no version info
5. Close and reopen solution
6. Build solution in VS – no version info
7. Rebuild solution in VS – version info!

In 3 and 4, it’s like VS isn’t aware of Directory.Build.props being added, because it’s already taken stock of the build situation and doesn’t rescan. After a close and reopen, VS is aware of the file, but the build doesn’t do anything because the obj dir is up to date. But a rebuild at that point (or deleting obj and building) gets everything to work.