Anyone know how to breakdown every modules into different assemblies
and refernces. Hence, to repair problematic module, only that
particular module needed to be recompiled.
or any place can get more information about assemblies & references
12  1094 
just code it that way?! im kinda missing what you're not getting.. just code
all the modules as seperate projects and refrence them all together... it's
not that hard
" A-PK" <pi********@hotmail.com> wrote in message
news:uQ***************@tk2msftngp13.phx.gbl... Anyone know how to breakdown every modules into different assemblies
and refernces. Hence, to repair problematic module, only that
particular module needed to be recompiled.
or any place can get more information about assemblies & references
If you want to take this approach, you'll need to create each module in its
own solution, which will compile it to its own assembly. For example, one
solution could be the module that describes data classes and another could
describe business classes.
Search MSDN.Microsoft.com, keyword "assemblies" for more.
" A-PK" <pi********@hotmail.com> wrote in message
news:uQ***************@tk2msftngp13.phx.gbl... Anyone know how to breakdown every modules into different assemblies
and refernces. Hence, to repair problematic module, only that
particular module needed to be recompiled.
or any place can get more information about assemblies & references
how to compile them and make those project readable and can reference them ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:OY**************@tk2msftngp13.phx.gbl... If you want to take this approach, you'll need to create each module in
its own solution, which will compile it to its own assembly. For example, one
solution could be the module that describes data classes and another could
describe business classes.
Search MSDN.Microsoft.com, keyword "assemblies" for more.
" A-PK" <pi********@hotmail.com> wrote in message
news:uQ***************@tk2msftngp13.phx.gbl... Anyone know how to breakdown every modules into different assemblies
and refernces. Hence, to repair problematic module, only that
particular module needed to be recompiled.
or any place can get more information about assemblies & references
Compile them just as you would any assembly. Reference them as you would
any assembly. Once they are referenced, you can instantiate the classes in
the modules.
Are you saying you don't know how to compile and make references? If so,
that is a completely different issue. If you are using VS.NET, "build" your
assembly (compile) from the Build menu. If not using VS.NET, use the
command line compilers.
" A-PK" <pi********@hotmail.com> wrote in message
news:Oc**************@tk2msftngp13.phx.gbl... how to compile them and make those project readable and can reference them
?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:OY**************@tk2msftngp13.phx.gbl... If you want to take this approach, you'll need to create each module in
its own solution, which will compile it to its own assembly. For example,
one solution could be the module that describes data classes and another
could describe business classes.
Search MSDN.Microsoft.com, keyword "assemblies" for more.
" A-PK" <pi********@hotmail.com> wrote in message
news:uQ***************@tk2msftngp13.phx.gbl... Anyone know how to breakdown every modules into different assemblies
and refernces. Hence, to repair problematic module, only that
particular module needed to be recompiled.
or any place can get more information about assemblies & references
so sorry.....
I right click the "references" under the solution explorer and choose Add
References.
then pop up one screen with Three Tab there
..NET \ COM \ Projects
i wonder which to choose ? I choose Project then anotehr screen poping up
i browse to the destination path and choose xxx.exe but can not add the
references.
this is where I stuck.
1- i dun know if my file compile correctly - acoording to scott, i did
compile them correcntly.
2- i dun know if my destination path is correct, but i have try every files
on that folder, but all can not
Is it only DLL or COM file can be references ?
I create a new project and try to compile and make it a reference ...can or
can not ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:#3**************@TK2MSFTNGP10.phx.gbl... Compile them just as you would any assembly. Reference them as you would
any assembly. Once they are referenced, you can instantiate the classes
in the modules.
Are you saying you don't know how to compile and make references? If so,
that is a completely different issue. If you are using VS.NET, "build"
your assembly (compile) from the Build menu. If not using VS.NET, use the
command line compilers.
" A-PK" <pi********@hotmail.com> wrote in message
news:Oc**************@tk2msftngp13.phx.gbl... how to compile them and make those project readable and can reference
them ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:OY**************@tk2msftngp13.phx.gbl... If you want to take this approach, you'll need to create each module
in its own solution, which will compile it to its own assembly. For example,
one solution could be the module that describes data classes and another could describe business classes.
Search MSDN.Microsoft.com, keyword "assemblies" for more.
" A-PK" <pi********@hotmail.com> wrote in message
news:uQ***************@tk2msftngp13.phx.gbl...
> Anyone know how to breakdown every modules into different assemblies
>
> and refernces. Hence, to repair problematic module, only that
>
> particular module needed to be recompiled.
>
>
> or any place can get more information about assemblies & references
>
>
" A-PK" <pi********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... so sorry.....
I right click the "references" under the solution explorer and choose Add
References.
then pop up one screen with Three Tab there
.NET \ COM \ Projects
i wonder which to choose ? I choose Project then anotehr screen poping up
i browse to the destination path and choose xxx.exe but can not add the
references.
You want to make a reference to a .NET Assembly, right? Then choose .NET
and hit browse. Browse to the .NET assembly in question and hit select.
Then click OK. It's really very simple.
this is where I stuck.
1- i dun know if my file compile correctly - acoording to scott, i did
compile them correcntly.
2- i dun know if my destination path is correct, but i have try every
files on that folder, but all can not
Is it only DLL or COM file can be references ?
I create a new project and try to compile and make it a reference ...can
or can not ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:#3**************@TK2MSFTNGP10.phx.gbl... Compile them just as you would any assembly. Reference them as you
would any assembly. Once they are referenced, you can instantiate the classes
in the modules.
Are you saying you don't know how to compile and make references? If
so, that is a completely different issue. If you are using VS.NET, "build"
your assembly (compile) from the Build menu. If not using VS.NET, use the
command line compilers.
" A-PK" <pi********@hotmail.com> wrote in message
news:Oc**************@tk2msftngp13.phx.gbl... how to compile them and make those project readable and can reference them ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:OY**************@tk2msftngp13.phx.gbl...
> If you want to take this approach, you'll need to create each module
in its
> own solution, which will compile it to its own assembly. For
example, one > solution could be the module that describes data classes and another
could > describe business classes.
>
> Search MSDN.Microsoft.com, keyword "assemblies" for more.
>
>
> " A-PK" <pi********@hotmail.com> wrote in message
> news:uQ***************@tk2msftngp13.phx.gbl...
> > Anyone know how to breakdown every modules into different
assemblies > >
> > and refernces. Hence, to repair problematic module, only that
> >
> > particular module needed to be recompiled.
> >
> >
> > or any place can get more information about assemblies &
references > >
> >
>
>
ok..should i compile my project to .dll file then make references to my
project ?
i have compile my file to dll, and able to make references, i wonder if i
dun compile to dll (class), could I still make reference to my project ?
i am confused about dll now...i though dot net already face off dll.....but
how come i still need to compile dll in order to make references ?...pls
guide me....i am not clear in this issue
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eL**************@TK2MSFTNGP10.phx.gbl...
" A-PK" <pi********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... so sorry.....
I right click the "references" under the solution explorer and choose
Add References.
then pop up one screen with Three Tab there
.NET \ COM \ Projects
i wonder which to choose ? I choose Project then anotehr screen poping
up i browse to the destination path and choose xxx.exe but can not add the
references.
You want to make a reference to a .NET Assembly, right? Then choose .NET
and hit browse. Browse to the .NET assembly in question and hit select.
Then click OK. It's really very simple.
this is where I stuck.
1- i dun know if my file compile correctly - acoording to scott, i did
compile them correcntly.
2- i dun know if my destination path is correct, but i have try every
files on that folder, but all can not
Is it only DLL or COM file can be references ?
I create a new project and try to compile and make it a reference ...can
or can not ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:#3**************@TK2MSFTNGP10.phx.gbl... Compile them just as you would any assembly. Reference them as you would any assembly. Once they are referenced, you can instantiate the
classes in the modules.
Are you saying you don't know how to compile and make references? If so, that is a completely different issue. If you are using VS.NET,
"build" your assembly (compile) from the Build menu. If not using VS.NET, use the
command line compilers.
" A-PK" <pi********@hotmail.com> wrote in message
news:Oc**************@tk2msftngp13.phx.gbl...
> how to compile them and make those project readable and can
reference them ?
>
> "Scott M." <s-***@BADSPAMsnet.net> wrote in message
> news:OY**************@tk2msftngp13.phx.gbl...
> > If you want to take this approach, you'll need to create each
module in > its
> > own solution, which will compile it to its own assembly. For
example, one
> > solution could be the module that describes data classes and
another could
> > describe business classes.
> >
> > Search MSDN.Microsoft.com, keyword "assemblies" for more.
> >
> >
> > " A-PK" <pi********@hotmail.com> wrote in message
> > news:uQ***************@tk2msftngp13.phx.gbl...
> > > Anyone know how to breakdown every modules into different
assemblies > > >
> > > and refernces. Hence, to repair problematic module, only that
> > >
> > > particular module needed to be recompiled.
> > >
> > >
> > > or any place can get more information about assemblies & references > > >
> > >
> >
> >
>
>
" A-PK" <pi********@hotmail.com> wrote in message
news:ed****************@TK2MSFTNGP11.phx.gbl... ok..should i compile my project to .dll file then make references to my
project ?
Whatever .dll you want to reference should already be compiled into its
final form (.dll or .exe) before you reference it. The project that needs
to use the referenced .dll need not be compiled to make the reference, but
certainly needs to be compiled in order for its code to run (and therefore
use the referenced assembly).
i have compile my file to dll, and able to make references, i wonder if i
dun compile to dll (class), could I still make reference to my project ?
See above.
i am confused about dll now...i though dot net already face off
dll.....but how come i still need to compile dll in order to make references ?...pls
guide me....i am not clear in this issue
As I stated, you need to have whatever you want to reference already
compiled, because the compiled assembly is what you make a reference to.
The project that is making the reference needs to be compiled to run, but
not to make a reference. An example of this is that a brand new project in
VS.NET will already have references to commonly used .NET assemblies
(system.dll, mscoree.dll, etc.) before you even begin.
I really would suggest an msdn.microsoft.com search on "Assemblies",
"Namespaces" and "references" as these are all basic tenants of .NET
programming.
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:eL**************@TK2MSFTNGP10.phx.gbl...
" A-PK" <pi********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... so sorry.....
I right click the "references" under the solution explorer and choose Add References.
then pop up one screen with Three Tab there
.NET \ COM \ Projects
i wonder which to choose ? I choose Project then anotehr screen poping up i browse to the destination path and choose xxx.exe but can not add
the references.
You want to make a reference to a .NET Assembly, right? Then choose
..NET and hit browse. Browse to the .NET assembly in question and hit select.
Then click OK. It's really very simple.
this is where I stuck.
1- i dun know if my file compile correctly - acoording to scott, i did
compile them correcntly.
2- i dun know if my destination path is correct, but i have try every
files on that folder, but all can not
Is it only DLL or COM file can be references ?
I create a new project and try to compile and make it a reference
....can or can not ?
"Scott M." <s-***@BADSPAMsnet.net> wrote in message
news:#3**************@TK2MSFTNGP10.phx.gbl...
> Compile them just as you would any assembly. Reference them as you
would > any assembly. Once they are referenced, you can instantiate the classes in
> the modules.
>
> Are you saying you don't know how to compile and make references?
If so, > that is a completely different issue. If you are using VS.NET,
"build" your
> assembly (compile) from the Build menu. If not using VS.NET, use
the > command line compilers.
>
>
> " A-PK" <pi********@hotmail.com> wrote in message
> news:Oc**************@tk2msftngp13.phx.gbl...
> > how to compile them and make those project readable and can
reference them
> ?
> >
> > "Scott M." <s-***@BADSPAMsnet.net> wrote in message
> > news:OY**************@tk2msftngp13.phx.gbl...
> > > If you want to take this approach, you'll need to create each module in
> > its
> > > own solution, which will compile it to its own assembly. For
example, > one
> > > solution could be the module that describes data classes and another > could
> > > describe business classes.
> > >
> > > Search MSDN.Microsoft.com, keyword "assemblies" for more.
> > >
> > >
> > > " A-PK" <pi********@hotmail.com> wrote in message
> > > news:uQ***************@tk2msftngp13.phx.gbl...
> > > > Anyone know how to breakdown every modules into different
assemblies > > > >
> > > > and refernces. Hence, to repair problematic module, only that
> > > >
> > > > particular module needed to be recompiled.
> > > >
> > > >
> > > > or any place can get more information about assemblies &
references > > > >
> > > >
> > >
> > >
> >
> >
>
>
I have a concern which follows on from this discussion.
I am building a .NET application made up of multiple assemblies
(projects) in a single solution. The projects are decoupled as much as
possible so that only a few interfaces are exposed between projects.
But....
Whenever I touch any code in a more fundamental project (say, Storage),
ALL files are recompiled in ALL projects that reference this changed
project.
This is unacceptable! At the moment the compile times are not large as
the project is still at POC stage but I expect the code space to
increase at least 100 to 1000 fold.
Am I missing something, or is this deliberate? Surely VS can determine
whether any exposed types have been changed rather than taking what
appears to be the most pessimistic approach.
Any information would be very much appreciated.
Whatever .dll you want to reference should already be compiled into its
final form (.dll or .exe) before you reference it. The project that needs
to use the referenced .dll need not be compiled to make the reference, but
certainly needs to be compiled in order for its code to run (and therefore
use the referenced assembly).
i have compile my file to dll, and able to make references, i wonder if i
dun compile to dll (class), could I still make reference to my project ?
As I stated, you need to have whatever you want to reference already
compiled, because the compiled assembly is what you make a reference to.
The project that is making the reference needs to be compiled to run, but
not to make a reference. An example of this is that a brand new project in
VS.NET will already have references to commonly used .NET assemblies
(system.dll, mscoree.dll, etc.) before you even begin.
---
If you whish to reply to me directly, my addres is spam proofed as:
pbromley at adi dot co dot nz
Or if you prefer - no****@nowhere.com :-)
When you make a reference to a .NET assembly, a COPY of that assembly is
placed in your application's /bin folder. If the assembly you are
referencing were to change AFTER you've made your reference to it, you will
not see those changes in your project UNLESS you recompile (which causes new
copies of referenced assemblies to be gotten).
This is the behavior that you are describing and it is by design. I
understand that if the public interface of an assembly doesn't change that
there shouldn't be the need to go get a new copy of it, but that is the
behavior.
However, if you are in production and you need to update one of the
satellite assemblies that your application uses and you know that the
interface for that assembly has not changed, you can simple replace the old
assembly with the new one and you would NOT have to recompile the main
application.
"Peter Bromley" <no****@nowhere.com> wrote in message
news:Ow**************@tk2msftngp13.phx.gbl... I have a concern which follows on from this discussion.
I am building a .NET application made up of multiple assemblies
(projects) in a single solution. The projects are decoupled as much as
possible so that only a few interfaces are exposed between projects.
But....
Whenever I touch any code in a more fundamental project (say, Storage),
ALL files are recompiled in ALL projects that reference this changed
project.
This is unacceptable! At the moment the compile times are not large as
the project is still at POC stage but I expect the code space to
increase at least 100 to 1000 fold.
Am I missing something, or is this deliberate? Surely VS can determine
whether any exposed types have been changed rather than taking what
appears to be the most pessimistic approach.
Any information would be very much appreciated.
Whatever .dll you want to reference should already be compiled into its
final form (.dll or .exe) before you reference it. The project that
needs to use the referenced .dll need not be compiled to make the reference,
but certainly needs to be compiled in order for its code to run (and
therefore use the referenced assembly).
i have compile my file to dll, and able to make references, i wonder if
idun compile to dll (class), could I still make reference to my project ?
As I stated, you need to have whatever you want to reference already
compiled, because the compiled assembly is what you make a reference to.
The project that is making the reference needs to be compiled to run,
but not to make a reference. An example of this is that a brand new project
in VS.NET will already have references to commonly used .NET assemblies
(system.dll, mscoree.dll, etc.) before you even begin.
---
If you whish to reply to me directly, my addres is spam proofed as:
pbromley at adi dot co dot nz
Or if you prefer - no****@nowhere.com :-)
Hi Scott,
thank for guiding me the reference and assemblies.
i got one more question.
if my .dll path is not fixed, how could I add .dll files to be the
referecens.
In other word, how could I change the .dll path in run times. thank you
That's a tough one. Try looking into creating "Shared Assemblies" & the
"Global Assembly Cache". But I'm not sure if this will do it.
" A-PK" <pi********@hotmail.com> wrote in message
news:OX**************@TK2MSFTNGP10.phx.gbl... Hi Scott,
thank for guiding me the reference and assemblies.
i got one more question.
if my .dll path is not fixed, how could I add .dll files to be the
referecens.
In other word, how could I change the .dll path in run times. thank you
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: A-PK |
last post by:
Anyone know how to breakdown every modules into different assemblies
and refernces. Hence, to repair problematic module, only that
particular module needed to be recompiled.
or any place...
|
by: Afaq |
last post by:
Hi,
After adding large number of empty resource files (which will be updated
later), we are not able to compile the project. the following is the output
of the build process. It fails while...
|
by: Dan |
last post by:
Here's a scenario I'd like to discuss in order to setup my VS.NET IDE
properly and be able to prepare a distribution:
a) I have a windows forms C# app using 3 shared assemblies I developed to...
|
by: Invalidlastname |
last post by:
Hi,
We developed some assemblies which use EnterpriseServices queued components.
In order to use EnterpriseServices, these assemblies need to be installed
into GAC. I used the pre-build and...
|
by: Arpan |
last post by:
Assume that I am creating ASP.NET pages in the C:\Inetpub\wwwroot\ASPX
directory. This directory has a sub-directory named \bin where in all
DLLs are stored. Are these DLLs which are stored in the...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: ryjfgjl |
last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
| |
