Prev: DataObject & DataObjectField Attributes?
Next: How do I reuse a BackgroundWorker object?
From: not_a_commie on 16 Apr 2010 11:43
When I use the "Publish Web Site" command for my .Net 2.0 Webservices,
all the referenced assemblies are automatically copied to the
destination folder. However, any native DLLs that I manually placed in
the Bin folder are not copied. Any ideas how to change this? Is there
some always-copy-this-file-on-publish element that I can put in the
web.config file? Thanks for your time.
From: Mr. Arnold on 16 Apr 2010 15:23
not_a_commie wrote:
> When I use the "Publish Web Site" command for my .Net 2.0 Webservices,
> all the referenced assemblies are automatically copied to the
> destination folder. However, any native DLLs that I manually placed in
> the Bin folder are not copied.

What native DLLs are you talking about?

> Any ideas how to change this? Is there
> some always-copy-this-file-on-publish element that I can put in the
> web.config file? Thanks for your time.

There is nothing that I know about that can be placed in a Web.config to
accomplish this.
From: Family Tree Mike on 16 Apr 2010 16:57
On 4/16/2010 11:43 AM, not_a_commie wrote:
> When I use the "Publish Web Site" command for my .Net 2.0 Webservices,
> all the referenced assemblies are automatically copied to the
> destination folder. However, any native DLLs that I manually placed in
> the Bin folder are not copied. Any ideas how to change this? Is there
> some always-copy-this-file-on-publish element that I can put in the
> web.config file? Thanks for your time.

Why are they there if you don't reference them?

One possible solution is to add the dlls to your project as a file. It
should then be copied to the publish folder.

--
Mike
From: Mr. Arnold on 16 Apr 2010 17:11
Family Tree Mike wrote:
> On 4/16/2010 11:43 AM, not_a_commie wrote:
>> When I use the "Publish Web Site" command for my .Net 2.0 Webservices,
>> all the referenced assemblies are automatically copied to the
>> destination folder. However, any native DLLs that I manually placed in
>> the Bin folder are not copied. Any ideas how to change this? Is there
>> some always-copy-this-file-on-publish element that I can put in the
>> web.config file? Thanks for your time.
>
> Why are they there if you don't reference them?

DLL(s) may reference other DLL(s) with no reference made in the project
to them, but they are required.

You ever try to add a control, a DLL, to the Toolbox and that DLL has
references to other DLL(s) and those DLL(s) must be moved to the
location of the ToolBox DLL that is being added to the ToolBox?


From: Family Tree Mike on 16 Apr 2010 18:44
On 4/16/2010 5:11 PM, Mr. Arnold wrote:
> Family Tree Mike wrote:
>> On 4/16/2010 11:43 AM, not_a_commie wrote:
>>> When I use the "Publish Web Site" command for my .Net 2.0 Webservices,
>>> all the referenced assemblies are automatically copied to the
>>> destination folder. However, any native DLLs that I manually placed in
>>> the Bin folder are not copied. Any ideas how to change this? Is there
>>> some always-copy-this-file-on-publish element that I can put in the
>>> web.config file? Thanks for your time.
>>
>> Why are they there if you don't reference them?
>
> DLL(s) may reference other DLL(s) with no reference made in the project
> to them, but they are required.
>
> You ever try to add a control, a DLL, to the Toolbox and that DLL has
> references to other DLL(s) and those DLL(s) must be moved to the
> location of the ToolBox DLL that is being added to the ToolBox?
>
>

No, I've never added a control of my own with dependencies to the
toolbox. Nor have I experienced secondary dll dependencies being an
issue in a web application. If a secondary dependency has been missing,
it has been flagged on build.

--
Mike
 |  Next  |  Last
Pages: 1 2
Prev: DataObject & DataObjectField Attributes?
Next: How do I reuse a BackgroundWorker object?