Well, I figured out why slingshot and <solution> are mucking up my references. They use the HintPath which is in the *.csproj file. For some reason, mine are inconsistent. If I open the csproj files in VS.NET, all of the references are pointed correctly. But if I open it in notepad, the HintPath is incorrect (in some but not in others). Does anyone know how to fix this?
Thanks - Eric
_________________________________________________________________________
- From: Jean Rajotte
- Subject: RE: [Nant-users] Slingshot includes problems
- Date: Mon, 14 Jul 2003 09:37:53 -0700
i'm not clear on this conversation...
i've mucked in slingshot 2 months ago (or so), changing how it handled
references. btw, slingshot is deprecated in favour of the <solution>
task.
external references get copied to the build directory when they are
marked "copy local" in vss. in the .csproj file, that corresponds to
<references><reference Private="True" /></references>.
i'm not even sure i'm addressing your question. an actual set of files
( a .??proj and the matching *.build file, as well as the command line
or task to invoke it would help understand).
also, again not sure i'm helping here, there's a replacerefs
attribute/commandline param i added to slingshot.
read up on it there:
http://nant.sourceforge.net/wiki/index.php/SLiNgshoT
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Fetzer
> Sent: Monday, July 14, 2003 10:55
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [Nant-users] Slingshot includes problems
>
>
> Bernard,
>
> The external dependencies are all present. The VS.NET
> solution file that I
> am creating from slingshot is building without error based on the
> dependencies in all cases. Here's my case scenario:
>
> Local D Drive:
>
> Organizaion
> Team
> Project1
> Debug
> Subproject1
> Subproject2
> Project2
> Debug
> Subproject1
> Subproject2
> ...
>
> The project folders contain the .sln which builds without
> error for both
> subprojects in VS.NET. The Debug folder will get executables
> including any
> external dependencies (i.e. the .sln file in Project1 may map
> external
> dependencies to the Debug folder in Project2 - in which case
> Project2 was
> built first...). The Subproject folders contain source and
> any internal
> dependencies. Once I've built the .sln file in the case scenario for
> Project1, I use slingshot to create the build file based on
> that solution
> file. I delete the contents of the Debug folder to use my
> .build file
> instead with NAnt. In order to get the .build file to work I
> have to change
> the following lines:
>
> <includes
> name="D:\Organization\Team\Project1\Library\bin\externalDepend
> s.dll" />
> to
> <includes
> name="D:\Organization\Team\Project1\Debug\externalDepends.dll" />
>
> and in some cases
>
> <includes
> name="D:\Organization\Project1\Library\bin\externalDepends2.dll"
> />
> to
> <includes
> name="D:\Organization\Team\Project1\Debug\externalDepends2.dll" />
>
>
> This makes no sense to me because I have the .sln file saved
> down to the D
> drive; and if I open the solution file up in the
> D:\Organization\Team\Project1 folder, the references are
> still correct. It
> will build again without errors. Where exactly does slingshot get
> information on where these external dependencies can be
> found? The reason
> I'm blaming VSS is because in the second change noted, the
> folder structure
> in VSS for the external dependency was different (i.e. the
> subprojects are
> split up between two databases and one of those does not
> contain the Team
> folder).
>
> Thanks,
> Eric
>
>
> >From: "Bernard Vander Beken" To: "Eric Fetzer" , Subject: RE:
> >[Nant-users]
> >Slingshot includes problems Date: Sat, 12 Jul 2003 14:58:05 +0200
> >
> >Hello Eric,
> >
> >You should not have to tweak the project properties in VS.NET.
> >
> >However, it may be needed to manually copy external
> dependencies to the
> >build directory before calling the slingshot-generated build file.
> >
> >Best regards,
> >
> >Bernard
> >
> >
> >-----Original Message----- From: Eric Fetzer
> >[mailto:[EMAIL PROTECTED]
> >Sent: Fri 7/11/2003 23:38 To:
> [EMAIL PROTECTED] Cc: Subject:
> >[Nant-users] Slingshot includes problems I've run into some
> problems with
> >slingshot building my includes with the incorrect path. I'm
> guessing that I
> >must be missing something in the Visual Studio .NET as I am
> extremely new
> >to it. In order to have the paths match between VS and NAnt,
> I have been
> >going into the Properties of each project (subproject of a
> solution) and
> >setting the build configuration to Debug\ for Debug and Release\ for
> >Release. I confirm that the build works in VS, save down the
> .sln file, and
> >then build my .build file based on the .sln file. When I
> have slingshot
> >create the build file, he is completely getting the
> reference includes
> >paths wrong so that I have to go in manually and fix them.
> Note that it is
> >very consistent from project to project what he's confusing.
> The only thing
> >I can figure is that he is getting confused by the
> SourceSafe bindings
> >because our projects aren't organiz(s)ed the same way in VSS as our
> >development environment. Can anyone help out here? Thanks - Eric
> >
>
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Nant-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/n> ant-users
>
i've mucked in slingshot 2 months ago (or so), changing how it handled
references. btw, slingshot is deprecated in favour of the <solution>
task.
external references get copied to the build directory when they are
marked "copy local" in vss. in the .csproj file, that corresponds to
<references><reference Private="True" /></references>.
i'm not even sure i'm addressing your question. an actual set of files
( a .??proj and the matching *.build file, as well as the command line
or task to invoke it would help understand).
also, again not sure i'm helping here, there's a replacerefs
attribute/commandline param i added to slingshot.
read up on it there:
http://nant.sourceforge.net/wiki/index.php/SLiNgshoT
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Fetzer
> Sent: Monday, July 14, 2003 10:55
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [Nant-users] Slingshot includes problems
>
>
> Bernard,
>
> The external dependencies are all present. The VS.NET
> solution file that I
> am creating from slingshot is building without error based on the
> dependencies in all cases. Here's my case scenario:
>
> Local D Drive:
>
> Organizaion
> Team
> Project1
> Debug
> Subproject1
> Subproject2
> Project2
> Debug
> Subproject1
> Subproject2
> ...
>
> The project folders contain the .sln which builds without
> error for both
> subprojects in VS.NET. The Debug folder will get executables
> including any
> external dependencies (i.e. the .sln file in Project1 may map
> external
> dependencies to the Debug folder in Project2 - in which case
> Project2 was
> built first...). The Subproject folders contain source and
> any internal
> dependencies. Once I've built the .sln file in the case scenario for
> Project1, I use slingshot to create the build file based on
> that solution
> file. I delete the contents of the Debug folder to use my
> .build file
> instead with NAnt. In order to get the .build file to work I
> have to change
> the following lines:
>
> <includes
> name="D:\Organization\Team\Project1\Library\bin\externalDepend
> s.dll" />
> to
> <includes
> name="D:\Organization\Team\Project1\Debug\externalDepends.dll" />
>
> and in some cases
>
> <includes
> name="D:\Organization\Project1\Library\bin\externalDepends2.dll"
> />
> to
> <includes
> name="D:\Organization\Team\Project1\Debug\externalDepends2.dll" />
>
>
> This makes no sense to me because I have the .sln file saved
> down to the D
> drive; and if I open the solution file up in the
> D:\Organization\Team\Project1 folder, the references are
> still correct. It
> will build again without errors. Where exactly does slingshot get
> information on where these external dependencies can be
> found? The reason
> I'm blaming VSS is because in the second change noted, the
> folder structure
> in VSS for the external dependency was different (i.e. the
> subprojects are
> split up between two databases and one of those does not
> contain the Team
> folder).
>
> Thanks,
> Eric
>
>
> >From: "Bernard Vander Beken" To: "Eric Fetzer" , Subject: RE:
> >[Nant-users]
> >Slingshot includes problems Date: Sat, 12 Jul 2003 14:58:05 +0200
> >
> >Hello Eric,
> >
> >You should not have to tweak the project properties in VS.NET.
> >
> >However, it may be needed to manually copy external
> dependencies to the
> >build directory before calling the slingshot-generated build file.
> >
> >Best regards,
> >
> >Bernard
> >
> >
> >-----Original Message----- From: Eric Fetzer
> >[mailto:[EMAIL PROTECTED]
> >Sent: Fri 7/11/2003 23:38 To:
> [EMAIL PROTECTED] Cc: Subject:
> >[Nant-users] Slingshot includes problems I've run into some
> problems with
> >slingshot building my includes with the incorrect path. I'm
> guessing that I
> >must be missing something in the Visual Studio .NET as I am
> extremely new
> >to it. In order to have the paths match between VS and NAnt,
> I have been
> >going into the Properties of each project (subproject of a
> solution) and
> >setting the build configuration to Debug\ for Debug and Release\ for
> >Release. I confirm that the build works in VS, save down the
> .sln file, and
> >then build my .build file based on the .sln file. When I
> have slingshot
> >create the build file, he is completely getting the
> reference includes
> >paths wrong so that I have to go in manually and fix them.
> Note that it is
> >very consistent from project to project what he's confusing.
> The only thing
> >I can figure is that he is getting confused by the
> SourceSafe bindings
> >because our projects aren't organiz(s)ed the same way in VSS as our
> >development environment. Can anyone help out here? Thanks - Eric
> >
>
> _________________________________________________________________
> The new MSN 8: smart spam protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> Nant-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/n> ant-users
>
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
