Bugs item #931819, was opened at 2004-04-08 17:44
Message generated for change (Comment added) made by drieseng
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=931819&group_id=31650
Category: Tasks
Group: 0.85
Status: Open
Resolution: None
Priority: 5
Submitted By: Jos Clijmans (clijmans)
Assigned to: Gert Driesen (drieseng)
Summary: Issues with Solution task
Initial Comment:
We have some serious issues with the nightly build from
05/04/2004
Error in license task : NAnt.VSNet.Tasks.SolutionTask is
not serializable
solved by putting the Serializable attribute on the
task
AssemblyKey file cannot be found
The solution task changes the working directory to obj
VS.Net keeps the current directory when double-click on
a .sln file.
Our AssemblyInfo.vb file specifies the assemblykeyfile
without directory info (..). So VS.Net finds it in the
projectdir. NAnt looks into the obj dir and doesn't find
the snk file.
VS.Net copies the app.config file to "outputfile".config
as part of the build, NAnt doesn't.
----------------------------------------------------------------------
>Comment By: Gert Driesen (drieseng)
Date: 2004-04-08 20:52
Message:
Logged In: YES
user_id=707851
Items 2 and 3 are fixed in cvs now.
Can you give me more information on the license task issue ?
Thanks !
----------------------------------------------------------------------
Comment By: Gert Driesen (drieseng)
Date: 2004-04-08 19:56
Message:
Logged In: YES
user_id=707851
- <license> : in what circumstances did you get this
serialization exception ?
- assemblykeyfile : I'm fixing this right now, but I was really
surprise to learn how VB.NET actually deal with this. If you
just open VS.NET from the Start menu, you would actually be
forced to place your key file in the VS.NET directory or
specify a full path in order to compile a assembly with a
strong name. This is really very bad behaviour, if you ask
me. I'll fix this by using the directory in which the solution file
(or the project file, depending on whether you specified a
solution file for the <solution> task or a list of projects) is
located as working directory. I still don't like this solution,
but I don't think there's much more we can do. I'll commit this
fix to cvs later today.
- this is a known issue, I'll try to look into this ASAP.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=402868&aid=931819&group_id=31650
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
