RE: [nant-dev] Patch for 1156702
Gert, I guess I'll just have to keep a private copy on NAnt with these changes in it. We have over 100 csproj files (in about 30 solutions) to build our entire project. The solution task was the easy way to still have just one file that listed the project properties (the .csproj file) for each project that is used by both the developer and the automated build process. Keeping two files in sync (the csproj file and a seprate NAnt build file using the compiler tasks) is just not feasible. Our need was to be able to have pdb files for the release build so we could use tools like ncover. We discovered that VS.NET does not support the pdbonly option directly os the solution task did not either. Anyway - thanks Brian From: Gert Driesen [mailto:[EMAIL PROTECTED]Sent: Sat 3/5/2005 8:43 AMTo: Walker, Brian; nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] Patch for 1156702 Brian, I'm afraid this is not something we'll support in the solution task. If we start adding switches like this one, then we end up with something that is no longer controllable. If you really need lots of flexibility, then I'd suggest using our individual compiler tasks. I've just added support for the different debug types to cvs. Before this change, our compiler tasks only supported either full debug output or no debug output at all. Ireally hope you understand ! We might look into a more configurable solution task after the 0.85 release, but no promises there ... Gert From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Walker, BrianSent: vrijdag 4 maart 2005 19:22To: nant-developers@lists.sourceforge.netSubject: [nant-dev] Patch for 1156702 This is a patch for bug 1156702. It adds the releasesymbols attribute to the solution task. If set to true and a project in the solution is set to not generate debug information (DebugSymbols is false) then it sets the debug setting to /debug:pdbonly instead of /debug-. This will generate the pdb file but otherwise leave the assembly as a release build (no debuggable attribute added). Brian Walker
[nant-dev] [ nant-Bugs-1145670 ] Solution Circular Reference Error
Bugs item #1145670, was opened at 2005-02-21 19:49 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1145670group_id=31650 Category: Tasks Group: 0.85 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Jeff Voigt (jeffvoigt) Assigned to: Gert Driesen (drieseng) Summary: Solution Circular Reference Error Initial Comment: In regards to the Solution Task: When the solution file has two projects that reference each other, a StackOverflowException is thrown. This results in a JIT Debugging error (0x800405a6) to appear in the automated build process, and the log file will only contain the message fatal stack overflow. With the -debug+ flag on when running the build file, you will see Loading referenced project... messages alternating between the two circular referenced projects. This will continue until a stack overflow occurs. (See attached file) It is valid for two projects to reference each other. The Visual Studio IDE handles this gracefully, it would be nice if nant could too. -- Comment By: Gert Driesen (drieseng) Date: 2005-03-08 18:59 Message: Logged In: YES user_id=707851 This is now fixed in CVS. We now fail gracefully in case of circular project references. Thanks for the report ! -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1145670group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] debug=true/full and DEBUG
I am wondering about another issue that I initially thought might be helped bythe change below, but it turned out not quite. I think this has been asked before (a long time ago), but I figured I'd ask again. Currently (in cvs), the csc task sets the DEBUG symbol if debug is true, Full, or PdbOnly. That is fairly limiting in the first two cases and I think conceptually "wrong" in the last case. By setting DEBUG, many conditionally compiled functions are included in the compiled assembly. In the PdbOnly case, that is probably not what is desired. Someone using PdbOnly probably wants a "release" style build but with a pdb file. They will instead get all their DEBUG stuff included (Debug.Writeline, Debug.Assert, etc). Our situation is slightly different. We would like to turn on the debug build (to include debugging symbols), but *not* define DEBUG. In VS.NET project files, I believe it's possible to control debug symbols separately from compilation symbols such as DEBUG. We've wished for a while that this was possible in the csc task. Any thoughts on perhaps another entry in the DebugOutput enum that would allow this sort of situation? Or some other workaround? Thanks!! From: Gert Driesen [mailto:[EMAIL PROTECTED]Sent: Sat 3/5/2005 8:43 AMTo: Walker, Brian; nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] Patch for 1156702 [snip] I've just added support for the different debug types to cvs. Before this change, our compiler tasks only supported either full debug output or no debug output at all. [snip]
RE: [nant-dev] debug=true/full and DEBUG
Hi, I agree that it would've been better to not implicitly set symbols, but instead leave it up to the build authors to use the define attribute for this purpose. I'm not sure whether its a good idea to introduce such a (breaking) change. We could ofcourse not define any symbols when the "debug" attribute is set to Full, PdbOnly orNone. What do you think ? Gert From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erv WalterSent: dinsdag 8 maart 2005 20:29To: Gert Driesen; nant-developers@lists.sourceforge.netSubject: [nant-dev] debug=true/full and DEBUG I am wondering about another issue that I initially thought might be helped bythe change below, but it turned out not quite. I think this has been asked before (a long time ago), but I figured I'd ask again. Currently (in cvs), the csc task sets the DEBUG symbol if debug is true, Full, or PdbOnly. That is fairly limiting in the first two cases and I think conceptually "wrong" in the last case. By setting DEBUG, many conditionally compiled functions are included in the compiled assembly. In the PdbOnly case, that is probably not what is desired. Someone using PdbOnly probably wants a "release" style build but with a pdb file. They will instead get all their DEBUG stuff included (Debug.Writeline, Debug.Assert, etc). Our situation is slightly different. We would like to turn on the debug build (to include debugging symbols), but *not* define DEBUG. In VS.NET project files, I believe it's possible to control debug symbols separately from compilation symbols such as DEBUG. We've wished for a while that this was possible in the csc task. Any thoughts on perhaps another entry in the DebugOutput enum that would allow this sort of situation? Or some other workaround? Thanks!! From: Gert Driesen [mailto:[EMAIL PROTECTED]Sent: Sat 3/5/2005 8:43 AMTo: Walker, Brian; nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] Patch for 1156702 [snip] I've just added support for the different debug types to cvs. Before this change, our compiler tasks only supported either full debug output or no debug output at all. [snip]
[nant-dev] [ nant-Bugs-1159348 ] Building web projects copies all project dlls
Bugs item #1159348, was opened at 2005-03-08 12:51 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 Category: Tasks Group: None Status: Open Resolution: None Priority: 5 Submitted By: Curtis Wensley (cwensley) Assigned to: Nobody/Anonymous (nobody) Summary: Building web projects copies all project dlls Initial Comment: I have a solution with quite a few projects, mostly class libraries and also a web project. Everything compiles fine, but the output of all the class libraries are copied to the bin\ folder of the web project, even if they do not have a reference to them. VS.NET only copies the dll's of the projects that the web project references in the solution, not everything. When deploying this, all of these will be included as well, which is not the desired effect. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] debug=true/full and DEBUG
That would work great! I agree that whatever is done, it should be non breaking to existing true/false settings. From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 2:45 PM To: Erv Walter; nant-developers@lists.sourceforge.net Subject: RE: [nant-dev] debug=true/full and DEBUG Hi, I agree that it would've been better to not implicitly set symbols, but instead leave it up to the build authors to use the define attribute for this purpose. I'm not sure whether its a good idea to introduce such a (breaking) change. We could ofcourse not define any symbols when the debug attribute is set to Full, PdbOnly orNone. What do you think ? Gert From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erv Walter Sent: dinsdag 8 maart 2005 20:29 To: Gert Driesen; nant-developers@lists.sourceforge.net Subject: [nant-dev] debug=true/full and DEBUG I am wondering about another issue that I initially thought might be helped bythe change below, but it turned out not quite. I think this has been asked before (a long time ago), but I figured I'd ask again. Currently (in cvs), the csc task sets the DEBUG symbol if debug is true, Full, or PdbOnly. That is fairly limiting in the first two cases and I think conceptually wrong in the last case. By setting DEBUG, many conditionally compiled functions are included in the compiled assembly. In the PdbOnly case, that is probably not what is desired. Someone using PdbOnly probably wants a release style build but with a pdb file. They will instead get all their DEBUG stuff included (Debug.Writeline, Debug.Assert, etc). Our situation is slightly different. We would like to turn on the debug build (to include debugging symbols), but *not* define DEBUG. In VS.NET project files, I believe it's possible to control debug symbols separately from compilation symbols such as DEBUG. We've wished for a while that this was possible in the csc task. Any thoughts on perhaps another entry in the DebugOutput enum that would allow this sort of situation? Or some other workaround? Thanks!! From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Sat 3/5/2005 8:43 AM To: Walker, Brian; nant-developers@lists.sourceforge.net Subject: RE: [nant-dev] Patch for 1156702 [snip] I've just added support for the different debug types to cvs. Before this change, our compiler tasks only supported either full debug output or no debug output at all. [snip]
[nant-dev] [ nant-Bugs-1159348 ] Building web projects copies all project dlls
Bugs item #1159348, was opened at 2005-03-08 21:51 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 Category: Tasks Group: None Status: Open Resolution: None Priority: 5 Submitted By: Curtis Wensley (cwensley) Assigned to: Nobody/Anonymous (nobody) Summary: Building web projects copies all project dlls Initial Comment: I have a solution with quite a few projects, mostly class libraries and also a web project. Everything compiles fine, but the output of all the class libraries are copied to the bin\ folder of the web project, even if they do not have a reference to them. VS.NET only copies the dll's of the projects that the web project references in the solution, not everything. When deploying this, all of these will be included as well, which is not the desired effect. -- Comment By: Gert Driesen (drieseng) Date: 2005-03-08 22:13 Message: Logged In: YES user_id=707851 What version of NAnt are you using ? If you're using NAnt 0.84, then please try using NAnt 0.85 RC2 or a recent nightly build (http://nant.sourceforge.net/nightly/latest) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] msm task property issues...
Sorry for the cross post, but I'm not sure which list Jim is monitoring :-) I've run into an issue with the MSM task and the way it is filling out the MSM summary table via properties See http://sourceforge.net/tracker/index.php?func=detailaid=1149861group_id=54 790atid=474851 for a little more detail. The end result is that the MSM modules cannot be used in 3rd party apps like wise or installshield. In order to set the msm Summary:Title and Author fields the Property ProductName and Manufacturer are used and placed in both the Summary and Property table. However if you merge that msm into an msi, the msm ProductName will overwrite the value in the MSI. If you leave the ProductName/Manufacture off, then Wise and InstallShield won't display any information on the MSM. So there should be a way to set the information in the summary table (Title, Subject, Author, Key Words, Comments, Last Saved By, and Package Code. And nothing should be required in the properties section (as it is now). Also, I've put in a few bugs with patches for some small items: http://sourceforge.net/tracker/index.php?func=detailaid=1153721group_id=54 790atid=474851 http://sourceforge.net/tracker/index.php?func=detailaid=1153718group_id=54 790atid=474851 http://sourceforge.net/tracker/index.php?func=detailaid=1149948group_id=54 790atid=474851 If someone could take a look at those I think they get a few small things. The patch for the search function fixes one thing, but doesn't make the search app work :-( I'm putting together a large MSI built from a library of NAnt built MSM files. This wouldn't even be remotely possible without Nant's MSI/MSM tasks. Thanks John Cole - This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1159348 ] Building web projects copies all project dlls
Bugs item #1159348, was opened at 2005-03-08 12:51 Message generated for change (Comment added) made by cwensley You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 Category: Tasks Group: None Status: Open Resolution: None Priority: 5 Submitted By: Curtis Wensley (cwensley) Assigned to: Nobody/Anonymous (nobody) Summary: Building web projects copies all project dlls Initial Comment: I have a solution with quite a few projects, mostly class libraries and also a web project. Everything compiles fine, but the output of all the class libraries are copied to the bin\ folder of the web project, even if they do not have a reference to them. VS.NET only copies the dll's of the projects that the web project references in the solution, not everything. When deploying this, all of these will be included as well, which is not the desired effect. -- Comment By: Curtis Wensley (cwensley) Date: 2005-03-08 19:13 Message: Logged In: YES user_id=288230 I am using nant 0.85.1869.0 (rc2) -- Comment By: Gert Driesen (drieseng) Date: 2005-03-08 13:13 Message: Logged In: YES user_id=707851 What version of NAnt are you using ? If you're using NAnt 0.84, then please try using NAnt 0.85 RC2 or a recent nightly build (http://nant.sourceforge.net/nightly/latest) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] [ nant-Bugs-1159348 ] Building web projects copies all project dlls
Bugs item #1159348, was opened at 2005-03-08 21:51 Message generated for change (Comment added) made by drieseng You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 Category: Tasks Group: None Status: Open Resolution: None Priority: 5 Submitted By: Curtis Wensley (cwensley) Assigned to: Nobody/Anonymous (nobody) Summary: Building web projects copies all project dlls Initial Comment: I have a solution with quite a few projects, mostly class libraries and also a web project. Everything compiles fine, but the output of all the class libraries are copied to the bin\ folder of the web project, even if they do not have a reference to them. VS.NET only copies the dll's of the projects that the web project references in the solution, not everything. When deploying this, all of these will be included as well, which is not the desired effect. -- Comment By: Gert Driesen (drieseng) Date: 2005-03-09 07:43 Message: Logged In: YES user_id=707851 Can you attach a small repro for this issue (including solution/project file, sources and any third party assemblies you reference) ? Thanks ! -- Comment By: Curtis Wensley (cwensley) Date: 2005-03-09 04:13 Message: Logged In: YES user_id=288230 I am using nant 0.85.1869.0 (rc2) -- Comment By: Gert Driesen (drieseng) Date: 2005-03-08 22:13 Message: Logged In: YES user_id=707851 What version of NAnt are you using ? If you're using NAnt 0.84, then please try using NAnt 0.85 RC2 or a recent nightly build (http://nant.sourceforge.net/nightly/latest) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=402868aid=1159348group_id=31650 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] debug=true/full and DEBUG
This change has now been committed to cvs. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erv WalterSent: dinsdag 8 maart 2005 22:01To: Gert Driesen; nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] debug=true/full and DEBUG That would work great! I agree that whatever is done, it should be non breaking to existing true/false settings. From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 2:45 PMTo: Erv Walter; nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] debug=true/full and DEBUG Hi, I agree that it would've been better to not implicitly set symbols, but instead leave it up to the build authors to use the define attribute for this purpose. I'm not sure whether its a good idea to introduce such a (breaking) change. We could ofcourse not define any symbols when the "debug" attribute is set to Full, PdbOnly orNone. What do you think ? Gert From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erv WalterSent: dinsdag 8 maart 2005 20:29To: Gert Driesen; nant-developers@lists.sourceforge.netSubject: [nant-dev] debug=true/full and DEBUG I am wondering about another issue that I initially thought might be helped bythe change below, but it turned out not quite. I think this has been asked before (a long time ago), but I figured I'd ask again. Currently (in cvs), the csc task sets the DEBUG symbol if debug is true, Full, or PdbOnly. That is fairly limiting in the first two cases and I think conceptually "wrong" in the last case. By setting DEBUG, many conditionally compiled functions are included in the compiled assembly. In the PdbOnly case, that is probably not what is desired. Someone using PdbOnly probably wants a "release" style build but with a pdb file. They will instead get all their DEBUG stuff included (Debug.Writeline, Debug.Assert, etc). Our situation is slightly different. We would like to turn on the debug build (to include debugging symbols), but *not* define DEBUG. In VS.NET project files, I believe it's possible to control debug symbols separately from compilation symbols such as DEBUG. We've wished for a while that this was possible in the csc task. Any thoughts on perhaps another entry in the DebugOutput enum that would allow this sort of situation? Or some other workaround? Thanks!! From: Gert Driesen [mailto:[EMAIL PROTECTED]Sent: Sat 3/5/2005 8:43 AMTo: Walker, Brian; nant-developers@lists.sourceforge.netSubject: RE: [nant-dev] Patch for 1156702 [snip] I've just added support for the different debug types to cvs. Before this change, our compiler tasks only supported either full debug output or no debug output at all. [snip]
