Title: Message
You need to regenerate you schema file (.xsd).  Run the nant build with deploy-schema as the target.  This will recreate the schema file and copy to the correct location.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Zarger
Sent: Thursday, October 07, 2004 9:56 AM
To: [EMAIL PROTECTED]
Cc: Curtis Zarger
Subject: RE: [Nant-users] IntelliSense for NAnt build files
Importance: Low

I successfully installed the IntelliSense as described, but I've lost my NAntContrib tasks in the process.  They are no longer recognized as valid tasks; VS.Net underlines the NAntContrib tasks and on mouseover indicates that the active schema does not support the element. 

 

I've re-copied the NAntContrib bin contents into the NAnt bin folder, but haven't been able to recover use of the NAntContrib tasks, or get them into the schema with the <nantschema> tasks.

 

Any thoughts would be appreciated.

 

Curt Zarger

 

-----Original Message-----
From: Matt Hulse [mailto:[EMAIL PROTECTED]
Sent:
Thursday, September 16, 2004 12:22 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Nant-users] IntelliSense for NAnt build files

 

IntelliSense Lives!!!

 

Thanks for the replies.

 

I had typed in the xmlns as I'd seen many times but the problem ended up being that the namespace in the xsd did not match the one I was typing in.  Because of this the intellisense never worked.  I used the <nantschema> task and created my own xsd with the target namespace that I had been trying to use (http://nant.sf.net/schemas/nant-0.85.win32.net-1.0.xsd.) This works great.  I can even see my custom and contrib. tasks in IntelliSense.  Awesome!

 

Thanks to Edwin and Bill for your help.

 

Long live the NAnt Community!!!

 

Matt Hulse

 

 

 

This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.

Reply via email to