Application Error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • lotus18
    Contributor
    • Nov 2007
    • 865

    Application Error

    Hello World

    I created a simple program in C# .Net 2005 and I compiled it and have its .exe file. This works well in my computer. But when I copied it to some pc, the .exe file works well in some pc but not all. In some pcs it displays The application failed to initialize property (0xc0000135). Click on OK to terminate application. What's wrong with it?

    Rey Sean
  • DrBunchman
    Recognized Expert Contributor
    • Jan 2008
    • 979

    #2
    This error occurs when you don't have the .NET framework installed on the machine.

    Dr B

    Comment

    • lotus18
      Contributor
      • Nov 2007
      • 865

      #3
      Originally posted by DrBunchman
      This error occurs when you don't have the .NET framework installed on the machine.

      Dr B
      Some computers that I tried are using XP. I'm not sure about this but I think XP has atleast .net framework 1.0.

      Rey Sean

      Comment

      • DrBunchman
        Recognized Expert Contributor
        • Jan 2008
        • 979

        #4
        You should be able to check in the IIS console whether you've got the framework installed (remember these machines may not have IIS installed either).

        I'm not sure whether what you say about XP is correct.

        Dr B

        Comment

        • lotus18
          Contributor
          • Nov 2007
          • 865

          #5
          I created an error handling method in which Splash is the name of my form.

          Code:
          public Splash()
          		{
          			try
          			{
          				InitializeComponent();
          			}
          			catch
          			{
          				MessageBox.Show("The application failed to initialize property " +
          					"(0xc0000135). Click OK to download .NET framework.", "Unable To" +
          					"Load Components", MessageBoxButtons.OK, MessageBoxIcon.Information);
          				System.Diagnostics.Process.Start("http://msdn.microsoft.com/en-us/netframework/aa569263.aspx");
          				Application.Exit();
          			}
          
          			
          		}
          Rey Sean

          Comment

          • Plater
            Recognized Expert Expert
            • Apr 2007
            • 7872

            #6
            There may be some other error causing that, you should only be displaying that message to the particular exception that triggered the fault.

            The fact that you can get "that far" would insuate that they do in fact have .NET installed, and there is something else wrong with your code.
            Possibly you are using a custom object that they do not have a .DLL for or you are using .net2.0 components and they only have .net1.1.

            Comment

            • lotus18
              Contributor
              • Nov 2007
              • 865

              #7
              Originally posted by Plater
              There may be some other error causing that, you should only be displaying that message to the particular exception that triggered the fault.

              The fact that you can get "that far" would insuate that they do in fact have .NET installed, and there is something else wrong with your code.
              Possibly you are using a custom object that they do not have a .DLL for or you are using .net2.0 components and they only have .net1.1.
              So what should I do? Please give me solution with this problem. Thanks.

              Rey Sean

              Comment

              • DrBunchman
                Recognized Expert Contributor
                • Jan 2008
                • 979

                #8
                Have you checked whether your deployment machines have the correct version of .NET installed? If not then install it on one and see if your exe works. If that works then you have your solution.

                Or, as Plater said, do you have any dll's referenced by this application that might not be installed?

                Dr B

                Comment

                Working...