Browse by Tags
All Tags »
IntelliSense (
RSS)
If by any chance you are not seeing intellisense in your JavaScript or HTML after installing Visual Studio 2010 Beta 2 you might be running into a known bug that we can show you how to fix. The bug is related to user settings which we don’t remove when Beta 1 is uninstalled. One particular setting under HKCU\Software\Microsoft\VisualStudio\10.0\HTML Editor\ TargetFriendlyName . For Beta 2, this setting does not match the schema’s we know about. As a result, JScript intellisense will fail to load and most items will be missing in markup as well. The minimum fix is to manually repair the TargetFriendlyName setting in the registry (change it to be just "XHTML 1.0 Transitional”) but due to the fact that more settings could be affected the recommended...
Scalable Vector Graphics (SVG) is W3C standard language for describing two-dimensional vector and mixed vector/raster graphics in XML. Firefox 3+, Opera 9+ and Safari 3+ support SVG rendering. Unfortunately, Internet Explorer 8 does not support SVG natively and requires a plug-in. There a plug in from Adobe (although support was discontinued this year) as well as few pulg-ins listed in Wikipedia article on SVG . SVG element is part of upcoming HTML 5 standard which allows inline SVG in HTML documents. Inline SVG is not yet fully supported in modern browsers so you probably still want to use <object> element for now. For example: < html > < head > < title > SVG test </ title > </ head > < body > <...
In yesterday’s post , I alluded to a simple include extension method that I like to use when I don’t care about designer support. In a comment, Andrew asked if I could share the code for it, so here it is. I never liked the regular way of including user controls in WebForms and how they require a registration and a declaration, both of which are more verbose than they need to be. A plain #include would work but is a little outdated (and if I’m not mistaken it’s not even available by default in IIS7). My Include method is quite similar to MVC’s RenderPartial except that it doesn’t deal with view data. It’s a plain and simple include. Just give it the relative path to a user control: <% this .Include( "Header.ascx" ); %> Here’s...
jQuery 1.3 was released a little over a month ago. The 1.3 release adds exciting features such as selector performance improvements, "live events" where events can be bound to both current and future elements, and more. Version 1.3.2 was released a few days ago and fixes some bugs include one involving selector performance in IE. I just wanted to let everyone know that we now have VSDoc files for all of the 1.3 releases. You can download them from the jQuery Downloads page ... A refresher on how to use the file can be found here or here . Here's one of the new functions in action... Hope this helps! Jeff King Program Manager Visual Studio Web Tools Read More...
I've been reading through the 70 or so comments on our last 2 jQuery posts. There have been a lot of great questions. Apologies for not being able to answer them sooner (I was busy preparing for Dev Connections). Instead of answering them inline with the comments, I'll try to paraphrase the popular issues here and answer them centrally. 1. I have a ton of Content Pages, do I need to put script references for IntelliSense in each one? No, you do not need to repeat the script references on each content page. Visual Studio 2008 will auto-detect the presence of a master page and scan for references in that file. Thus, placing references in the master page is all you need to do. 2. I put a vsdoc reference in...
Jeff King just announced the release of a patch for Visual Studio 2008 that enables the IDE to find the –vsdoc.js file without requiring the developer to reference it. To give some context, a documentation file (basically the same file as the runtime script but with XML documentation annotations ) can be provided to help Visual Studio provide IntelliSense. Until now, you had to reference that extra file explicitly, usually within a server-side <% if %> block so that the file never gets included at runtime. Now that this patch shipped, this is no longer necessary and Visual Studio is going to be able to find the –vsdoc.js file for any script file that is referenced, whether that is through a ScriptManager ScriptReference: or using a plain...
Last week I mentioned we would be releasing a Hotfix to accompany our new jQuery VSDoc file . This Hotfix is now available at the MSDN Code Gallery . Here's a direct download link for this small (2MB) patch: http://code.msdn.microsoft.com/KB958502/Release/ProjectReleases.aspx?ReleaseId=1736 I want to emphasize that this patch is intended for all JavaScript files, not just those related to jQuery . Generally, we will opportunistically look for documentation files related to the script file. For example, given "mylibrary.js", we will search in the same directory for: mylibrary -vsdoc .js, then if we don't find it we will search for... mylibrary .debug .js, then if we don't find it we will search for... mylibrary.js The idea...
In SP1 for Visual Studio 2008 and Visual Web Developer 2008, C# introduced a new feature to provide 'live' reporting of compilation errors. Unfortunately, the introduction of this functionality also introduced a bug where in certain cases, false C# compilation errors appear in the Error List for ASP.NET Website projects. Specifically the following is a list of issues you may have experienced due to this bug in SP1: If you have a breakpoint in a code-behind file. On project open, you get incorrect errors in the Error List for that code-behind file (e.g. – button1 is not declared). These errors do not go away until you open that code-behind file. Once you open the code-behind file, the errors go away. When you open a code-behind file,...
A while back we updated IntelliSense to not fail when referencing jQuery. However, getting IntelliSense for chained calls and rich summary/parameter hints still required adding special comments to a few thousand lines of jQuery. If you didn't have the time, you could download such a file from friendly members of the community such as James and Brennan . As part of our new partnership with jQuery , yesterday we announced the availability of the official IntelliSense documentation file. As you can see, our friends at jQuery have added a new download link for Visual Studio at http://docs.jquery.com/Downloading_jQuery#Download_jQuery . You can also download the file directly from http://code.jquery.com/jquery-1.2.6-vsdoc.js . As you might guess...
IntelliSense documentation files for jQuery just got published on jquery.com . This enables great IntelliSense at design-time for jQuery in Visual Studio 2008. It goes without saying that this file should only be used at design-time and never at runtime. For the moment, in order to ensure that, you can include the file from an “if (false)” server code block. We’re also working on a much better solution. Many, many thanks to John Resig, Scott Cate and Jeff King for making that possible. 1.2.6: http://code.jquery.com/jquery-1.2.6-vsdoc.js Latest release (currently just a copy of 1.2.6): http://code.jquery.com/jquery-latest-vsdoc.js Read More...
More Posts
Next page »