RE: [Sharpcvslib-developers] VS.NET compile problems

[Clayton H. <cla...@sp...>]

-----Original Message-----
From: Clayton Harbour=20
Sent: October 17, 2004 9:34 AM
To: Nicklas Norling
Cc: Nant-Developers (E-Mail)
Subject: [nant-dev] RE: [Sharpcvslib-developers] VS.NET compile problems


Hey Nicklas,

Thanks for forwarding that link, I have known about the issue for awhile
but had not read on possible work arounds.  Based on this information
and your suggestion I have updated the vs.net solution and projects.  I
used the console project to "copy" all dlls' to the output directory
just by setting the copy local attribute.  I am not sure if we need to
copy all of these to the bin directory.  Building with both NAnt and
vs.net might mean some confusion between the two but I don't think that
switching back and forth between the two build mechanisms is very
common...please let me know if I am wrong :-).


Also, please note that I have also added a new sub-project for the
console application.  This existed in the NAnt build but was not in the
vs.net solution (my bad, I just don't use the solution build...sorry).
The idea behind this is that the cvs.exe just provides a loading
mechanism for dependant libraries.  I have not updated the sharpdevelop
build to mirror this...Gerald if you have time can you do this?


Cheers,


Clayton



> -----Original Message-----
> From: Nicklas Norling [mailto:ex...@ex...]
> Sent: October 16, 2004 2:53 PM
> To: sha...@li...
> Subject: [Sharpcvslib-developers] VS.NET compile problems
>=20
>=20
> Hi.
>=20
> Using VS.NET 2003 to compile the solution seems to lock up the
> assemblies and give
> errors on SharpCvsLib main assembly.
> By the looks of it it appears to be the dreaded bug described in=20
> http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;313512.
>=20
> I was wondering if there is any interest in me "fixing" this by
> separating each projects
> output to a separate folder. This unfortunately means that the binary=20
> needs to be moved
> in place to the top bin folder or scripts relying on the=20
> current top bin=20
> folder needs to look
> elsewhere. The most obvious solution would be using copy as a=20
> post build=20
> event but that
> might be a platform issue as it would create a bat file with the=20
> commands entered into the
> event. Nant could also be made to copy the output after the compile=20
> (nant solution task
> supports post build events).
>=20
> What do you think?
> /Nicke
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal Use IT products in your business? Tell us=20
> what you think of them. Give us Your Opinions, Get Free=20
> ThinkGeek Gift Certificates! Click to find out more=20
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Sharpcvslib-developers mailing list=20
> Sha...@li...
> https://lists.sourceforge.net/lists/listinfo/sharpcvslib-developers
>=20


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give
us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
nant-developers mailing list
nan...@li...
https://lists.sourceforge.net/lists/listinfo/nant-developers