Quick question....

Our solution contains some dll's (usually from thrid party components like dundas etc) that live in an "external assemblies" folder within the solution folder.

Now, to make life easy - I am considering making "external assemblies" a project within my solution, that contains nothing apart from the dll's. That way, when people "get latest version" of the solution from within VS.NEt, they'll also get any new versions of the referenced dlls from sourcesafe too.... easy peasy!

I think its a good idea, but I have a niggling worry about this....

I'm afraid we do that, too. We call ours 'sharedassemblies', and it's for those little things like Excentrics World's stuff and MetaBuilders. Too many people to coordinate downloads and reinstalls, much easier to point them to a shared location and be done with it.

Somehow, I'm embarrased of it. Not sure why.

But then, I've never used the phrase, 'easy peasy', so perhaps I've nothing to be ashamed of...

swallace wrote:

Somehow, I'm embarrased of it. Not sure why.

Exactly! Why do i have a feeling this is bad? Is it just because it sounds lame - creating a project and then just adding dlls?

Hey - easy peasy is a perfectly valid phrase here in sunny england

MattWoberts wrote:

Hey - easy peasy is a perfectly valid phrase here in sunny england

Yeah, like "Sunny England" is a perfectly valid phrase among Dutch Comedians

Why do i have a feeling this is bad?

I assuage my guilt by blaming Microsoft, calling it a design flaw that didn't anticipate real-world usage.

Yeah, like "Sunny England" is a perfectly valid phrase among Dutch Comedians

Or "French Army."