I have a solution containing many usercontrol projects.
When I wish to reference a usercontrol in another project I can select
either the project or the assembly.
Does it make a difference which one I select?
Thanks 11 1923
Just Me,
I normally reference the project, allowing VS.NET to work out compile &
setup dependencies for me.
If you reference the assembly, then you need to manually work out the
compile & setup dependencies. You can use "Project - Project Dependencies"
to set the compile dependencies, I believe you need to manually add the
respective assemblies to setup projects.
I've never had any real problems with referencing the project, however I
have seen reports on developers having problems with both methods.
Hope this helps
Jay
" Just Me" <gr****@a-znet.com> wrote in message
news:eU******** ******@TK2MSFTN GP11.phx.gbl... I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Yes it does. When you select project it is simply for debugging. When you
do a final compile you should first compile the child project and then
reference the compiled assembly in the parent project.
Dan
" Just Me" <gr****@a-znet.com> wrote in message
news:eU******** ******@TK2MSFTN GP11.phx.gbl... I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Thanks, but can you tell me why?
I mean if I select the project for the final compile, what bad thing
happens?
Thanks again
"solex" <so***@nowhere. com> wrote in message
news:Oj******** ******@TK2MSFTN GP14.phx.gbl... Yes it does. When you select project it is simply for debugging. When you do a final compile you should first compile the child project and then reference the compiled assembly in the parent project.
Dan
" Just Me" <gr****@a-znet.com> wrote in message news:eU******** ******@TK2MSFTN GP11.phx.gbl... I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
You mean, if I reference an assembly, I have to also reference all its
dependencies?
thanks
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. .. Just Me, I normally reference the project, allowing VS.NET to work out compile & setup dependencies for me.
If you reference the assembly, then you need to manually work out the compile & setup dependencies. You can use "Project - Project Dependencies" to set the compile dependencies, I believe you need to manually add the respective assemblies to setup projects.
I've never had any real problems with referencing the project, however I have seen reports on developers having problems with both methods.
Hope this helps Jay
" Just Me" <gr****@a-znet.com> wrote in message news:eU******** ******@TK2MSFTN GP11.phx.gbl...I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Dan,
I only reference projects, when I do my final compiles (release builds),
using Build Solution, the child project is compiled first then the parent
project is compiled.
Do you have a documented case where the above does not work? I would be
curious to see it.
Hope this helps
Jay
"solex" <so***@nowhere. com> wrote in message
news:Oj******** ******@TK2MSFTN GP14.phx.gbl... Yes it does. When you select project it is simply for debugging. When you do a final compile you should first compile the child project and then reference the compiled assembly in the parent project.
Dan
" Just Me" <gr****@a-znet.com> wrote in message news:eU******** ******@TK2MSFTN GP11.phx.gbl... I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Just Me, You mean, if I reference an assembly, I have to also reference all its dependencies?
No that is not what my statement is saying!
If you have 2 or more projects in your solution, an executable and one or
more class libraries. And you reference the class library assembly from your
executable. The executable may be built before the class library, causing
build errors. However ever if you use "Project - Project Dependencies" you
can indicate that the executable depends on (requires) the class library,
VS.NET will then build the class library first, then it will build the
executable.
As I stated I normally reference projects, then VS.NET takes care of every
thing (dependencies) for me. In both debug & release (final) builds.
You mean, if I reference an assembly, I have to also reference all its dependencies?
There are cases where you need to reference dependent assemblies/projects.
For example:
- Library1 has BaseClass
- Library2 has DerivedClass that inherits from BaseClass
- Executable3 references Library2 & uses DerivedClass, Exectuable3 also
needs to reference Library1 as VB.NET needs the "definition " for the
BaseClass also. Here Exectuable3 can either reference both assemblies or the
projects.
However this dependent referencing has nothing to do with build order, which
is what my initial comments about Build/Project Dependencies are referring
to.
Hope this helps
Jay
" Just Me" <gr****@a-znet.com> wrote in message
news:uG******** ******@TK2MSFTN GP14.phx.gbl... You mean, if I reference an assembly, I have to also reference all its dependencies?
thanks
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message news:%2******** ********@TK2MSF TNGP10.phx.gbl. .. Just Me, I normally reference the project, allowing VS.NET to work out compile & setup dependencies for me.
If you reference the assembly, then you need to manually work out the compile & setup dependencies. You can use "Project - Project Dependencies" to set the compile dependencies, I believe you need to manually add the respective assemblies to setup projects.
I've never had any real problems with referencing the project, however I have seen reports on developers having problems with both methods.
Hope this helps Jay
" Just Me" <gr****@a-znet.com> wrote in message news:eU******** ******@TK2MSFTN GP11.phx.gbl...I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Thanks a lot.
I've got it now.
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message
news:e%******** ********@TK2MSF TNGP14.phx.gbl. .. Just Me, You mean, if I reference an assembly, I have to also reference all its dependencies? No that is not what my statement is saying!
If you have 2 or more projects in your solution, an executable and one or more class libraries. And you reference the class library assembly from your executable. The executable may be built before the class library, causing build errors. However ever if you use "Project - Project Dependencies" you can indicate that the executable depends on (requires) the class library, VS.NET will then build the class library first, then it will build the executable.
As I stated I normally reference projects, then VS.NET takes care of every thing (dependencies) for me. In both debug & release (final) builds.
You mean, if I reference an assembly, I have to also reference all its dependencies? There are cases where you need to reference dependent assemblies/projects. For example: - Library1 has BaseClass - Library2 has DerivedClass that inherits from BaseClass - Executable3 references Library2 & uses DerivedClass, Exectuable3 also needs to reference Library1 as VB.NET needs the "definition " for the BaseClass also. Here Exectuable3 can either reference both assemblies or the projects.
However this dependent referencing has nothing to do with build order, which is what my initial comments about Build/Project Dependencies are referring to.
Hope this helps Jay
" Just Me" <gr****@a-znet.com> wrote in message news:uG******** ******@TK2MSFTN GP14.phx.gbl... You mean, if I reference an assembly, I have to also reference all its dependencies?
thanks
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message news:%2******** ********@TK2MSF TNGP10.phx.gbl. .. Just Me, I normally reference the project, allowing VS.NET to work out compile & setup dependencies for me.
If you reference the assembly, then you need to manually work out the compile & setup dependencies. You can use "Project - Project Dependencies" to set the compile dependencies, I believe you need to manually add the respective assemblies to setup projects.
I've never had any real problems with referencing the project, however I have seen reports on developers having problems with both methods.
Hope this helps Jay
" Just Me" <gr****@a-znet.com> wrote in message news:eU******** ******@TK2MSFTN GP11.phx.gbl... I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Jay,
I do not have documentation. It was my understanding that this was an
accepted method. I generally compile my components outside of the solution
and therefore need to reference the assembly. This way I do not inadverntly
recompile the component if there are no changes, which can cause problems if
there are other projects that depend on the component.
In short my posting was just my convention and apologize for any
misunderstandin g.
Regards,
Dan
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message
news:OP******** ******@TK2MSFTN GP10.phx.gbl... Dan, I only reference projects, when I do my final compiles (release builds), using Build Solution, the child project is compiled first then the parent project is compiled.
Do you have a documented case where the above does not work? I would be curious to see it.
Hope this helps Jay
"solex" <so***@nowhere. com> wrote in message news:Oj******** ******@TK2MSFTN GP14.phx.gbl... Yes it does. When you select project it is simply for debugging. When you do a final compile you should first compile the child project and then reference the compiled assembly in the parent project.
Dan
" Just Me" <gr****@a-znet.com> wrote in message news:eU******** ******@TK2MSFTN GP11.phx.gbl... I have a solution containing many usercontrol projects. When I wish to reference a usercontrol in another project I can select either the project or the assembly.
Does it make a difference which one I select? Thanks
Dan,
For projects that are shared across solutions, that may be a good
convention.
I currently do not share projects across solutions, so I have not "crossed
that bridge yet".
I can see potential problems for projects destined for the GAC where this
may be an issue, however for shared projects that are destined for side by
side deployment I don't know if I would worry about it. As I stated above, I
have not "crossed that bridge yet".
Thanks for the additional info!
Jay
"solex" <so***@nowhere. com> wrote in message
news:Oo******** ******@TK2MSFTN GP11.phx.gbl... Jay,
I do not have documentation. It was my understanding that this was an accepted method. I generally compile my components outside of the solution and therefore need to reference the assembly. This way I do not inadverntly recompile the component if there are no changes, which can cause problems if there are other projects that depend on the component.
In short my posting was just my convention and apologize for any misunderstandin g.
Regards, Dan
"Jay B. Harlow [MVP - Outlook]" <Ja************ @msn.com> wrote in message news:OP******** ******@TK2MSFTN GP10.phx.gbl... Dan, I only reference projects, when I do my final compiles (release builds), using Build Solution, the child project is compiled first then the parent project is compiled.
Do you have a documented case where the above does not work? I would be curious to see it.
Hope this helps Jay
"solex" <so***@nowhere. com> wrote in message news:Oj******** ******@TK2MSFTN GP14.phx.gbl... > Yes it does. When you select project it is simply for debugging. When > you > do a final compile you should first compile the child project and then > reference the compiled assembly in the parent project. > > Dan > > " Just Me" <gr****@a-znet.com> wrote in message > news:eU******** ******@TK2MSFTN GP11.phx.gbl... >> I have a solution containing many usercontrol projects. >> When I wish to reference a usercontrol in another project I can select >> either the project or the assembly. >> >> Does it make a difference which one I select? >> >> >> >> Thanks >> >> > >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics |
by: Petri J. Riipinen |
last post by:
Hi,
I'm writing a largish (>60 projects) solution with VS.NET 2003 using VB.NET
as my implementation language. I'm using NUnit and NUnit VS.NET-addin to
implement unit tests for my code.
Currently I have a single UnitTests-project that contains unit tests for all
other projects. This way I can embed all unit testing into a single assembly
which I can use during the development but exclude from a setup that I
create from other...
|
by: WM Chung |
last post by:
Hi all,
I meet a problem in building my .Net Solution and I would like to seek help.
After I have added a dll to reference in one of my project in my solution,
when I re-build the solution, I meet the following error :
------ Rebuild All started: Project: OIDCOMMON, Configuration: Debug .NET
------
Preparing resources...
|
by: Robert |
last post by:
I have a series of web applications (configured as separate applications) on
a server.
There is a main application at the root and then several virtual directories
that are independant applications.
I am testing an upgrade of all of the sites and have converted the main root
site...although not necessarily fixed any issues.
I move on instead and converted one of the virtual roots that is a seperate
|
by: John Lafrowda |
last post by:
Hi all,
I'm trying to handle two projects in one solution (.net 2002, both projects
are VB). The first project contains only some public constant definitions
(for the moment) and compiles into class libarary. The second one is builds
an executable which has a reference to the assembly of the first project to
retrieve global constant definitions. The whole thing works fine as long as
no definitions are changed in the library project.
...
|
by: serge calderara |
last post by:
Dear all,
I do not see the difference between Referencing an assembliy for use in my
project and Register it on a page ?
At the end if I want to use assembly functionnality , I need anyway to add a
reference no ?
| |
by: MSDNAndi |
last post by:
Hi,
I have the following problem with VS 2005 (Professional) and C# 2.0
I will use assembly and namespace synonymously here.
I have a class in namespace InheritClass inherit from a baseclass in
namespace BaseClass.
Then I have a class in namespace InheritClassUser that uses the class in
namespace InheritClass.
The references/using are from InheritClass to BaseClass and from
|
by: Richard Lewis Haggard |
last post by:
We are having a lot of trouble with problems relating to failures relating
to 'The located assembly's manifest definition with name 'xxx' does not
match the assembly reference" but none of us here really understand how this
could be an issue. The assemblies that the system is complaining about are
ones that we build here and we're not changing version numbers on anything.
The errors come and go with no apparent rhyme or reason.
We do not...
|
by: WXS |
last post by:
In a case you have Project/Assembly A references Project/Assembly B which
References Project/Assembly C.
Let's say Project A needs be and references it directly. Unknown to A, B
needs project C's assembly but it uses C's assembly dynamically (Load
Assembly).
Even with copy Local set on all references Project A when built will get
project B's output but not project C's.
This is from what I hear due to an "enhancement" in VS2005, that...
|
by: ma79ash |
last post by:
Language :: VS.NET/ C#
The type 'frm_data.frm_data' is defined in an assembly that is not
referenced. You must add a reference to assembly
I have a Frm_sol solution, which consists on 2 projects
FRM_Business and frm_Data.
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look !
Part I. Meaning of...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can effortlessly switch the default language on Windows 10 without reinstalling. I'll walk you through it.
First, let's disable language synchronization. With a Microsoft account, language settings sync across devices. To prevent any complications,...
| |
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth.
The Art of Business Website Design
Your website is...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own....
Now, this would greatly impact the work of software developers. The idea...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules.
He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms.
Adolph will...
|
by: TSSRALBI |
last post by:
Hello
I'm a network technician in training and I need your help.
I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs.
The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols.
I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
|
by: 6302768590 |
last post by:
Hai team
i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
| |
by: bsmnconsultancy |
last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating effective websites that not only look great but also perform exceptionally well. In this comprehensive...
| |