Chris,
We have had to recently solve this problem ourselves, and found two
solutions:
1) Each web project has it's own copy of the generic framework (which I know
you want to avoid)
2) Use the GAC
We opted for #1 for a couple of reasons. First, we found that it is a good
thing to avoid the GAC. Debugging is one issue, registering files and
getting them to show up in Visual Studio is another.
Second, you may find that you will end up with multiple copies of your
generic framework anyway. In our case, we need the ability to upgrade or fix
the framework for one product without impacting others, which means we have
multiple versions of the same framework. So if product A references version
1.0 of the framework, and product B references version 1.1, then we have
multiple copies of the framework anyway. One big benefit for us is we can do
xcopy deployment.
Hope that helps a little!
Bob L.
"Chris Stewart" <Ch**********@discussions.microsoft.com> wrote in message
news:C8**********************************@microsof t.com...
I have a solution I've been working on, which contains a dll project and
web services project. This solution is a generic framework that should be
used with many different projects we do, each of which would have their own web
application project. How can I set this up in VS.NET, so it works well
with source safe 6.0 and we can "import" those generic projects into whichever
client web application we're working on? I really don't want multiple
copies of the generic projects.
