Installer problem with VB projects and C# projects

[Brian Henry]

This has worked perfectly for the past year now all the sudden it will not
compile the installer project correctly. All our source code is in a Source
Safe database so every system we do this on should be identicle. On one
system the installer project will compile correctly, but on two others it
will fail with this error.

------ Rebuild All started: Project: Installer, Configuration: Debug ------
Building file 'T:\Current Builds Installers\Benefits
System\Installer.msi'...
ERROR: Could not find file
'C:\reschinidev\benefits\Reporting\obj\Release\Reporting.dll' 'The system
cannot find the path specified.'

if i remove that project from the installer then it says another one with
the same error (there are about 20 project outputs in the installer) every
thing in the installer is added as a primary output from [project]
(release.net)... as for the projects they have custom build locations for
when they are built. not into the standard project\bin\release folder...
what could be going on? what should i look at? ive tried about everything
including creating a new installer from scratch and still got the same
errors.

 

[Dan Bass]

It looks like the reporting.dll file was referenced directly by the
installer rather than the project output (which could be .exe / .dll etc).
Hence the reason "C:\reschinidev\" is mentioned in the error.

When adding files that are the result of a compilation by your application,
do not "Add Files...", but rather "Add Project Output...". You'll find this
will then reference the DLL in question regardless of the folders in which
you try to build the solution.

The reason it has always worked it seems, is that the project used to exist
on the C:\, but now you've a partition T:\ I presume, on which your projects
are compiled.

Hope that makes sense.
Good luck.

 

[Brian Henry]

that is how they are added to the installer through Add Project Output... i
actually made a new installer to figure out what was going on with the same
add project output and still get the same error on two systems but no
another one (3 systems total)...

It looks like the reporting.dll file was referenced directly by the
installer rather than the project output (which could be .exe / .dll etc).
Hence the reason "C:\reschinidev\" is mentioned in the error.

When adding files that are the result of a compilation by your
application, do not "Add Files...", but rather "Add Project Output...".
You'll find this will then reference the DLL in question regardless of the
folders in which you try to build the solution.

The reason it has always worked it seems, is that the project used to
exist on the C:\, but now you've a partition T:\ I presume, on which your
projects are compiled.

Hope that makes sense.
Good luck.

This has worked perfectly for the past year now all the sudden it will
not compile the installer project correctly. All our source code is in a
Source Safe database so every system we do this on should be identicle.
On one system the installer project will compile correctly, but on two
others it will fail with this error.

------ Rebuild All started: Project: Installer, Configuration:
Debug ------
Building file 'T:\Current Builds Installers\Benefits
System\Installer.msi'...
ERROR: Could not find file
'C:\reschinidev\benefits\Reporting\obj\Release\Reporting.dll' 'The system
cannot find the path specified.'

if i remove that project from the installer then it says another one with
the same error (there are about 20 project outputs in the installer)
every thing in the installer is added as a primary output from [project]
(release.net)... as for the projects they have custom build locations for
when they are built. not into the standard project\bin\release folder...
what could be going on? what should i look at? ive tried about everything
including creating a new installer from scratch and still got the same
errors.

 

[Dan Bass]

If you shut down VS.Net and perform a search on all the solution and
projects file for "C:\reschinidev", what files come up? There should be no
references to anything absolute, but only relative from the solution (.sln)
file.

that is how they are added to the installer through Add Project Output...
i actually made a new installer to figure out what was going on with the
same add project output and still get the same error on two systems but no
another one (3 systems total)...

It looks like the reporting.dll file was referenced directly by the
installer rather than the project output (which could be .exe / .dll
etc).
Hence the reason "C:\reschinidev\" is mentioned in the error.

When adding files that are the result of a compilation by your
application, do not "Add Files...", but rather "Add Project Output...".
You'll find this will then reference the DLL in question regardless of
the folders in which you try to build the solution.

The reason it has always worked it seems, is that the project used to
exist on the C:\, but now you've a partition T:\ I presume, on which your
projects are compiled.

Hope that makes sense.
Good luck.

This has worked perfectly for the past year now all the sudden it will
not compile the installer project correctly. All our source code is in a
Source Safe database so every system we do this on should be identicle.
On one system the installer project will compile correctly, but on two
others it will fail with this error.

------ Rebuild All started: Project: Installer, Configuration:
Debug ------
Building file 'T:\Current Builds Installers\Benefits
System\Installer.msi'...
ERROR: Could not find file
'C:\reschinidev\benefits\Reporting\obj\Release\Reporting.dll' 'The
system cannot find the path specified.'

if i remove that project from the installer then it says another one
with the same error (there are about 20 project outputs in the
installer) every thing in the installer is added as a primary output
from [project] (release.net)... as for the projects they have custom
build locations for when they are built. not into the standard
project\bin\release folder... what could be going on? what should i look
at? ive tried about everything including creating a new installer from
scratch and still got the same errors.