Don't comment the topic if you have a new question.
You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.
By Matthew, 9 March, 2010
Hi
I downloaded the sources of serial port component. After successufully building the component, I try to run a debug version of, I get the following:
System.IO.FileLoadException was unhandled
Message="Could not load file or assembly 'Gurux.Serial, Version=5.0.0.2, Culture=neutral, PublicKeyToken=cee95795a537823a' or one of its dependencies. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)"
Source="ModbusApp"
FileName="Gurux.Serial, Version=5.0.0.2, Culture=neutral, PublicKeyToken=cee95795a537823a"
What's wrong?
Br,
Matt
Hi, Matt!
You can try and run the following bat, before starting your test application.
Note: this must be run with Administrator rights. (Start command prompt as Administrator).
Press enter in console, after you receive the exception.
Notepad opens with error log. In that error log you can see what component is missing.
zipped trace.bat
Keep us posted!
BR,
Mikko
Hi again,
Below is the error log that I received.
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = C:\Temp\WindowsFormsApplication16\bin\Debug\Gurux.Serial.dll
AssemblyDirectory = C:\Temp\WindowsFormsApplication16\bin\Debug\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Temp\WindowsFormsApplication16\bin\Debug\Gurux.Serial.dll.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC90.DebugCRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.DebugCRT.DLL.
INFO: Attempt to probe manifest at C:\Temp\WindowsFormsApplication16\bin\Debug\Microsoft.VC90.DebugCRT.DLL.
INFO: Attempt to probe manifest at C:\Temp\WindowsFormsApplication16\bin\Debug\Microsoft.VC90.DebugCRT.MANIFEST.
INFO: Attempt to probe manifest at C:\Temp\WindowsFormsApplication16\bin\Debug\Microsoft.VC90.DebugCRT\Microsoft.VC90.DebugCRT.DLL.
INFO: Attempt to probe manifest at C:\Temp\WindowsFormsApplication16\bin\Debug\Microsoft.VC90.DebugCRT\Microsoft.VC90.DebugCRT.MANIFEST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Activation Context generation failed.
End Activation Context Generation.
________________________________________
Matt
Hi Matt,
it just contains the 64-bit release version of VC++ runtime library; but it does not contain the debug version of VC++ runtime library.
To make your debug version application run on the target machine, copy the debug version VC++ runtime library to the deployed machine.
You can find the debug version VC++ runtime library in the “redist” subdirectory of your VC++ installed directory.
("C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\redist")
Or then you can just build release version from the wrapper.
You can still debug COM component.
Br,
Mikko
Hi there,
i think PublicKeyToken=cee95795a537823a' or one of its dependencies. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tools.
Hi michael123,
Thanks for your reply. You are right about sxstrace.exe. It is a great tool for solving reference problems.
However, in this case trace shows the problem.
Microsoft.VC90.DebugCRT is missing.
See below.
Br,
Mikko
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference Microsoft.VC90.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Activation Context generation failed.
End Activation Context Generation.
Matt, try this
error log
debug symbols
But I have installed
about Vcredist_x64
Public key
Public key