Variations on this trick would include using compiler directives like #if FALSE, or /* block comments */ to exclude the section of code. Now, for the real script tag, we can use the static functions that ASP.NET provides to emit the proper path: language: htmlįor ASP.NET WebForms, you would use the Server.ApplyAppPathModifier() function in place of Url.Content(). Just make sure that the script is referenced relative to the physical file in which this tag exists. We can use the relative path here, since this will never make it across the wire. Since the code is unreachable, it will be ignored and will not be checked for definite assignment as per the C# spec (§5.3.3.1).Įxtending this idea a little bit further, we can add our long-sought-after IntelliSense: language: html Take these lines for example: language: htmlĪfter being transformed by ASP.NET into a pure C# listing, this code will be compiled into an assembly. This means that we can use a technique similar to conditional comments in order to ignore sections of HTML, but still have it recognized as part of the HTML document. The little bit of magic required to make everything work in our favor is the fact that Visual Studio will treat everything outside of code sections as though it were one continuous block of HTML. aspx files living in one folder, or I had to live without JavaScript IntelliSense. We would have minified scripts for production (by default), VSDoc scripts for IntelliSense (in design mode), and full source scripts for debugging (when DEBUG is defined or a debugger is attached).Īt this point, I used to conclude that I had to live with all of my. If it could, then we would just write a chunk of code to do the virtual path transformation based on current mode. Since we can’t use a virtual path, and we can’t use a relative path, we are stuck.Īdd on top of this that we often need to switch between different scripts for auto-completion, debugging, and production and you start to see the direness of the situation.Īt the center of the issue is the fact that Visual Studio can’t execute code in the editor in order to “know” where a script will come from. This in effect means that we can’t use the “virtual path” to reference the same script from everywhere in our app. We can’t use runat="server" on script tags, because ASP.NET has repurposed this format in order to include server-side code into the page. “Oh, my goodness gracious!” So where does that leave us? “I’ll just add a run-at attribute, so that ASP.NET transforms the path for me…” “I’ll just add my script here, and presto!”
You have probably gone through these steps: If you are like me, you have probably had trouble in the past trying to get JavaScript IntelliSense to work well in Visual Studio.
View otac0n on GitHub Getting IntelliSense in JavaScript files in ASP.NET MVC The Problem
0 kommentar(er)
