J
Jupiter49
Hi, I'm testing some ASP products and finding that I am forced to copy
identically populated /bin folders to remote, where I don't have to
locally. This seems wasteful. I set up my local projects/folders
structure to eliminate this but so far I can't find a way to do it on
remote.
I like having a RootProject with folders under it where I keep various
pages that all rely on the same assemblies in the /bin folder at the
RootProject level. When I get new assemblies I just copy them once
and all my pages can use them.
Great, but when I deploy this structure to remote I am forced to have
a /bin folder in the level BELOW RootProject, which means that for
every folder I have under RootProject I have to have a separate /bin
with redundant copies of the same assemblies. Is there a work-around
to this?
identically populated /bin folders to remote, where I don't have to
locally. This seems wasteful. I set up my local projects/folders
structure to eliminate this but so far I can't find a way to do it on
remote.
I like having a RootProject with folders under it where I keep various
pages that all rely on the same assemblies in the /bin folder at the
RootProject level. When I get new assemblies I just copy them once
and all my pages can use them.
Great, but when I deploy this structure to remote I am forced to have
a /bin folder in the level BELOW RootProject, which means that for
every folder I have under RootProject I have to have a separate /bin
with redundant copies of the same assemblies. Is there a work-around
to this?