Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. s JavaScript in ASP.NET page trouble

s JavaScript in ASP.NET page trouble

Scheduled Pinned Locked Moved ASP.NET
csharpjavascripthtmlasp-netdatabase
5 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    Bounz
    wrote on last edited by
    #1

    Hi. I have index.aspx with the following content: <%@ Page Language="C#" ContentType="text/html" %> Untitled Document Hooray Here stm31.js and mainmenu.js are scripts, which draws menu. When i try to open this page in browser i get an error in browser and my menu is not displayed (but "Hooray" is). The source of generated page is: Untitled Document Hooray And when I make a simple .htm with this html-code I can view my menu in browser. What I do wrong in my asp script and what i have to do to correct my mistake? -- Digitally yours, Bounz

    G 1 Reply Last reply
    0
    • B Bounz

      Hi. I have index.aspx with the following content: <%@ Page Language="C#" ContentType="text/html" %> Untitled Document Hooray Here stm31.js and mainmenu.js are scripts, which draws menu. When i try to open this page in browser i get an error in browser and my menu is not displayed (but "Hooray" is). The source of generated page is: Untitled Document Hooray And when I make a simple .htm with this html-code I can view my menu in browser. What I do wrong in my asp script and what i have to do to correct my mistake? -- Digitally yours, Bounz

      G Offline
      G Offline
      Guffa
      wrote on last edited by
      #2

      You are missing the html tag and the title tag. The language property of the script tag is deprecated in htlm 4, just use the type propery. --- b { font-weight: normal; }

      B 1 Reply Last reply
      0
      • G Guffa

        You are missing the html tag and the title tag. The language property of the script tag is deprecated in htlm 4, just use the type propery. --- b { font-weight: normal; }

        B Offline
        B Offline
        Bounz
        wrote on last edited by
        #3

        Hm-m. Even with html and title tag i have the same error.. Now asp script looks like: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %> Untitled Page !! -- Digitally yours, Bounz

        B 1 Reply Last reply
        0
        • B Bounz

          Hm-m. Even with html and title tag i have the same error.. Now asp script looks like: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %> Untitled Page !! -- Digitally yours, Bounz

          B Offline
          B Offline
          Bounz
          wrote on last edited by
          #4

          I found some bug (or it's no bug) but this page cannot be displayed properly because of some symbols, which appears in html-code, returned by IIS. So, we have the first line:  As you see, before we have 3 odd symbols. Where are they from and how can I get them out of there? -- Digitally yours, Bounz

          B 1 Reply Last reply
          0
          • B Bounz

            I found some bug (or it's no bug) but this page cannot be displayed properly because of some symbols, which appears in html-code, returned by IIS. So, we have the first line:  As you see, before we have 3 odd symbols. Where are they from and how can I get them out of there? -- Digitally yours, Bounz

            B Offline
            B Offline
            Bounz
            wrote on last edited by
            #5

            I've solved my problem. Trouble was in page encoding.. windows-1251 nedeed.. :) -- Digitally yours, Bounz

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups