Table of Contents
Reply to discussion (solution)
Home Web Front-end HTML Tutorial I don't believe no one can solve this problem! _html/css_WEB-ITnose

I don't believe no one can solve this problem! _html/css_WEB-ITnose

Jun 24, 2016 pm 12:12 PM

I downloaded the source code of a website online
There is no problem when debugging it locally
But as soon as I publish it
there is a problem
What is the reason


Normal The screen should be





I think there is something that needs to be changed in
web.config when publishing? ? ? ? ?


Reply to discussion (solution)

Front-end html jquery
The back-end is written in c#, compiled into a dll
and referenced in the front-end

Your server does not support C#

The environment is not configured properly and the script is not parsed successfully.

CSS file is not imported, causing problems

CSS file is not imported, causing problems. Wrong.

The environment is not configured properly and the script is not parsed successfully. I think so too, but how should I match it? Unable to parse dll

Even <%@ Page Language="C#" ....
is out, is it still supported? Otherwise, the file suffix is ​​wrong. I can’t believe that I would make such a low-level mistake

Even <%@ Page Language="C#" ....
has come out, do you still say you support it? Otherwise, the file suffix is ​​wrong. I don’t believe that I would make such a low-level mistake
It’s not a question of support, or what does it mean to be called support? The framework is installed, and this machine is the server
I think it is a configuration problem
If the suffix is ​​wrong, doesn’t HTML support page references?

Check out the configuration of IIS

Check out the configuration of IIS
Haha, how to configure it

Quote from 8th Floor’s reply:

Even <%@ Page Language="C#" ....
has come out, are you still saying you support it? Otherwise, the file suffix is ​​wrong. I don’t believe that I would make such a low-level mistake

It’s not a question of support, or what does it mean to be called support? The framework is installed, and this machine is the server
I think it is a configuration problem
If the suffix is ​​wrong, doesn’t HTML support page references? Unfortunately, the
suffix is ​​aspx

html is only interpreted in the browser

Oops! Don't worry if something goes wrong sometimes! Don’t rush to answer other people’s suggestions first! Read the code clearly yourself!

Quoted from the 9th floor’s reply:

Quoted from the 8th floor’s reply:

Even <%@ Page Language="C#" ....
came out Yes, do you still say you support it? Otherwise, the file suffix is ​​wrong. I don’t believe that I would make such a low-level mistake

It’s not a question of support, or what does it mean to be called support? The framework is installed, and this machine is the server
I think it is a configuration problem
If the suffix is ​​wrong, doesn’t HTML support page references?
Unfortunately,
the suffix is ​​aspx
...
His code structure is originally html suffix
Do I have to change all of these to aspx when publishing, or as long as Can you directly parse aspx instead of html through configuration?
If so
What is his purpose for doing this? ? ? ?

I had a similar problem when I first started learning to debug and use other people’s DISCUZ templates. When index.thml was displayed, the template code was also displayed, which explains this paragraph. The code was not parsed successfully. I checked that some parts of my html code and PHP code did not match well. I don’t know if yours has the same problem. Don’t just look at the index file. It’s useless. It’s all background parsing. After the results come out, check the template.

This is web.config






& lt ;section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/> ;

< section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>

& LT; Section name =" AuthenticationService "Type =" System.Web.configuration.ScriptingAutHentheServiceSect ION, System.web.exTensions, Version = 3.5.0.0, Culture = Neutral, PublicKeytoken = 31BF3856AD36E35 "RequirePerMission =" false" allowDefinition="MachineToApplication"/>

                                         









" "
"
77A5C561934E089" />
                                                                          buildProviders>


                                                          error statusCode="404" redirect="FileNotFound.htm"/>




                                                                                                                                                       "asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
        
      

    

    
      
      
      
      
      

    

    
      
      
    

    
  

  
    
      
        
        
      
      
        
        
        
      
    

  






ule"/> ;
                                                                         < ;remove name="ScriptHandlerFactoryAppServices"/>


           




< assemblyBinding xmlns= "urn:schemas-microsoft-com:asm.v1">


< bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>



                                                                                                            🎜> & lt;/assemblybinding & gt;
& lt;/runtime & gt;
& lt; local = "rent" & gt;
& lt; system.web & gt;
& lt; a Uthorization & gt;
& lt; Alow users = "?" />
                                                       system.web>
                                                                                                                                                       
      
    
  
  
    
      
        
      

    

  
  
    
      
        
      

    

   
  
    
      
        
      

    

  
  
    
      
        
      

    

  
  
    
      
        
      

    

  
  
    
      
        
      

    

  
  
    
      
        
      

    

  
  
    
      
        
      

    

  


看看需要做什么修改

I had a similar problem when I first started learning to debug and use other people’s DISCUZ templates. When index.thml was displayed, the template code was also displayed. This means that this code was not successfully parsed. I checked that it was Some parts of my html code and PHP code don't match well. I don't know if yours has the same problem. Don't just look at the index file. It's useless. They are all the results of background parsing. Check with the template. Bar.
It is indeed used in a nested manner
I checked the references and there is no problem
I have no problem with debugging
But there is a problem as soon as it is released
I think it needs to be modified before publishing. What
I think what should be modified is the content in web.config

Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Hot AI Tools

Undresser.AI Undress

Undresser.AI Undress

AI-powered app for creating realistic nude photos

AI Clothes Remover

AI Clothes Remover

Online AI tool for removing clothes from photos.

Undress AI Tool

Undress AI Tool

Undress images for free

Clothoff.io

Clothoff.io

AI clothes remover

Video Face Swap

Video Face Swap

Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Tools

Notepad++7.3.1

Notepad++7.3.1

Easy-to-use and free code editor

SublimeText3 Chinese version

SublimeText3 Chinese version

Chinese version, very easy to use

Zend Studio 13.0.1

Zend Studio 13.0.1

Powerful PHP integrated development environment

Dreamweaver CS6

Dreamweaver CS6

Visual web development tools

SublimeText3 Mac version

SublimeText3 Mac version

God-level code editing software (SublimeText3)

Hot Topics

Java Tutorial
1663
14
PHP Tutorial
1266
29
C# Tutorial
1239
24
Understanding HTML, CSS, and JavaScript: A Beginner's Guide Understanding HTML, CSS, and JavaScript: A Beginner's Guide Apr 12, 2025 am 12:02 AM

WebdevelopmentreliesonHTML,CSS,andJavaScript:1)HTMLstructurescontent,2)CSSstylesit,and3)JavaScriptaddsinteractivity,formingthebasisofmodernwebexperiences.

The Roles of HTML, CSS, and JavaScript: Core Responsibilities The Roles of HTML, CSS, and JavaScript: Core Responsibilities Apr 08, 2025 pm 07:05 PM

HTML defines the web structure, CSS is responsible for style and layout, and JavaScript gives dynamic interaction. The three perform their duties in web development and jointly build a colorful website.

HTML, CSS, and JavaScript: Essential Tools for Web Developers HTML, CSS, and JavaScript: Essential Tools for Web Developers Apr 09, 2025 am 12:12 AM

HTML, CSS and JavaScript are the three pillars of web development. 1. HTML defines the web page structure and uses tags such as, etc. 2. CSS controls the web page style, using selectors and attributes such as color, font-size, etc. 3. JavaScript realizes dynamic effects and interaction, through event monitoring and DOM operations.

HTML: The Structure, CSS: The Style, JavaScript: The Behavior HTML: The Structure, CSS: The Style, JavaScript: The Behavior Apr 18, 2025 am 12:09 AM

The roles of HTML, CSS and JavaScript in web development are: 1. HTML defines the web page structure, 2. CSS controls the web page style, and 3. JavaScript adds dynamic behavior. Together, they build the framework, aesthetics and interactivity of modern websites.

The Future of HTML: Evolution and Trends in Web Design The Future of HTML: Evolution and Trends in Web Design Apr 17, 2025 am 12:12 AM

The future of HTML is full of infinite possibilities. 1) New features and standards will include more semantic tags and the popularity of WebComponents. 2) The web design trend will continue to develop towards responsive and accessible design. 3) Performance optimization will improve the user experience through responsive image loading and lazy loading technologies.

The Future of HTML, CSS, and JavaScript: Web Development Trends The Future of HTML, CSS, and JavaScript: Web Development Trends Apr 19, 2025 am 12:02 AM

The future trends of HTML are semantics and web components, the future trends of CSS are CSS-in-JS and CSSHoudini, and the future trends of JavaScript are WebAssembly and Serverless. 1. HTML semantics improve accessibility and SEO effects, and Web components improve development efficiency, but attention should be paid to browser compatibility. 2. CSS-in-JS enhances style management flexibility but may increase file size. CSSHoudini allows direct operation of CSS rendering. 3.WebAssembly optimizes browser application performance but has a steep learning curve, and Serverless simplifies development but requires optimization of cold start problems.

HTML vs. CSS vs. JavaScript: A Comparative Overview HTML vs. CSS vs. JavaScript: A Comparative Overview Apr 16, 2025 am 12:04 AM

The roles of HTML, CSS and JavaScript in web development are: HTML is responsible for content structure, CSS is responsible for style, and JavaScript is responsible for dynamic behavior. 1. HTML defines the web page structure and content through tags to ensure semantics. 2. CSS controls the web page style through selectors and attributes to make it beautiful and easy to read. 3. JavaScript controls web page behavior through scripts to achieve dynamic and interactive functions.

HTML: Building the Structure of Web Pages HTML: Building the Structure of Web Pages Apr 14, 2025 am 12:14 AM

HTML is the cornerstone of building web page structure. 1. HTML defines the content structure and semantics, and uses, etc. tags. 2. Provide semantic markers, such as, etc., to improve SEO effect. 3. To realize user interaction through tags, pay attention to form verification. 4. Use advanced elements such as, combined with JavaScript to achieve dynamic effects. 5. Common errors include unclosed labels and unquoted attribute values, and verification tools are required. 6. Optimization strategies include reducing HTTP requests, compressing HTML, using semantic tags, etc.

See all articles