Project Design Poll
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Usually I reference the project so I can debug into it. Once you've made a release build and deployed it it doesn't matter how you set it up in the VS. What I have run into (many times) is accidently referencing a DLL that's installed in the GAC and then wondering why my changes aren't taking effect. :sigh:
-
If they are all in the same solution then I reference the assembly(DLL) as that is what is suggested in VS2015.
- I would love to change the world, but they won’t give me the source code.
Not sure I agree, but maybe I don't understand what you mean.
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I'm with PIEBALD on this one, reference the project so you can debug into it.
Never underestimate the power of human stupidity RAH
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Why would I want to reference just the dll if I have access to the project? I'm only seeing limitations.
Wrong is evil and must be defeated. - Jeff Ello
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
suggest it for future polls? Poll Suggestion Page[^] You will probably get more people answering than posting here
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
suggest it for future polls? Poll Suggestion Page[^] You will probably get more people answering than posting here
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
I thought you could just create a poll. I'm sure I did, once.
I wanna be a eunuchs developer! Pass me a bread knife!
-
I thought you could just create a poll. I'm sure I did, once.
I wanna be a eunuchs developer! Pass me a bread knife!
Maybe it was like that... then
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Maybe it was like that... then
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
"There were eight-teen of us livin' in that septic tank!"
I wanna be a eunuchs developer! Pass me a bread knife!
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Reference other projects because the referenced dll will reflect the changes made from other projects automatically when rebuilding the solution. Unless if you want other developers not to edit the code directly from other projects(core project or business logic) referencing the assembly is the way to go. :-)
-
Do you reference other projects or do you reference the assemblies from other projects? I've been on a lot of teams and I've seen it done both ways? What's your take on the right way to reference other code?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
It depends. If the "other project" is a utility set that is shared by other solutions, then generally I would reference the assembly. If it's going to be changed as the current solution evolves, then I reference the project so I can debug through. My general rule is simple: if it's external to the solution then I reference the assembly - and "upgrade" to referencing the project if it becomes necessary. That way, my changes are not risking other solutions which may depend on something working the way it does now.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
