C:\WINDOWS\ assembly\NativeImages_v2.0.50727_32\index3a0.dat 的用途是什么？
我试图诊断为什么 .Net ActiveX 控件在某些机器上的加载时间比其他机器慢得多，并且我发现（使用 ProcMon）在缓慢加载控件的机器上，浏览器进程似乎花费了很多时间用这个文件做一些事情。
在缓慢的过程中，我看到上述格式的事件组 (4-8) 大约需要 200 毫秒才能完成：
6:02:17.333 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
6:02:17.364 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
6:02:17.396 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
6:02:17.427 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
但是，在控件加载速度很快的计算机上进行的类似跟踪中，我只看到一行带有 成功结果。
这个文件是什么？
I'm trying to diagnose why out .Net ActiveX control has a much slower load time on certain machines than others and I've discovered (using ProcMon) that on machines that load the control slowly the browser process seems to spend a lot of time doing something with this file.
In the slow process I see groups of events (4-8) in the above format that take around 200ms to complete:
6:02:17.333 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
6:02:17.364 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
6:02:17.396 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
6:02:17.427 CreateFile C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\index3a0.dat NAME NOT FOUND
However in a similar trace taken on a machine where the control loads quickly I see only a single line with a SUCCESS result.
What is this file?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为这与 GAC 条目的缓存/快速查找或类似的东西有关，在我的系统上它被称为 index1c.dat （在这个系统上它是 0 字节）
我猜测这个名称来自于下的 LatestIndex 值HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\NativeImagesIndex\v2.0.50727_32
您可以尝试 Windows Update 或尝试运行
"%windir%\Microsoft.NET\Framework\v2.0.50727\ngen" update...但即使您可以触发此缓存的更新，这也可能不是导致问题的原因。
I assume this has something to do with caching/quick lookup of GAC entries or something like that, on my system it is called index1c.dat (It is 0 bytes on this system)
I'm guessing the name comes from the LatestIndex value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\NativeImagesIndex\v2.0.50727_32
You could try windows update or try running
"%windir%\Microsoft.NET\Framework\v2.0.50727\ngen" update...but even if you could trigger a update of this cache, this might not be the cause of your problems.