|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Program can't run: "The application has failed to start because its side-by-side configuration is inI have this application of mine which works well. It even used to work on Vista. (I work on XP most of the time). There are some ManagedC++ assemblies in the project. Now when I try to start the project under vista, when I try to access classes in the ManagedC++ assemblies I get this error: ========================================== Exception : System.IO.FileLoadException Message : Could not load file or assembly 'NScribe, Version=1.0.2553.30928, Culture=neutral, PublicKeyToken=null' 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 for more detail. (Exception from HRESULT: 0x800736B1) Source : NovaMindEditor Help : OSVersion : Microsoft Windows NT 6.0.5600.0 Thread : Stack : at NovaQuickStart.Program.StartApp(String[] args) at NovaQuickStart.Program.Main(String[] args) in C:\Development\Development\Windows\NovaQuickStart\Program.cs:line 59 -------- Caused by Exception -------- Exception : System.Runtime.InteropServices.COMException Message : The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail. (Exception from HRESULT: 0x800736B1) Source : Help : Stack : ========================================== Any ideas? "Lloyd Dupont" <net.galador@ld> wrote Sounds like an issue with the SxS config (aka manifest). VC8 shared> -------- Caused by Exception -------- > Exception : System.Runtime.InteropServices.COMException > Message : The application has failed to start because its side-by-side > configuration is incorrect. Please see the application event log for more > detail. (Exception from HRESULT: 0x800736B1) CRTs take advantage of OS Fusion support to bind to the appropriate version. Did you take a look at the event log? On XP SP2+ & 2003+ you should see a message indicating what exactly is wrong with the manifest. You may take a look at the manifests with resource editor (just open or export the resource of type RT_MANIFEST in the consuming DLL). To diagnose native DLL loading problems you can also enable NT loader snaps (there's gflags.exe in the Debugging Tools for Windows or you can use the (undocumented) ShowSnaps variable : {,,ntdll.dll}*((char*)_ShowSnaps)=1 in the VC debugger -- assuming you have symbols loaded for ntdll.dll) -hg I don't have any manifest file ....
I mean there are some in the /debug & /release of my C++ project, but none in my solution output directory Show quote "Holger Grund" <holger.gr***@remove.ix-n.net> wrote in message news:%23K6IG23KHHA.1280@TK2MSFTNGP04.phx.gbl... > "Lloyd Dupont" <net.galador@ld> wrote > >> -------- Caused by Exception -------- >> Exception : System.Runtime.InteropServices.COMException >> Message : The application has failed to start because its side-by-side >> configuration is incorrect. Please see the application event log for more >> detail. (Exception from HRESULT: 0x800736B1) > > Sounds like an issue with the SxS config (aka manifest). VC8 shared > CRTs take advantage of OS Fusion support to bind to the appropriate > version. Did you take a look at the event log? On XP SP2+ & 2003+ > you should see a message indicating what exactly is wrong with the > manifest. > > You may take a look at the manifests with resource editor (just open > or export the resource of type RT_MANIFEST in the consuming DLL). > > To diagnose native DLL loading problems you can also enable NT > loader snaps (there's gflags.exe in the Debugging Tools for Windows > or you can use the (undocumented) ShowSnaps variable : > {,,ntdll.dll}*((char*)_ShowSnaps)=1 in the VC debugger -- assuming > you have symbols loaded for ntdll.dll) > > -hg > "Lloyd Dupont" <net.galador@ld> wrote The 2005 version of the toolchain will merge the files into the resources>I don't have any manifest file .... > I mean there are some in the /debug & /release of my C++ project, but none > in my solution output directory > of the PE image. You can open the EXE/DLL file with the resource editor and see whether there's a RT_MANIFEST resource. -hg Haha..
thanks for the tip! Show quote "Holger Grund" <holger.gr***@remove.ix-n.net> wrote in message news:%232fcn4kLHHA.420@TK2MSFTNGP06.phx.gbl... > "Lloyd Dupont" <net.galador@ld> wrote > >>I don't have any manifest file .... >> I mean there are some in the /debug & /release of my C++ project, but >> none in my solution output directory >> > The 2005 version of the toolchain will merge the files into the resources > of the PE image. You can open the EXE/DLL file with the resource editor > and see whether there's a RT_MANIFEST resource. > > -hg > BTW, there is something weird happening.
When I build the thing and give it to my colleague, everythings work. However when he builds it, it doesn't work. He use the same project! Any idea why that should be? Show quote "Holger Grund" <holger.gr***@remove.ix-n.net> wrote in message news:%232fcn4kLHHA.420@TK2MSFTNGP06.phx.gbl... > "Lloyd Dupont" <net.galador@ld> wrote > >>I don't have any manifest file .... >> I mean there are some in the /debug & /release of my C++ project, but >> none in my solution output directory >> > The 2005 version of the toolchain will merge the files into the resources > of the PE image. You can open the EXE/DLL file with the resource editor > and see whether there's a RT_MANIFEST resource. > > -hg >  |
|||||||||||||||||||||||
Other interesting topics