I figured out how to do this awesome thing. It's really awesome. I already gave numerous reasons why it would save time and be advantageous.

The PM however is asking one thing and says my idea doesn't possibly solve one thing and I need to think on that.

I think he's absolutely insane (if I understand his problem statement) and that to do so would be utterly to much of a PITA.

So coders... riddle me this... you have a source tree. How do you keep track of released Assemblies in the wild? Be it releases or 1-off?

The PM is saying I need to keep track of any and every released version every let into the wild. Including (god help me) if we release...

...1 dll for 1 client which is having an issue. A single machine/client fix.

So how do you keep track of that. I know source trees can do a bit. But how do you keep things consistent amongst multiple simultaneous..

...versions? Like how can I prevent one machine with the special fix dll not get the auto-update the rest of the client base gets?

I suppose I could do some freakish policy settings or crazy internal logic but it just makes it... it's really a buzzkill.

Thoughts anyone??