Deploy All Dependent Files

[Derek Hart]

I have a Visual Studio.Net solution that has several projects, one of which
is a web service project. I has a reference set to a DLL which is in the
same solution, but is a separate project. When I go to publish the web
service, there does not seem to be an option that would automatically
determine what references there are in the DLL, so dependencies for that DLL
do not publish for the web service project. Do I have to do an InstallShield
build or similar to make this happen?

Derek

[John Saunders]

Is this a Web Site project (File->New->Web Site) or a Web Application
project (File->New->Project)? If the latter, then there should be no
problem; the dependency should get copied to the bin folder and deployed
from there.

If the former, then I don't know since I never use Web Site projects. Your
issue is one of the reasons I don't.

--
John Saunders | MVP - Connected System Developer

[Derek Hart]

Actually, it is a new project (File-New-Project), and it is a new ASP.NET
Web Service Application - I understand that references in this project will
populate, but I have another project in the same solution, which is a set of
VB.Net classes (so another project, another DLL, but in the same solution).
I was hoping to figure out the best way to have the references in the VB.Net
application get published. I guess it is not enough that the web service
project is in the same solution, nor can the publishing component figure out
that the web service is dependent on the vb.net dll, and to look for
references in the vb.net project. Should I simply add all the same
references that are in the VB.Net project into the Web Service project?

Derek

"John Saunders" <[e-mail] t.comwrote in message
news:uO******** ******@TK2MSFTN GP02.phx.gbl...

Is this a Web Site project (File->New->Web Site) or a Web Application
project (File->New->Project)? If the latter, then there should be no
problem; the dependency should get copied to the bin folder and deployed
from there.

If the former, then I don't know since I never use Web Site projects. Your
issue is one of the reasons I don't.

--
John Saunders | MVP - Connected System Developer

[Derek Hart]

Actually, it is a new project (File-New-Project), and it is a new ASP.NET
Web Service Application - I understand that references in this project will
populate, but I have another project in the same solution, which is a set of
VB.Net classes (so another project, another DLL, but in the same solution).
I was hoping to figure out the best way to have the references in the VB.Net
application get published. I guess it is not enough that the web service
project is in the same solution, nor can the publishing component figure out
that the web service is dependent on the vb.net dll, and to look for
references in the vb.net project. Should I simply add all the same
references that are in the VB.Net project into the Web Service project?

Derek

"John Saunders" <[e-mail] t.comwrote in message
news:uO******** ******@TK2MSFTN GP02.phx.gbl...

Is this a Web Site project (File->New->Web Site) or a Web Application
project (File->New->Project)? If the latter, then there should be no
problem; the dependency should get copied to the bin folder and deployed
from there.

If the former, then I don't know since I never use Web Site projects. Your
issue is one of the reasons I don't.

--
John Saunders | MVP - Connected System Developer

[John Saunders]

Ok, so it sounds like your web service project _does_ reference the class
library, so you are getting the class library DLL deployed. But you are not
getting the dependencies of the class library deployed. Is that correct?

Yes, one workaround would be to duplicate the references. A simple setup
project would also work. To learn why Publish isn't getting all the
second-level references would require study of the MSBUILD output, and I
doubt I'll have enough time this week. If you want to do it yourself, I
suggest you use the Tools->Options and set the MSBUILD output level to
verbose; do the publish, then look at the output in the Output window.
You'll want to save it to a file first, it will be large.

In particular, there are places where MSBUILD will call project B from the
project A build, sort of like a subroutine. Gathering references is one
example of where this is done. Look in the output from the build of your web
service project for calls to your VB project and see if you can see a step
being skipped, or some other reason why not all of the references are
gathered or copied.

And if you find out what's wrong, please post the answer here.

--
John Saunders | MVP - Connected System Developer

"Derek Hart" <de********@yah oo.comwrote in message
news:es******** ******@TK2MSFTN GP04.phx.gbl...

Actually, it is a new project (File-New-Project), and it is a new ASP.NET
Web Service Application - I understand that references in this project
will populate, but I have another project in the same solution, which is a
set of VB.Net classes (so another project, another DLL, but in the same
solution). I was hoping to figure out the best way to have the references
in the VB.Net application get published. I guess it is not enough that the
web service project is in the same solution, nor can the publishing
component figure out that the web service is dependent on the vb.net dll,
and to look for references in the vb.net project. Should I simply add all
the same references that are in the VB.Net project into the Web Service
project?

Derek

"John Saunders" <[e-mail] t.comwrote in message
news:uO******** ******@TK2MSFTN GP02.phx.gbl...

>Is this a Web Site project (File->New->Web Site) or a Web Application
project (File->New->Project)? If the latter, then there should be no
problem; the dependency should get copied to the bin folder and deployed
from there.

If the former, then I don't know since I never use Web Site projects.
Your issue is one of the reasons I don't.

--
John Saunders | MVP - Connected System Developer