有没有人成功地使用免注册COM与.NET组件？ [英] Is anyone successfully using registration-free COM with .NET components?

问题描述

直到最近，我们使用免注册COM 我们的本地和.NET愉快COM组件。但是，我们遇到了一个奇怪的问题，即我们的应用程序推出了Windows XP SP3随机崩溃（但不能在Vista上）后，我们只改一个.NET程序集的版本号从候选发布版将发布。 （你能不恨墨菲定律？）

Until recently, we were happily using registration-free COM for our native and .NET COM components. However, we ran into a weird issue where our application started crashing randomly on windows XP SP3 (but not on vista) after we only changed the version number of a .NET assembly to move from release candidate to release. (Don't you just hate Murphy's law?)

在很多丢失的人日和磨牙，我们发现这个问题是在sxs.dll 已知的bug >这检索有关.NET类的信息时，会导致堆损坏。这里有一个热修复，这使得这个问题消失，但热修复程序不打算重新分配。

After many a lost man-day and teeth grinding, we discovered that the issue was a known bug in sxs.dll which causes heap corruption when retrieving information about a .NET class. There is a hot-fix which makes the issue disappear but hot-fixes are not intended to be redistributed.

我们有点难倒有在免注册COM实现这样一个可怕的错误。有没有人在那里成功地利用免注册COM组件用于.NET组件？你是怎么解决这个问题？

We're kinda stumped that there is such a horrible bug in the registration-free COM implementation. Is anyone out there successfully using registration-free COM for .NET components? How did you work around this issue?

推荐答案

这个问题涉及到如何的SxS计算之类的信息的大小。程序集的版本号是该信息的一部分。

This issue is related to how SxS calculates the size of the class information. The version number of the assembly is part of this information.

由于它正在与候选发布版本号，也许是解决方法，你是让释放相同长度的RC版本的版本号。

Since it was working with the release candidate version number, perhaps the workaround for you is to make the version number of the release the same length as the RC release.

如果这个不适合你的工作，有一个重新分配请求权修补程序建立的过程。我将参与微软客户支持，以追求这条路线。

If this doesn't work for you, there is an established process for requesting redistribution rights for hotfixes. I would engage Microsoft customer support to pursue this route.

这篇关于有没有人成功地使用免注册COM与.NET组件？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！