exe not executed
-
Hello, I am using an .exe file at my client but it gives me the error "The application failed to initialize properly(0xc0000135).Click on OK to terminate the aplication". Earlier I used to use the same .exe file which is made in the debug folder of project for other clients but I didnt face this issue.Can you please tell what must be the problem. The OS is Windows 2000 for client and I am using Windows XP. Pritha
You probably need to install the .Net Framework on that computer. I think the highest version of the .Net Framework that will work on Windows 2000 is 2.0. By the way, Google is your friend.
-
Hello, I am using an .exe file at my client but it gives me the error "The application failed to initialize properly(0xc0000135).Click on OK to terminate the aplication". Earlier I used to use the same .exe file which is made in the debug folder of project for other clients but I didnt face this issue.Can you please tell what must be the problem. The OS is Windows 2000 for client and I am using Windows XP. Pritha
-
The application developer used the .Net Framework, just install the framework and Re-run the application Remember to Reboot HAPPY WORKING
-
Hello, Thanks for your replies. But I have executed .exe on the PCs which do not have .Net Framework. Are you sure that I need to load .Net Framework Pritha
-
Hello, I am using an .exe file at my client but it gives me the error "The application failed to initialize properly(0xc0000135).Click on OK to terminate the aplication". Earlier I used to use the same .exe file which is made in the debug folder of project for other clients but I didnt face this issue.Can you please tell what must be the problem. The OS is Windows 2000 for client and I am using Windows XP. Pritha
0xc0000135 is the error code you get when your system does not include the expected version of .NET .NET has many versions (from 1.0 up to 4.0), they can coexist (you can have many on one system), and your EXE by default needs a very specific version; the good approach is to have all of them available on your system. Some Windows versions have some .NET versions preinstalled; XP and Vista often include 1.1, 2.0 and 3.0; which are present can be seen by looking in C:\Windows\Microsoft.NET\Framework; the folder names (all but one) represent installed versions. Some more details are available here[^]. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
-
0xc0000135 is the error code you get when your system does not include the expected version of .NET .NET has many versions (from 1.0 up to 4.0), they can coexist (you can have many on one system), and your EXE by default needs a very specific version; the good approach is to have all of them available on your system. Some Windows versions have some .NET versions preinstalled; XP and Vista often include 1.1, 2.0 and 3.0; which are present can be seen by looking in C:\Windows\Microsoft.NET\Framework; the folder names (all but one) represent installed versions. Some more details are available here[^]. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
Thanks for your answer. Does the same hold true for different versions of Excel. Say if I have included a certain version of Excel. Microsoft Excel 5.0 Object Library added as a reference in my project then it should work with the client only if it has that version of Object Library Pritha
-
Thanks for your answer. Does the same hold true for different versions of Excel. Say if I have included a certain version of Excel. Microsoft Excel 5.0 Object Library added as a reference in my project then it should work with the client only if it has that version of Object Library Pritha
Excel is native code, not managed code, so it should always run fine, even without .NET present. Excel automation through PIA (Primary Interop Assembly) may be different, and different versions of Office may require different PIA versions, I don't know any details. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
-
Excel is native code, not managed code, so it should always run fine, even without .NET present. Excel automation through PIA (Primary Interop Assembly) may be different, and different versions of Office may require different PIA versions, I don't know any details. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).
-
you're welcome. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read formatted code with indentation, so please use PRE tags for code snippets.
I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).