{"id":1131,"date":"2006-09-22T18:10:00","date_gmt":"2006-09-22T23:10:00","guid":{"rendered":"http:\/\/blogs.devhorizon.com\/reza\/?p=1131"},"modified":"2006-09-22T18:10:00","modified_gmt":"2006-09-22T23:10:00","slug":"vsnet-intellisense-for-build-files-in-nant","status":"publish","type":"post","link":"https:\/\/blogs.devhorizon.com\/reza\/2006\/09\/22\/vsnet-intellisense-for-build-files-in-nant\/","title":{"rendered":"VS.NET Intellisense for .build files in NAnt"},"content":{"rendered":"

If you have ever worked with NAnt<\/A> , you probably know that there is an xsd for .build files that provides intellisense in VS.NET 2003. After you add a task dll ( In my case NAnt.SharePoint.Task.dll) or <\/SPAN>install a newer version of NAnt , there are some manual steps required to make VS recognizes the new schema. Instead of the manual process, you can get NAnt itself to update\/generate its schema for the internal use of VS.NET 2003 by creating a build file and calling the command line as described below:<\/P>
\n

1) Create UpdateCreateSchema.build file with the following NAnt snippet and save the file in for example c:
\nantGen folder :<\/P>
\n

<\/o:p><\/P>
\n

<\/o:p><\/P>
\n


\n

 <\/SPAN>xml<\/SPAN> <\/SPAN>version<\/SPAN>=”1.0″<\/SPAN> <\/SPAN>encoding<\/SPAN>=”utf-8″<\/SPAN> <\/SPAN>?><\/SPAN>
<<\/SPAN>project<\/SPAN> <\/SPAN>name<\/SPAN>=”<\/SPAN><\/SPAN> <\/SPAN>UpdateCreateSchema“<\/SPAN> <\/SPAN>default<\/SPAN>=”genschema”>
    <\/SPAN> <\/SPAN>might be different in your installation–><\/SPAN><\/SPAN><\/P>
\n

    <<\/SPAN>property<\/SPAN> <\/SPAN>name<\/SPAN>=”SchemaFile”<\/SPAN> <\/SPAN>value<\/SPAN>=”C:Program FilesMicrosoft Visual Studio .NET 2003Common7PackagesschemasxmlNAnt.xsd”\/>
    <<\/SPAN>target<\/SPAN> <\/SPAN>name<\/SPAN>=”genschema”>
        <<\/SPAN>nantschema<\/SPAN> <\/SPAN>output<\/SPAN>=”${SchemaFile}”<\/SPAN> <\/SPAN>target-ns<\/SPAN>=”http:\/\/nant.sf.net\/schemas\/nant.xsd”\/>
    <\/< SPAN>target<\/SPAN>>
<\/< SPAN>project<\/SPAN>><\/SPAN><\/SPAN>    <\/SPAN><\/P><\/BLOCKQUOTE>
\n

2) Assuming Nant has been properly added to Path variable, open a command prompt and change directory to c:
\nantGen . Call the following command line:<\/o:p><\/P>
\n

<\/SPAN><\/P>
\n


\n

 <\/SPAN>nant file: UpdateCreateSchema.build<\/P><\/BLOCKQUOTE>
\n

3) Now that you have deployed the latest version of NAnt.xsd file to the C:Program FilesMicrosoft Visual Studio .NET 2003Common7Packagesschemasxml folder , you must go through all of your build files in your project and <\/P>
\n


\n

a.Make VS.NET recognize your .build file as an XML file (If already done, skip this step then ): <\/o:p><\/P>
\n

In “Solution Explorer”, right-click a .build file and choose “Open With”. In the “Open With” dialog, select “HTML\/XML Editor” and click the “Set as Default” button. Enable intellisense for each .build file.<\/P>
\n

b.When file is opened by the “HTML\/XML Editor” , in the properties window , set the targetSchema to the newly updated\/generated Nant.xsd<\/P><\/BLOCKQUOTE>
\n

4) Boom. You’ll get intellisense. Enjoy!<\/P><\/SPAN><\/SPAN><\/p>\n","protected":false},"excerpt":{"rendered":"

If you have ever worked with NAnt , you probably know that there is an xsd for .build files that provides intellisense in VS.NET 2003. After you add a task dll ( In my case NAnt.SharePoint.Task.dll) or install a newer version of NAnt , there are some manual steps required to make VS recognizes the new schema. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-1131","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/posts\/1131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/comments?post=1131"}],"version-history":[{"count":0,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/posts\/1131\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/media?parent=1131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/categories?post=1131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/tags?post=1131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}