I'm working on a page using <canvas>, which is a HTML5 tag, in Visual Web Developer Express Edition 2008, and the validator in the HTML editor is telling me it's an invalid tag. That's because it's set to validate against XHTML 1.0 Transitional. I'd prefer for it to not do that and tell me what's valid or invalid based on the HTML5 doctype, but I can't find anywhere in the preferences that suggests this would be possible.
Is there a way to tell Visual Studio to validate against HTML5, or add a new spec reference manually? I'd prefer not to have to go in and add tags manually, which appears to be the only option at the moment.
It looks like the Visual Web Developer team solved the problem by adding HTML5 support themselves:
http://blogs.msdn.com/webdevtools/archive/2009/11/18/html-5-intellisense-and-validation-schema-for-visual-studio-2008-and-visual-web-developer.aspx
You all probably know that new HTML 5 standard is coming. We made a new intellisense schema that you can add to VS 2008 or VWD Express 2008 and get intellisense and validation on HTML 5 elements.
For Visual Studio 2010 you'll want to install the Web Standards Update for Visual Studio 2010 SP1:
It updates the HTML5 intellisense and validation to reflect the latest
W3C specifications and fixes some bugs bugs in the current SP1 support
for HTML5. Also JavaScript intellisense it updated to reflect many of
the new browser capabilities such as Geolocation and DOM storage.
Finally, this update adds comprehensive CSS3 intellisense and
validation based on the latest specifications from W3C.
For Visual Studio 2008, Microsoft has provided an updated version of the HTML 5 validation schema and intellisense in the Visual Studio Gallery.
HTML 5 Intellisense
The updated schema was posted by Mikhail Arkhipov, the same Microsoft employee who wrote the blog post linked in Rahul's answer.
I created a validation schema that you're free to use:
http://johndyer.name/post/2009/07/21/HTML5-XHTML5-Validation-Schema-for-Visual-Studio-2008.aspx
This is now included in Visual Studio 2010 SP1
You can define your own validation standards.
You need to add the file to the folder in VS install, and add to the registry.
This is the description I used (HTML and CSS have a very similar approach): http://blogs.msdn.com/mikhailarkhipov/archive/2007/10/19/how-to-create-custom-css-intellisense-schema-in-visual-studio-2005-and-2008.aspx
Related
I am using the Visual Studio TFS 2017 Power Tools to apply some changes to a few of my organisation's TFS work item templates. As expected, the work item templates have two form layout elements - one for the Visual Studio IDE form and the other for the corresponding Web form.
I've had no issue implementing, previewing and validating the changes specific to the Visual Studio IDE form. However, I'm unable to do similar for the changes that are specific to the Web forms and that makes me rather uneasy, as I'd like to also review and validate my changes before importing them to the Live environment. Is there any way I can achieve this before importing my changes?
Remember back in CRM 2011 days, there is this XrmPageTemplate.js file from CRM SDK? Visual Studio will give you nice JavaScript intellisense if you refer to this file from your JavaScript. My question is how do you do the same for CRM 2015? Thanks.
On GitHub you can find the Definitely Typed project containing TypeScript definition files, among which those for Dynamics CRM.
Add the definition file to your web project and name it, say, "Xrm.intellisense.ts". Reference it in your Javascript file by adding the following line at the top of the page. (You will probably need to adjust the path.)
/// <reference path="/Scripts/References/XrmPage.intellisense.ts"/>
Intellisense will work great with Resharper.
I am using a separate javascript file to put my React JS JSX in. When I use the example given by the documents, I get tons of Visual Studio warnings and ugly squiggly lines..
I cannot figure out a way around this.. Pretty much a deal breaker for React JS.
Visual Studio 2012 was released before ReactJs, so you can't really blame them for not supporting it.
There is some visual studio stuff here:
http://reactjs.net/
You can see support for tooling being asked here:
https://github.com/reactjs/React.NET/issues/3
with Web Essentials being one of the prime picks for asking for support (might want to add your votes!)
If you are using Resharper it might be added in the next release, JetBrains is looking to add it into WebStorm
https://youtrack.jetbrains.com/issue/WEB-10136
This is because you're essentially putting html into your javascript. I found this after a quick google search and might fix your problem: https://visualstudiogallery.msdn.microsoft.com/d65d6b29-6dd7-4100-81b1-609e5afce356
The page mentions: "Visual Studio currently doesn't have native JSX syntax support. You can edit .jsx files in regular VS JavaScript editor for now and vote for adding native JSX support in Visual Studio here (the most requested feature in WE)."
We recently started using Telerik Reporting. Some users use the Telerik Report Designer, while I use Visual Studio 2012. Is there a way to import their trdx reports into my Visual Studio class library?
This is currently not supported and in all honesty would be unnatural and tedious task for Telerik to do if they were to do it (create .net class from xml file). I believe they did it one way(VS -> xml) as in most cases devs would create a base/template report that regular users can modify.
I am creating a SharePoint 2010 feature in Visual Studio 2010.
While ReSharper is a valuable tool for writing code, it reports lots of errors (all server-relative image references, master page reference, ContentPlaceHolderID's referring to the master page and so on) in .aspx layout definitions. I had to exclude the master page from ReSharper completely, as it was hanging the VS process - however, the errors were reported before as well.
Is there a 'clever' way of configuring it to correctly parse those files?
As mentioned earlier, R# has offers no support for SharePoint Application- and MasterPages. The issue is because SharePoint is using an other approach to reference assembies and because of the SharePoint specific implementation of the ASP.NET virtual path provider. So R# isn't able to locate all the required dependencies which are required to render an entire SharePoint site.
JetBrains will have to reproduce the SharePoint Designer behavior.
Thorsten
ReSharper 7 (still in beta) supports SharePoint now. ReSharper 7 understands SharePoint-specific master pages, resources, style sheets and JavaScript files.