Re: [Nant-users] Specifying -logger in the build file
- Original Message - From: "Douglas R. Steen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 03, 2003 6:57 AM Subject: [Nant-users] Specifying -logger in the build file > I'm using the -logger:NAnt.Core.MailLogger commandline option so that > I'll get an email with the build output, but since I want that to happen > every time I run my build file, I'd really like to specify it somehow in > the build file itself. > > Right now I'm just running it from a batch file, which I suppose is > okay, and I know that I could create another build file which would call > the first build file, but both of those solutions seem like hacks. > Isn't there a simple setting that allows me to set > commandline options? Nope, there isn't right now but we'll consider it for a future release ... Gert --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Specifying -logger in the build file
Douglas, you can log to a default text log, and then write a target that will send email to you. For example: You can also use nant.onfailure target to customize the message depending on the outcome of the build: ... see above You can now specify a different list of emails that receive the failure and success messages. If you want to get creative, you can parse the log file before sending it in an email, keeping only interesting bits and format them in the body of the message. d. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas R. Steen Sent: Wednesday, December 03, 2003 6:57 AM To: [EMAIL PROTECTED] Subject: [Nant-users] Specifying -logger in the build file I'm using the -logger:NAnt.Core.MailLogger commandline option so that I'll get an email with the build output, but since I want that to happen every time I run my build file, I'd really like to specify it somehow in the build file itself. Right now I'm just running it from a batch file, which I suppose is okay, and I know that I could create another build file which would call the first build file, but both of those solutions seem like hacks. Isn't there a simple setting that allows me to set commandline options? Douglas R. Steen Boulder, CO --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] ant => nant conversion tool?
I have some ant build scripts that I want to translate to nant, do you know of any tool(s) out there that would make my job easier? Thanks in advance, Rodrigo --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
Re: [Nant-users] MSBuilds bashing the foundation of Nant?
MS Build was presented at the PDC and there's alot of stuff on the web if you search in Goolge for MSBuild. I've read a few blogs where MS guys are saying that Ant / NAnt is the inspiration, but that they're having to roll their own due to licence issues with the opensource projects. I get the impression that they (MS Devs)would have liked to embrace & extend NAnt, but then lawyers got involved and canned that idea. Given that the Msft R&D spend is sooo big, I can't see this product not being a success. Unfortunately it may also stunt the growth of NAnt - which is a shame as the work the NAnt devs do is superb. The good news for end users is that MSBuild is XML so a bit of XSLT magic should be enough to port a NAnt build to an MSBuild :) The good(ish) news for Ant/NAnt devs is that that they can claim the glory for getting there first. Rgds Chris Whellams == This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. == --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] MSBuilds bashing the foundation of Nant?
Dianna, I have read a lot of talk about MSBuild here before, and none of it has given me the impression that MSBuild will "bash the foundation of NAnt." In fact, I think that the two environments will complement each other very well. Both will have very similar features. And they may be able to work together. There has been talk about the legalities interoperation between the two products. The Mono user space will still need an opensource .NET build tool. NAnt already exists to fill this need. It is for this reason above all others that I do not see NAnt going anywhere anytime soon. I expect that it will soon become an integral part of an opensource .NET IDE, and it may already be one (I am not too knowledgeable about such things). While I understand that you pessimism with MSBuild vs. NAnt stems from other Microsoft business practices, I doubt that we will see them throw their weight around in this area. Microsoft has always been very dependent on developers. Many of the first products that they developed were developer tools. Pissing off .NET developers (even opensource ones) is not a route I think that they will take. The project manager for the Visual Studio group at Microsoft has shed light on this issue in the past, and he has written many fond things about NAnt and its user community. I will not try to rehash what he has already said here. It is best to consult the archives. -Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Whellams, Chris Sent: Wednesday, December 03, 2003 7:56 AM To: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Subject: Re: [Nant-users] MSBuilds bashing the foundation of Nant? MS Build was presented at the PDC and there's alot of stuff on the web if you search in Goolge for MSBuild. I've read a few blogs where MS guys are saying that Ant / NAnt is the inspiration, but that they're having to roll their own due to licence issues with the opensource projects. I get the impression that they (MS Devs)would have liked to embrace & extend NAnt, but then lawyers got involved and canned that idea. Given that the Msft R&D spend is sooo big, I can't see this product not being a success. Unfortunately it may also stunt the growth of NAnt - which is a shame as the work the NAnt devs do is superb. The good news for end users is that MSBuild is XML so a bit of XSLT magic should be enough to port a NAnt build to an MSBuild :) The good(ish) news for Ant/NAnt devs is that that they can claim the glory for getting there first. Rgds Chris Whellams == This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation. == --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] MSBuilds bashing the foundation of Nant?
First, I must admit that being a *Windows Developer* has been good to me and my family for all these years. So, I've always try to look at things from all point of view and try carefully not to *bash* or *judge* MS blindly. But, this is a *bit* too much. I think MS should at least *thanks* the developers who devoted most of theirs free-time (I assume weekends included) to make life easier for most (if not all) of the .NET developers especially for the .NET *newbies*. So, if any of the MS people out there that listening to this message, please give the credits to the developers that helped open the door for the MSBuild. Just my $.02 Thanks, Daniel "Give credits to those who really deserved it" Nguyen -Original Message- From: Harvey Green [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 11:19 PM To: [EMAIL PROTECTED] Subject: Re: [Nant-users] MSBuilds bashing the foundation of Nant? Got this from Microsoft's VS roadmap page... http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx#whidbey Product Build Historically, developers have struggled when trying to map a complicated build infrastructure into the Visual Studio IDE. Roadblocks traditionally center around the inability to fully customize or understand what happens when a project is built within the development environment; the failure to reproduce a build within a build lab environment where Visual Studio is not likely to be present; and the limitations of a build system that was not optimized to model entire products, but rather single projects. The Whidbey release of Visual Studio will radically improve this area of software development by introducing a new build engine called MSBuild. Key design goals for MSBuild include: delivering a file format that is well-documented and backed up by a published XML schema definition; making the MSBuild engine an integral part of the .NET Framework redistributable; allowing developers to customize, augment or completely redefine the build process; and providing seamless integration with the Visual Studio Whidbey IDE. First, MSBuild will introduce a new XML-based file format that is simple to understand and easy to extend. The MSBuild file format will enable developers to fully describe what artifacts need to be built, as well as how they need to be built under different configurations. In addition, the file format will enable developers to author reusable rules which can be factored into separate files so that builds can be done consistently across different projects within a product. Second, MSBuild will ship as a core part of the Whidbey .NET Framework redistributable. This shift in philosophy will allow developers to rely on the MSBuild infrastructure regardless of IDE presence and licensing issues. In addition, by providing MSBuild class libraries as a core part of the .NET Framework, developers will be able to create and debug components of a customized MSBuild process using the managed language of their choice. Third, MSBuild will be completely transparent with regards to how it processes and builds software. All build steps will be explicitly expressed in the XML project file regardless of whether it was authored by hand or auto-generated by the Visual Studio Whidbey IDE. This also means that Visual Studio no longer treats any part of the "F5" build experience as a black box. A user can now understand, replicate, edit, remove, or augment any part of the build process. Finally like its predecessors, MSBuild will be fully integrated into the Visual Studio Whidbey IDE. This tight integration will enable developers to take advantage of all the built-in productivity features Visual Studio offers, while allowing developers to scale, customize, and adapt the Whidbey build system to their unique infrastructure needs. Deployment and Operations Dianna wrote: > Do you think that MS has now Borg ed the builds process? > > Recently they announced the new MSBuilds framework. > > Anyone know about this and how good its supposed to be? > > Eric Frank Cotter > --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-
[Nant-users] Using the License tag
Title: Using the License tag I have a 3rd party control that I'm trying to create a buildfile for. I have found the license tag, but have no idea where to actually put it in the "build" process! Before the csc tag, as an argument to the csc tag...??? Any help in getting this to its correct place would be greatly appreciated. Also, random thoughts on any conventions (or "must be"s) on the naming of the output and/or licensetarget attributes welcome too. Thanks! Jeffrey A. Block Sr. Systems Analyst The Timken Company [EMAIL PROTECTED] (330) 471-3268 ** PLEASE NOTE: The above email address has recently changed from a previous naming standard -- if this does not match your records, please update them to use this new name in future email addressed to this individual. This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **
Re: [Nant-users] Using the License tag
Hi, * Block, Jeffrey A. (Jeff) wrote on 03.12.2003 (14:10): > process! Before the csc tag, as an argument to the csc tag...??? Any help in Before the csc task. It generates a license file which then must be included as a resource in the csc task. -sa -- sa at programmers-world dot com http://www.livingit.de Bookmarks online: http://www.mobile-bookmarks.info Soon available in english Have people realized that the purpose of the fortune cookie program is to defuse project tensions? When did you ever see a cheerful cookie, a non-cynical, or even an informative cookie? Perhaps inadvertently, we have a channel for our aggressions. This still begs the question of whether the cookie releases the pressure or only serves to blunt the warning signs. Long live the revolution! Have a nice day. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] RE:Editing .build files w/syntax hilighting in VS.NET
Title: RE:Editing .build files w/syntax hilighting in VS.NET I've read through the archives and followed previous advice regarding how to get .build files fully recognized by VS.NET with Intellisense/validation. I've configured it such that VS.NET recognizes .build files as XML, and the opened files have syntax hilighting. However, I can't get Intellisense/validation working. Here's what I've done: 1. I went to http://nant.sourceforge.net/schema/ and downloaded the latest schema (nant-20030903.xsd) 2. I saved the nant-20030903.xsd file into my C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml folder 3. I edited my tag in my .build file to be: http://nant.sf.net/schema/'> Now when I restart VS.NET and open the .build file, I get an error(in the schema view, as opposed to the source view), stating: "The XML Designer encountered the following error while reading this file: Document Element must be schema. Please return to source view and correct these errors." I also tried using the tag like this: http://nant.sourceforge.net/schema/"/> I got the same error as above from the schema view. Does anyone know what's going on? Thanks in advance! Jeff Jeffrey L. White Software Build Manager Knight Financial Products (212) 209-1419 DISCLAIMER This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Trading Group may, at its discretion, monitor and review the content of all e-mail communications.
Re: [Nant-users] RE:Editing .build files w/syntax hilighting in VS.NET
I'm also having similar problems with nant schema. I couldn't get it to work using the method you described. There's a workaround: if you add the schema to the same project (maybe just the same solution - I don't remember) as your build files - the intellisense works (more or less - the schema is not very complete at the moment). Jarek - Original Message - From: "White, Jeffrey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 03, 2003 10:03 PM Subject: [Nant-users] RE:Editing .build files w/syntax hilighting in VS.NET > I've read through the archives and followed previous advice regarding how to get .build files fully recognized by VS.NET with Intellisense/validation. I've configured it such that VS.NET recognizes .build files as XML, and the opened files have syntax hilighting. However, I can't get > Intellisense/validation working. > > Here's what I've done: > 1. I went to http://nant.sourceforge.net/schema/ and downloaded the latest schema (nant-20030903.xsd) > 2. I saved the nant-20030903.xsd file into my C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml folder > 3. I edited my tag in my .build file to be: > > Now when I restart VS.NET and open the .build file, I get an error(in the schema view, as opposed to the source view), stating: "The XML Designer encountered the following error while reading this file: Document Element must be schema. Please return to source view and correct these errors." > > I also tried using the tag like this: > http://nant.sourceforge.net/schema/"/> > > I got the same error as above from the schema view. > > Does anyone know what's going on? Thanks in advance! > > Jeff > > Jeffrey L. White > Software Build Manager > Knight Financial Products > (212) 209-1419 > > > DISCLAIMER > This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of > this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. > E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. > NOTICE REGARDING PRIVACY AND CONFIDENTIALITY > Knight Trading Group may, at its discretion, monitor and review the content of all e-mail communications. > --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] MSBuilds bashing the foundation of Nant?
First off let me say I agree with the point of this post. I mention in my Open Source .Net book MS should thank the Apache Ant developers who had a really cool idea. But I can understand MS wanting to fully control such a critical part of their product. As I mention on my blog (http://www.nantz.org/dasBlog/default.aspx?date=2003-11-13), I think the Open Source community just needs to create a product to transform any build file to any other build file. Much of this work already exists on SF and just needs an organizer. Brian Nantz www.nantz.org "It is amazing what you can accomplish if you do not care who gets the credit." -Harry S Truman
RE: [Nant-users] Validation of build files in VS.NET
Title: Validation of build files in VS.NET Hi Gerrod, Save the XSD from the webpage into this folder: C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml This is the secret place where VS.NET looks for schemas. Then open an XML file in the VS editor, and click inside it. Go to the Properties window, and set targetSchema using the dropdown to the nant schema, which it will now find. (This just puts in the correct xmlns attribute.) Then validation and intellisense should work fine. The XML editing experience is still sometimes a bit quirky. In VS Whidbey (the next version), the XML editor is being rewritten from scratch and is greatly improved - and hopefully it will be easier to associate a schema with your document as well. Do ping me if you still have problems. Dan -- msbuild team -- danmose[at]microsoft.com "This posting is provided "AS IS" with no warranties, and confers no rights." :-) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gerrod ThomasSent: Monday, December 01, 2003 6:34 PMTo: '[EMAIL PROTECTED]'Subject: [Nant-users] Validation of build files in VS.NET Hi everyone, I'm trying to get VS.NET to use the NAnt schema for validation of my build files, but I can't seem to get it to work. I've searched around but haven't found a solution that works, so I'm hoping someone out there has had the same problem and managed to fix it. I've tried a number of things but I figured that the best one would be to declare my build file as follows - http://nant.sourceforge.net/schema/nant-current.xsd" name="UBO" default="compile"> Unfortunately I don't get IntelliSense. Also when I ask VS to validate my build file I get the error: Visual Studio could not locate a schema for this document. Validation can only ensure this is a well formed XML document and cannot validate the data against a schema. Does anyone have a solution for this? Thanks, Gerrod PS - please reply direct to me as subscribing to the list just times out :-( RECIPIENTS ARE REMINDED THAT THIS E-MAIL MESSAGEIS STRICTLY CONFIDENTIAL AND INTENDED ONLY FOR USEBY THE ADDRESSEE UNLESS OTHERWISE INDICATED. Investment Data Technologies Pty Ltd advise that they: - accept no liability for any abusive, defamatory, obscene, illegal, oroffensive material contained in this e-mail message- do not monitor the content of any e-mail messages sent fromInvestment Data Technologies- do not authorise or condone the sending of abusive, defamatory,obscene, illegal, or offensive material by their employees and contractors- cannot guarantee that this e-mail message is secure and will not beintercepted by a third party.
RE: [Nant-users] RE:Editing .build files w/syntax hilighting in VS.NET
Title: RE:Editing .build files w/syntax hilighting in VS.NET Line 3 should say something like that: http://nant.sf.net/schema/nant-20030903.xzd Thanks, Oleg From: White, Jeffrey [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2003 1:04 PM To: '[EMAIL PROTECTED]' Subject: [Nant-users] RE:Editing .build files w/syntax hilighting in VS.NET I've read through the archives and followed previous advice regarding how to get .build files fully recognized by VS.NET with Intellisense/validation. I've configured it such that VS.NET recognizes .build files as XML, and the opened files have syntax hilighting. However, I can't get Intellisense/validation working. Here's what I've done: 1. I went to http://nant.sourceforge.net/schema/ and downloaded the latest schema (nant-20030903.xsd) 2. I saved the nant-20030903.xsd file into my C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml folder 3. I edited my tag in my .build file to be: http://nant.sf.net/schema/'> Now when I restart VS.NET and open the .build file, I get an error(in the schema view, as opposed to the source view), stating: "The XML Designer encountered the following error while reading this file: Document Element must be schema. Please return to source view and correct these errors." I also tried using the tag like this: http://nant.sourceforge.net/schema/"/> I got the same error as above from the schema view. Does anyone know what's going on? Thanks in advance! Jeff Jeffrey L. White Software Build Manager Knight Financial Products (212) 209-1419 DISCLAIMER This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me and permanently delete the original and any copy of any e-mail and any printout thereof. E-mail transmission cannot be guaranteed to be secure or error-free. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. NOTICE REGARDING PRIVACY AND CONFIDENTIALITY Knight Trading Group may, at its discretion, monitor and review the content of all e-mail communications. --- The information contained in this e-mail message, and any attachment, is confidential and for use solely by the intended recipient. If you have received this message in error, please delete this message immediately. Although Moody's KMV makes every effort to protect its computing environment from malicious code, Moody's KMV is not responsible for any virus or other type of suspect code that may be transferred via this e-mail message.
[Nant-users] MSBuilds bashing the foundation of Nant?
Title: Message Let me start this by saying "I'm sorry if you thought I was bashing". It was a poor attempt at humor :) I live and breath the MS theme. I have drank the cool aide years ago. Your comments Daniel are most excellent. The contributors should all be proud that MS would take notice of your efforts and purse this as a viable facet to their fabulous development environment. I just hope that they integrate some kind of MMC or IIS via Share Point for monitoring. I heard that MSBuilds will integrate security as well into the builds processnice :) And with COM+ being exposed as a webservice..heheheh..some nice things are possible "delayed signing service...". Bravo Nant contribs and bravo MS. Eric F. Cotter
Re: [Nant-users] Validation of build files in VS.NET
I just wish the (Xml Schema) noNamespaceSchemaLocation hint was honored in the editor. :) Oh, that would make it so easy... http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/htm/xsd_ref_7ld1.asp BTW. The NAnt schema file generated by the task doesn't create array and collection task elements correctly. The file is not complete and doesn't correctly represent the buildfile structure. It will get better, I just have to fix the task (which I'm working on this exact moment for the next release). Also, this xsd will never be able to validate the build file as it cannot know certain things about how the file will be expended when it is read by nant. It cannot assert type information, as an example. > > > > - Original Message - > > > > From: Dan Moseley > > > > To: [EMAIL PROTECTED] > > > > Sent: Wednesday, December 03, 2003 12:22 PM > > > > Subject: RE: [Nant-users] Validation of build files in VS.NET > > > > > > > > > > > > Hi Gerrod, > > > > Save the XSD from the webpage into this folder: > > > > C:\Program Files\Microsoft Visual Studio .NET > > > > 2003\Common7\Packages\schemas\xml > > > > This is the secret place where VS.NET looks for schemas. > > > > > > > > Then open an XML file in the VS editor, and click inside it. Go to the > > > > Properties window, and set targetSchema using the dropdown to the nant > > > > schema, which it will now find. (This just puts in the correct xmlns > > > > attribute.) Then validation and intellisense should work fine. > > > > > > > > The XML editing experience is still sometimes a bit quirky. In VS > > Whidbey > > > > (the next version), the XML editor is being rewritten from scratch and > > is > > > > greatly improved - and hopefully it will be easier to associate a > schema > > > > with your document as well. > > > > > > > > Do ping me if you still have problems. > > > > > > > > Dan -- msbuild team -- danmose[at]microsoft.com > > > > > > > > > > --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
Re: [Nant-users] RE:Editing .build files w/syntax hilighting in VS.NET
In the next nightly build there will be a new target called "deploy-schema"
that will copy the schema file to the vs.net (7.0 and 7.1) schema
directories. That should help a little :)
Please note that the targetNamespace is in the form of
"http://nant.sf.net/schemas/${project.name}-${project.version}.${nant.platfo
rm.name}.${nant.settings.currentframework}.xsd", which for me became
"http://nat.sf.net/schemas/nant-0.84.win32.net-1.0.xsd"; on the latest cvs
tree. The nightly build will replace the version with the date, I believe.
But the point is that there is no one namespace; it is always changing as
the source code is changing...
> > - Original Message -
> > From: Blokhin, Oleg
> > To: White, Jeffrey ; [EMAIL PROTECTED]
> > Sent: Wednesday, December 03, 2003 4:41 PM
> > Subject: RE: [Nant-users] RE:Editing .build files w/syntax hilighting in
> > VS.NET
> >
> > Line 3 should say something like that:
> > http://nant.sf.net/schema/nant-20030903.xzd
> > Thanks,
> > Oleg
> >
> > From: White, Jeffrey [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, December 03, 2003 1:04 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: [Nant-users] RE:Editing .build files w/syntax hilighting in
> VS.NET
> >
> > I've read through the archives and followed previous advice regarding
how
> to
> > get .build files fully recognized by VS.NET with
Intellisense/validation.
> > I've configured it such that VS.NET recognizes .build files as XML, and
> the
> > opened files have syntax hilighting. However, I can't get
> > Intellisense/validation working.
> > Here's what I've done:
> > 1. I went to http://nant.sourceforge.net/schema/ and downloaded the
latest
> > schema (nant-20030903.xsd)
> > 2. I saved the nant-20030903.xsd file into my C:\Program Files\Microsoft
> > Visual Studio .NET 2003\Common7\Packages\schemas\xml folder
> > 3. I edited my tag in my .build file to be: > name='ProjName' default='build' xmlns='http://nant.sf.net/schema/'>
> > Now when I restart VS.NET and open the .build file, I get an error(in
the
> > schema view, as opposed to the source view), stating: "The XML Designer
> > encountered the following error while reading this file: Document
Element
> > must be schema. Please return to source view and correct these errors."
> > I also tried using the tag like this:
> > > target-ns="http://nant.sourceforge.net/schema/"/>
> > I got the same error as above from the schema view.
> > Does anyone know what's going on? Thanks in advance!
> >
>
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
___
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
