CSS validation in Visual Studio: ignore file - css

In my ASP.NET Core project I have a third party CSS file which causes Visual Studio 2022 to show many warnings. How can I tell VS to ignore this file for CSS validation?
I am aware that I could disable CSS validation altogether (Options->Text Editor->CSS-Advanced->Enable validation: False), but that is not what I need.

Related

F12 Go To Definition not working for CSS in CSHTML files - VS2017

I am working on my first Asp.net Core 2.0 Mvc web site.
Normally I use web forms, but I'm trying something new.
In my .cshtml files I cannot F12 or right click and "go to definition" on CSS classes. I thought something may be wrong with my install but I was able to open up a web forms application and it works just fine from an ASPX page.
I have seen topics from 2013 about this issue, but no solutions.
I have installed web essentials, but that didn't work either.
This is something I use regularly and it is hard to do it manually especially when you are looking at a minified CSS file.
I'm using Visual Studio 2017 Pro.
The ReSharper extension for Visual Studio adds this feature.
https://www.jetbrains.com/help/resharper/ReSharper_by_Language__CSS__Navigation.html#navigation-within-css-file

Is it possible to update Visual Studio's CSS validation?

I'm using VS2013 and am getting a lot of incorrect feedback on CSS3 syntax (particularly flex elements). Is the validation schema baked into a VS release or can it be updated somehow?
I had this problem in the past with Visual Studio 2010 (only CSS 2.1).
The short answer is yes, it is possible to add new schemas and use them instead of the default ones.
You can take a look at the visual studio gallery, but I cannot confirm if this will work on later versions of Visual Studio.
http://visualstudiogallery.msdn.microsoft.com/7211bcac-091b-4a32-be2d-e797be0db210

What is the purpose of Antlr package in Visual Studio 2013 ASP.NET project?

The ASP.NET (web forms) project template in Visual Studio 2013 includes several packages. I'm trying to figure out which ones are essential (may need to create a separate question for this). The post at http://blogs.msdn.com/b/webdev/archive/2013/10/16/asp-net-features-in-new-project-templates-in-visual-studio-2013.aspx explains the purpose of some of them, but I cannot figure out which need Antlr serves. Can someone clarify?
It is a transitive dependency declared in the WebGrease package, where it is used for a CSS lexer and parser.
Also relevant for Visual Studio 2015 (ASP.NET MVC 5)
Bundling and minification in the ASP.Net templates is implemented in Microsoft.AspNet.Web.Optimization, which depends upon WebGrease, which itself depends upon Antlr.
So if you want to take advantage of ASP.Net template's built-in bundling and minification, you need them all.

unrecognized tag-prefix in my project in asp.net control

I'm having a major problem in my project that all the asp.net controls having error of unrecognized tag-prefix because of the all the internal tag has been converted to lower case and intellisense is not working on these control but working on html controls, this project is working fine on other system but not on my system. Other projects on my system are working fine.
I have done the following things but didn't find the solution for it:
Deleted reflected schema from vs folder
Add tag for the asp control in web.config
Formatted my system.
Added the intellisense .js file.
Done the VS repair
Hoping for the positive solution. Thanks in advance
Delete the C:\Users\UserName\AppData\Roaming\Microsoft\VisualStudio\10.0 folder:
Visual Studio 2010 RTM intellisense not working for asp.net tags

CodeFile vs CodeBehind

What is the difference between CodeFile="file.ascx.cs" and CodeBehind="file.ascx.cs" in the declaration of a ASP.NET user control?
Is one newer or recommended? Or do they have specific usage?
CodeBehind: Needs to be compiled (ASP.NET 1.1 model). The compiled binary is placed in the bin folder of the website. You need to do a compile in Visual Studio before you deploy. It's a good model when you don't want the source code to be viewable as plain text. For example when delivering to a customer to whom you don't have an obligation to provide code.
CodeFile: You provide the source file with the solution for deployment. ASP.NET 2.0 runtime compiles the code when needed. The compiled files are at Microsoft.NET[.NET version]\Temporary ASP.NET Files.
I'm working with an Application Project in Visual Studio Express 2012 For Web and using .NET 4.0. In the code behind files for my login and change password pages I found a situation where I needed both CodeBehind and CodeFile in the declaration.
If I don't add a code file reference like
CodeFile=login.aspx.cs
The web page doesn't parse and the browser displays a parser error. It doesn't matter whether I compile the project or not.
If I don't add a code behind reference like
CodeBehind=login.aspx.cs
References to Security classes like MembershipUser fail both at compile time and when attempting to use intellisense with an error like "The type or namespace MembershipUser cannot be found". I have added a reference to System.Web.ApplicationServices as required by the .Net 4.0 framework.
I should add that these troublesome files are running in an application within the website created using the IIS Application tool. When I open the website from Visual Studio I have no difficulty with parser errors or reference errors. This confusion only occurs when I open the application as a project in Visual Studio.
Codebehind file need to compile before run but in src we dont need to compile and then run.. just save the file.

Resources