Hi All,
I have create a managed DLL (for dotnet 2.0) using visual C++ 2005 (work with windows media format).
I have problem on deployment in windows 2000 server.
It's error code is 0x8007007e seems like it's lost some library or thing.
Is there any prerequisite installed in client computer wen using managed c++.
Any one please help.
Thanks
Tutnik
Deployment Problem
Hot Topic
- How to change the text color in Edit control when it is disabled?
- ada conversion help
- Building Live.com Streaming Media Libraries in Visual C++ Express Beta 2
- VS2005 unnecessary build for project
- Region Resource leaks in C++ MFC project developed using VC7, Dotnet framework 1.1
- Debugging CArrays
- To detect any 'Enters' pressed
- VC 2005 RC with Loki small object allocator, std::lower_bound, and CompareFixedAllocatorSize
- _beginthread() issues...
- Fatal error when copiling my first program
Visual C++
- Problem with templates
- IShellBrowser::BrowseObject
- use of __value as a variable name in unmanaged c++ code
- Spaces instead of tabs in auto-generated code for MFC projects
- profiler for c++ native makefile in vs .net 2003
- a reference failure
- _findfirst() prototype changes
- Question/problem regarding to templates in C++
- How can I get the CheckedListBox for a Com project?
- VC2005 %50 Slower then VC2003
Deployment Problem
Edwood
One way to examine the statically linked DLLs used by your managed DLL is to use the Depends utility from the Visual Studio 2005 Tools\Bin directory. Run it against your managed DLL and it will list all the DLLs referenced by your DLL or referenced by a DLL your DLL references etc.
To catch dynamically linked libraries, use the Depends profile command to execute whatever program loads your managed code DLL. The Depends utility will track every LoadLibrary call and show you which one(s) worked and which failed.
I think (but am not absolutely certain) that you can copy depends.exe to your Windows 2000 system and run it there successfully.
Another useful tool for diagnosing these kinds of problems is FileMon from SysInternals. http://www.sysinternals.com/Utilities/Filemon.html. Run that tool on your Windows 2000 system and use it to monitor the program that loads your managed Dll. The filemon log should show you the failed attempt to access a file and the name of the file should tell you what you need to deploy..
If I had to guess, you probably have a dependency on the C run time library (e.g., MSVCR80.dll or MSVCM80.dll). http://msdn2.microsoft.com/en-us/library/abx4dbyh.aspx
Mark Olsen
Wooooooow....... good tools. Now I can see the missing DLL, Great!!!
And you are right the missing DLL is like the one you said
Thanks again.
Tutnik.
softgeek
Managed C++, by definition, requires the .NET framework.