ngen: Display says no assemblies but there is one!

The ngen 'display' command says I have no Logos assemblies, but there is one in the C:\Windows\Assembly folder. The 'uninstall' command stated that the 7.10 beta didn't have an assembly, but it worked for the 7.9 installation. Could this happen because it was compiled under .NET 4.6 and I now have .NET 4.7?

The command path is C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe and ngen is v4.7.2046.0

Why do the Logos log files still show .NET 4.0.30319.42000 for both 4.6 and 4.7?

Find more posts tagged with

Comments

Dave Hooton

Bump.

Bradley Grainger (Logos)

The ngen 'display' command says I have no Logos assemblies, but there is one in the C:\Windows\Assembly folder. The 'uninstall' command stated that the 7.10 beta didn't have an assembly, but it worked for the 7.9 installation. Could this happen because it was compiled under .NET 4.6 and I now have .NET 4.7?

The command path is C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe and ngen is v4.7.2046.0

"ngen" is a Microsoft tool. For technical questions about it, you're probably more likely to get answers on the MSDN forums.

Why do the Logos log files still show .NET 4.0.30319.42000 for both 4.6 and 4.7?

Because Microsoft stopped returning the right .NET version from the "Environment.Version" property in the .NET Framework. As it turns out, we don't really use that version number when troubleshooting so we should probably just remove it.

Dave Hooton

https://community.logos.com/discussion/comment/923574#Comment_923574

Thanks, Bradley

I'll just assume it means that there were no valid/working assemblies under 4.7.