Announcement

Collapse
No announcement yet.

Error when calling an aspx page

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Error when calling an aspx page

    I'm trying to call an aspx page that I saw posted. Proof of concept sort of thing.

    I get an error 'Could not determine which version of ASP.NET Web Pages to use.'

    It was suggested that I need to tweak the Web.Config page in the html folder of HS3, but still can't get any aspx pages to work.

    Has anyone run into this, and if so, what's the solution?

    Thanks

    PHP Code:
    <%@ Page Language="VB" %>
    <    html>
    <    body>
    Hello
    </body>
    </    html> 
    Don
    Tags: None
    #2
    Anyone?
    Don

    Comment

      #3
      Is this Windows or Linux?

      Please post your Web.Config file.
      Jon

      Comment

        #4
        Windows 7

        PHP Code:
        <?xml version="1.0"?>
        <!-- 
            Note: As an alternative to hand editing this file you can use the 
            web admin tool to configure settings for your application. Use
            the Website->Asp.Net Configuration option in Visual Studio.
            A full list of settings and comments can be found in 
            machine.config.comments usually located in 
            \Windows\Microsoft.Net\Framework\v2.x\Config 
        -->
        <configuration>
            <appSettings/>
            <connectionStrings/>
            <system.web>

                <!-- 
                    Set compilation debug="true" to insert debugging 
                    symbols into the compiled page. Because this 
                    affects performance, set this value to true only 
                    during development.
                
                <compilation debug="true"/>
                -->
                
                <!--
                    The <authentication> section enables configuration 
                    of the security authentication mode used by 
                    ASP.NET to identify an incoming user. 
                <authentication mode="Windows"/>
            -->
                <!--
                    The <customErrors> section enables configuration 
                    of what to do if/when an unhandled error occurs 
                    during the execution of a request. Specifically, 
                    it enables developers to configure html error pages 
                    to be displayed in place of a error stack trace.
                -->
                <customErrors mode="Off">
                </customErrors>

                <sessionState
                timeout="40"
                />


            </system.web>
        </configuration>
        Don

        Comment

          #5
          As an aside, I couldn't ever configure VS to have the Web page option.
          Don

          Comment

            #6
            That looks the same as mine.

            Have you tried calling test.aspx from Homeseer?

            There does seem something strange with your Homeseer installation as you also could not use the #Include statement?
            Jon

            Comment

              #7
              Yeah, good point. I'm unclear what you are referring to when you asked about 'calling test.aspx from Homeseer'. Could you explain?

              Thanks for your comments


              Originally posted by jon00 View Post

              Have you tried calling test.aspx from Homeseer?

              There does seem something strange with your Homeseer installation as you also could not use the #Include statement?
              Don

              Comment

                #8
                Homeseer provide test.aspx with the installation (located in the html directory)

                Call it as follows:

                http://<your Homeseer IP address>:<optional port number>/test.aspx
                Jon

                Comment

                  #9
                  Yep. That's how I was making the call.

                  Not sure how to troubleshoot this.
                  Don

                  Comment

                    #10
                    Still banging my head against a wall with this. I looked at the MS page describing this issue and it mentions the /html/bin directory holding 'Web page version assemblies'. I took a peek in my bin directory and don't see much of anything associated with dot net. I am wondering if I am missing some binary files, that other people have.

                    Tried files on another HS3 machine, this with XP... all the pages run without any drama. Perplexed.
                    Last edited by donstephens; August 2, 2017, 04:03 PM.
                    Don

                    Comment

                      #11
                      Finally figured this out, at least for me. I edited the Web.Config to add the
                      <add key="webPages:Version" value="2.0.0.0"/>
                      to the appSettings statement. Apparently, HomeSeer needs a restart for the Web.Config file to be read, and I hadn't done that.

                      Also, I think updating HomeSeer overrides the file. That is why it did work and then it didn't.

                      Hope this helps someone with a similar problem.
                      Don

                      Comment

                      Previous template Next
                      Working...
                      X