sxs | 易学教程

COM interop side-by-side assemblies

阅读更多关于 COM interop side-by-side assemblies

问题 I need to deploy multiple versions of the same C# .NET project. The project output is a COM interop assembly to be used in a native application. The problem I'm having is that I have to deploy several versions of this assembly side-by-side but whatever I do doesn't seem to create different versions. Instead the versions override eachother. I've tried changing the assembly GUID, tried changing the assembly version numbers, tried regenerating the assembly strong name key, tried changing the

Simulating SideBySide for Out of Process ActiveX

阅读更多关于 Simulating SideBySide for Out of Process ActiveX

We are adapting our client side relatively complicated application (ActiveX / .net / Delphi / C++ / COM ) to use SxS to achieve non admin deployment and isolation from older versions of our product. We were able to achieve this goal for almost all our in proc components such as our .net ui, Delphi ui, and the COM servers we use in proc by composing a manifest file which described all the libraries used by our process, with no registration on the client of any of the components (almost). And here comes the almost part: At the moment, our application invokes (from it's c++ portion) an out of

Building and deploying dll on windows: SxS, manifests and all that jazz

阅读更多关于 Building and deploying dll on windows: SxS, manifests and all that jazz

问题 Since VS 2005, I see that it is not possible to simply build a dll against MS runtime and deploy them together (http://www.ddj.com/windows/184406482). I am deeply confused by manifest, SxS and co: MSDN documentation is really poor, with circular references; specially since I am more a Unix guy, I find all those uninformative. My core problem is linking a dll against msvc9 or msvc8: since those runtime are not redistributable, what are the steps to link and deploy such a dll ? In particular,

Building and deploying dll on windows: SxS, manifests and all that jazz

阅读更多关于 Building and deploying dll on windows: SxS, manifests and all that jazz

Since VS 2005, I see that it is not possible to simply build a dll against MS runtime and deploy them together ( http://www.ddj.com/windows/184406482 ). I am deeply confused by manifest, SxS and co: MSDN documentation is really poor, with circular references; specially since I am more a Unix guy, I find all those uninformative. My core problem is linking a dll against msvc9 or msvc8: since those runtime are not redistributable, what are the steps to link and deploy such a dll ? In particular, how are the manifest generated (I don't want mt.exe, I want something which is portable across

Is anyone successfully using registration-free COM with .NET components?

阅读更多关于 Is anyone successfully using registration-free COM with .NET components?

问题 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?) 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