Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Namespace Question 1
- Thread starter BiancaJ
- Start date
-
1
- #2
Possibly, but not necessarily. Keep in mind too that any dll's that are referenced by a project are copied locally to the project's bin folder, so you can also find it there.
If you want to actually see some source code taht wrox has given though, I'm guessing the easiest would be to do a search on your machine for the assembly name. Or, better yet, look in your solution file. It should have a listing of the path it used to copy the assembly from.
D'Arcy
If you want to actually see some source code taht wrox has given though, I'm guessing the easiest would be to do a search on your machine for the assembly name. Or, better yet, look in your solution file. It should have a listing of the path it used to copy the assembly from.
D'Arcy
- Thread starter
- #3
Thank you for your reply 
Another question - lets say I declare "Using Modules.AdsManager.File" in my code.
Does it mean that I should have "bin/Modules/AdsManager/File" available at the same directory as I build my code?
Or will it be "Modules/AdsManager/File" available at the same directory as I build the code?
Thanks very much.
Bianca
Another question - lets say I declare "Using Modules.AdsManager.File" in my code.
Does it mean that I should have "bin/Modules/AdsManager/File" available at the same directory as I build my code?
Or will it be "Modules/AdsManager/File" available at the same directory as I build the code?
Thanks very much.
Bianca
Sorry Bianca, not quite clear on what your question is.
If you add a reference to your project, you have to tell it where the dll is. Once you do that, it copies a local copy to your project (this isn't the case with the GAC, but thats a whole other topic).
Now, if you did use the namespace that you mentioned, as long as you have a reference to the assembly in your project, you don't have to worry at all about moving the assembly yourself; vs.net should do that for you.
I *think* your asking if you need to put the files you want in the same directory as your project, and the answer is no: it'll get copied over.
hth
D
If you add a reference to your project, you have to tell it where the dll is. Once you do that, it copies a local copy to your project (this isn't the case with the GAC, but thats a whole other topic).
Now, if you did use the namespace that you mentioned, as long as you have a reference to the assembly in your project, you don't have to worry at all about moving the assembly yourself; vs.net should do that for you.
I *think* your asking if you need to put the files you want in the same directory as your project, and the answer is no: it'll get copied over.
hth
D
- Status