Scott Hanselman's Computer Zen - Intellisense and NAnt .build files in VS.NET

First time here? Check out the site's "greatest hits" or read a post from the archives. Feel free to leave a comment or ask a question, and consider subscribing to the latest posts via RSS or e-mail. Thanks for visiting!

« 作者：Scott Hanselman 首席工程師 | Main | Building MSI files from NAnt and Updatin... »

Intellisense and NAnt .build files in VS.NET

Posted in Nant | XML.

This has been blogged about before here and there, but I wanted to share it as I had to mess with it yesterday.

Getting Intellisquish to work with NAnt .build files in VS.NET:

Copy this file: nant-current.xsd (101.06 KB) to 'C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml' on your system.
In your NAnt build file (I make my with the extension .build) include this xmlns attribute:
<project default="all" basedir="." xmlns="http://nant.sf.net/schemas/nant-0.84.win32.net-1.0.xsd">
When you File|Open your .build file, notice the TINY down arrow on the Open button. Click it, go to Open With...
In Open With, select HTML/XML Editor. There you go, NAnt Build files with Intellisense.

If anyone knows how to tell VS.NET to ALWAYS open .build files with the XML Editor (without messing up any other file types) tell me, and then we can skip steps 3 and 4.

There is also some nice stuff on MSDN about Authoring Custom XML Schemas for use in VS.NET.

Posted at 2004-03-30 11:32 AM by Scott
Comments [9]
Permalink

Tracked by:
http://www.nantz.org/DasBlog/PermaLink.aspx?guid=818a283b-8e49-4f81-8efd-25c5e75... [Pingback]
"Intellisense and NAnt .build files in VS.NET" (吴海燕) [Trackback]
"Enable Intellisense for NANT build files in VS.NET" (Ram Gopinathan's Blog) [Trackback]
"Enable Intellisense for NANT build files in VS.NET" (Ram Gopinathan's Blog) [Trackback]
http://jemos.com/PermaLink,guid,ec3c96d1-8f13-4b73-aaaf-ae95e6b91a23.aspx [Pingback]

Tuesday, March 30, 2004 12:38:06 PM (Pacific Standard Time, UTC-08:00)

Do steps 1 and 2, but then go download VSTweak (http://www.gotdotnet.com/Community/Workspaces/Workspace.aspx?id=b9330ea5-096d-45b7-8a5b-17450d7a0d5a). It allows you to add a custom extension (.build) and have it treated like it was a common extension (.xml). Then when you open .build files, it automatically throws them into the HTML/XML editor.

Travis Illig

Tuesday, March 30, 2004 1:05:39 PM (Pacific Standard Time, UTC-08:00)

Click the "Set as Default" button in the "Open With" dialog.

Chris Bilson

Tuesday, March 30, 2004 4:32:53 PM (Pacific Standard Time, UTC-08:00)

What Chris said.

Sean Malloy

Wednesday, April 07, 2004 9:13:58 AM (Pacific Standard Time, UTC-08:00)

When I follow the steps above, I get squiggly lines below all my property elements; the tooltip says "The active schema does not support the element 'property'." All of my properties work correctly when running NAnt, however.

Anyone know why this is and how to fix it?

Eric

Thursday, April 22, 2004 9:20:00 PM (Pacific Standard Time, UTC-08:00)

Same problem here, may someone help?

Jack

Thursday, August 19, 2004 6:38:22 AM (Pacific Standard Time, UTC-08:00)

It is very easy to create the schema file yourself...just create and run a simple build file as described on my Blog (http://dukeytoo.blogspot.com/2004/08/nant-schema-file-for-vss-2003.html).

(I tried to post it here in the comment, but ASPX compained about dangerous tags. I'm too lazy to escape them out, so...)

Steven Campbell

Thursday, August 19, 2004 12:23:55 PM (Pacific Standard Time, UTC-08:00)

I see you have already been told how to make it the default. Here is a posting from my Blog explaining the whole process.

http://objectsharp.com/Blogs/dave/archive/2004/06/04/575.aspx

Dave Lloyd

Friday, January 14, 2005 8:05:16 AM (Pacific Standard Time, UTC-08:00)

The xsd for Nant is incorrect. (reason for squiggly lines). Inside of the project and target elements, it refers to an element properties of type nant:properties. I think the element name should be property in these two places (and possibly others).

Tim Wilson

Tuesday, January 31, 2006 3:29:01 PM (Pacific Standard Time, UTC-08:00)

Make sure if you have any nant include tasks that the included projects have the same namespace. If not you're likely to encounter an unlikely error: BUILD FAILED - Target 'foobar' does not exist in this project.

See details here:

http://dotnetbkm.blogspot.com/2006/01/nant-files-and-xml-namespaces.html