com

As a developer, I'm trying to setup a development environment on our brand new VMWare ESX server. Things are not working out: somewhere during the SharePoint Product & Technologies Configuration Wizard, the application just disappears, and in the event log I find the following error: .NET Runtime version 2.0.50727.3082 - Fatal Execution Engine Error (7A0979C6) (80131506) Now I know all this sounds suspiciously like a ServerFault.com style problem (and a very generic error message, lots of similar hits on google), and of course we are addressing the issue in such a way (installing/uninstalling

I need to access a third-party COM server with following interface definition (idl): interface IDisplay : IDispatch { HRESULT getFramebuffer ( [in] ULONG aScreenId, [out] IFramebuffer * * aFramebuffer, [out] LONG * aXOrigin, [out] LONG * aYOrigin ); }; As you can see, it returns 3 values via [out] parameter modificators. How to handle this via python win32 COM api? For example, i create an object and get IDisplay from it: object = win32com.client.Dispatch( "VirtualBox.VirtualBox" ) display = object.display How to call display.getFrameBuffer() so it will work? I have tried different ways, but

I have C# COM .dll. I would like to install the .dll once, but have it be registered for both x86 and x64. Here's the WiX I have for registering only x64: <Component Id="NETDLL.dll" Directory="INSTALLDIR"> <File Id="NETDLL.dll" Name="NETDLL.dll" KeyPath="yes" Source="..\NETDLL.dll" /> <Class Id="{78BE...}" Context="InprocServer32" Description="NETDLL" ThreadingModel="both" ForeignServer="mscoree.dll"> <ProgId Id="NETDLL" Description="NETDLL" /> </Class> <RegistryValue Root="HKCR" Key="CLSID\{78BE...}\Implemented Categories\{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29}" Value="" Type="string" Action=

I have a rather strange problem. I am exporting an interface from a C# library to COM. I have enabled the 'register with COM' project setting, so it calls tlbexp.exe to make the type libs. We use camel case on our method names and I noticed that the exported type library changes these any method that happens to coincide with a class name to Pascal case... e.g interface IFoo { void randomClass() } class RandomClass { } The exported IFoo in the type lib defines IFoo->RandomClass() instead of IFoo->randomClass() Any ideas on what causes this and how to stop it? Since COM is case-insensitive, both

Situation I run a build system that executes many builds for many project. To avoid one build impacting another we lock down the build user to only its workspace. Builds run as a non privileged users who only have write ability to the workspace. Challenge During our new build we need to use a legacy 3rdparty DLL that exposes its interface through COM. The dev team wants to register the build(regsrv32.exe) but our build security regime blocks this activity. If we relax the regime then the 3rdparty DLL will impact other builds and if I have two build which need two different versions I may have

I am opening VS2010 solutions using C# and VS2010 automation. I open the solutions like this: Type type = Type.GetTypeFromProgID("VisualStudio.DTE.10.0", true); Object comObject = Activator.CreateInstance(type); ... sol.Open(solution_full_path); The problem I am having is that when I create the instance of the VisualStudio.DTE.10.0 object, it starts the devenv.exe process from winlogon.exe which sees completely different environment than my application. Some of the environment variables are important for resolving some paths set in projects. Is there any how I can influence the environment