What is the equivalant of a 'friend' keyword in C Sharp?

You can use the keyword access modifier internal to declare a type or type member as accessible to code in the same assembly only You can use the InternalsVisibleToAttribute class defined in System.Rutime. CompilerServices to declare a type as accessible to code in the same assembly or a specified assembly only You use the first as you use any other access modifier such as private To wit: internal class MyClass { ... } You use the second as follows: assembly:InternalsVisibleTo("MyFriendAssembly", PublicKey="...") internal class MyVisibleClass { ... } Both of these can rightly be considered the equivalent of friend in C Methods that are protected are already available to derived classes.

You can use the keyword access modifier internal to declare a type or type member as accessible to code in the same assembly only. You can use the InternalsVisibleToAttribute class defined in System.Rutime. CompilerServices to declare a type as accessible to code in the same assembly or a specified assembly only.

You use the first as you use any other access modifier such as private. To wit: internal class MyClass { ... } You use the second as follows: assembly:InternalsVisibleTo("MyFriendAssembly", PublicKey="...") internal class MyVisibleClass { ... } Both of these can rightly be considered the equivalent of friend in C#. Methods that are protected are already available to derived classes.

I think you are looking for internal. This page has a pretty comprehensive comparison of VB/C#. As others have said, though, subclasses do have access to protected methods so you should already see them.

1) Internal is the C# equivelant of the VB. NET 'friend' keyword, as you have guessed (as opposed to a replacement) 2) Usage is as follows internal void Function() {} internal Class Classname() {} internal int myInt; internal int MyProperty { get; set; } 3) It, basically, is an access modifier that stipulates that the accessibility of the class / function / vairiable / property marked as internal is as if it were public to the Assembly it is compiled in, and private to any other assemblies.

Internal is the equivalent of friend. A protected method is only available within the same class or from an inheritor. If you're trying to expose protected methods from an inheritor, you can wrap them in public methods.

No, "internal" is not the same as "friend" (at least the C++ 'friend') friend specifies that this class is only accessible by ONE, particular class. Internal specifies that this class is accessible by ANY class in the assembly.

Your subclass will be able to access the protected members of the class you inherit. Are you looking to give access to these protected members to another class?

If you create a class on the same project as the source code you've received, and you don't inherit the source code's classes, yet you want have access to those protected methods, make those methods internal. But if you want to purely inherit the the class(be it on same project or different one), no need to change those protected to internal. You can merrily inherit the class and have access those protected methods at the same time.

That being said, there's a reason why some of the methods in the source code you've received has protected access on methods instead of internal/friend. Methods are marked as protected to allow 3rd party developers who inherits from those class and let them have an access on those methods(protected) even they are in binary form (i.e. DLL).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.