DLL Files
Kerdany
So, would you answer the following questions
1 ) Can we say that all different packages have different DLL files
2 ) When we compile any project, is it true that the classes of the package of that project is compiled
3 ) By knowing what DLL files means, now we can refer internal keywords. So Can we say that internal keyword has the same meaning with protected keyword in Java
Thanks
1 ) Can we say that all different packages have different DLL files
2 ) When we compile any project, is it true that the classes of the package of that project is compiled
3 ) By knowing what DLL files means, now we can refer internal keywords. So Can we say that internal keyword has the same meaning with protected keyword in Java
Thanks
Deltoid
Hi ,
Firstly thanks very much for your explanatory reply.
I also want to ask something about assemblies.
I think all assemblies are constructed by namespaces which include the classes that is compiled at that time, is not it
So, internal keywords provide us to access the only classes which are located in that namespace(Assembly's namespace), is it true
Firstly thanks very much for your explanatory reply.
I also want to ask something about assemblies.
I think all assemblies are constructed by namespaces which include the classes that is compiled at that time, is not it
So, internal keywords provide us to access the only classes which are located in that namespace(Assembly's namespace), is it true
TyTan
mert-1 wrote:
Oh,
I also add that my question is valid for the classes that are compiled at the same time(in the same Assembly).
Yes, then it should not give any errors.
tphsu
You can create an DLL so that you can easy deploy this with more projects.
There are no performance penalties, when a DLL is needed it will be loaded and it stays loaded untill the application ends.
For your development it can be handy to have multiple projects (DLL's) and for the update process it can be usefull to. The user doesn't have to download a very large .EXE file when you only updated one class for example. You can sepperate them by namespace, just as the .NET Framework does.
There are no performance penalties, when a DLL is needed it will be loaded and it stays loaded untill the application ends.
For your development it can be handy to have multiple projects (DLL's) and for the update process it can be usefull to. The user doesn't have to download a very large .EXE file when you only updated one class for example. You can sepperate them by namespace, just as the .NET Framework does.
- MyApp.Data < MyApp.Data.dll >
- MyApp.Data.Gateway
- MyApp.Data.Gateway.Mssql
- MyApp.Data.Gateway.Access
- MyApp.Data.Gateway.Webservice
- MyApp.Net < MyApp.Net.dll >
- MyApp.Net.Update
- MyApp.Drawing < MyApp.Drawing.dll >
- MyApp.Drawing.Imaging
Kevin.Ji
mert-1 wrote:
Hi ,
Firstly thanks very much for your explanatory reply.
I also want to ask something about assemblies.
I think all assemblies are constructed by namespaces which include the classes that is compiled at that time, is not it
So, internal keywords provide us to access the only classes which are located in that namespace(Assembly's namespace), is it true
This is correct indeed.
Quote of deleted reply
mert-1 wrote:
I heard that internal keyword means that the visiblity for classes which is kept in the same DLL library(File). So, I wonder that internal keywords provides the visibility for classses which are in the same namespaces.
No, the internal keyword is an access modifier for types and type members. Internal types or members are accessible only within files in the same assembly. You can read the full details and see and example here: internal (C# Reference).
mert-1 wrote:
The reason for my this opinion is that I know that DLL files is constructed by allocating the classes who have similar functions or are a little bit related with each other. For example, we use using keywords to call any class of ant specified namespaces. So, does it have the same meaning with this : we call the DLL files of the class that we wnat to use in our project (or files)
No, a DLL can contain one or more namespaces. Most of the time you have a Namespace like CompanyName.Controls and meybe extra namespaces related to it like CompanyName.Controls.Painting, CompanyName.Controls.Input and CompanyName.Controls.Grid.
mert-1 wrote:
And, Does creating namespaces have the same meaning with creating DLL files
No... the same reason as one quote above

DLL Files
jlang64
I also add that my question is valid for the classes that are compiled at the same time(in the same Assembly).
rankind
I supposed that at the below codes, that are form the link that you sent, should not have created any error since both class are in the same default namespaces as in the Java.
So I would like to ask that is not there any default namespaces concept in C#
So if there is, why does the following ocde snippets create an error
Efim
The namespace isn't related to the internal access modifier, it is the assembly that is creating the hence around your class.
Every class in every namespace can use your internal BaseClass as long as they are in the same assembly as the BaseClass.