Comments on: Visual Studio XML IntelliSense for URL Rewrite 1.1

By: 9h0s7

9h0s7 — Fri, 25 Jun 2010 14:50:57 +0000

I had to add the node to DotNetConfig35.xsd instead of DotNetConfig.xsd on VS 2010 and .net 4

By: Kirk

Kirk — Mon, 14 Jun 2010 11:06:08 +0000

Thanks for posting the update js for vs 2010 install. Works great. Thanks.

By: Visual Studio IntelliSense for URL Rewrite - Scott Forsyth's Blog

Visual Studio IntelliSense for URL Rewrite - Scott Forsyth's Blog — Fri, 04 Jun 2010 13:47:17 +0000

[...] has released a Visual Studio schema update for URL Rewrite which is available as a free quick download. Contrary to the title of the post, the installer [...]

By: ruslany

ruslany — Fri, 23 Apr 2010 20:51:02 +0000

@Barbaros: use the link in the trackback above to get the schema for v2.0.

By: RuslanY Blog

RuslanY Blog — Fri, 23 Apr 2010 20:50:01 +0000

Visual Studio XML IntelliSense for URL Rewrite 2.0…

Last year I published an XML schema for URL Rewrite 1.1 that could be used to enable IntelliSense support when editing rewrite rules in Visual Studio XML editor. Now that the URL Rewrite 2.0 has been released, the old schema will not work for the the n…

By: Barbaros

Barbaros — Thu, 22 Apr 2010 09:16:25 +0000

Any news for v2.0 schema?

By: ruslany

ruslany — Thu, 28 Jan 2010 18:06:01 +0000

@David: The links should work now. There was some glitch in the WP download plugin.

I do not yet have a schema for v2.0. I will try to provide it sometime soon.

By: David

David — Thu, 28 Jan 2010 16:02:32 +0000

The download link doesn’t work for the schema file. Do you have an updated schema for version 2?

By: ruslany

ruslany — Wed, 21 Oct 2009 02:10:49 +0000

@Gene: This is be because the XML schema cache is located in a different location in VS2010. Can you open the UpdateSchemaCache.js and replace this line:

var vs9CommonTools = shell.ExpandEnvironmentStrings( “%VS90COMNTOOLS%” );

with this line:

var vs9CommonTools = shell.ExpandEnvironmentStrings( “%VS100COMNTOOLS%” );

After that try running the script and see if that helps.

By: Gene

Gene — Tue, 20 Oct 2009 20:54:11 +0000

The same issue exists in Visual Studio 2010, but after running the script, no love. Is there an updated version for VS 2010?