A few C# questions.

What is the difference between C# and Visual C#?

Are people mainly using C# creating Console Applications or Windows Forms applications?

Quote:

---

Originally Posted by maikeru-sama

Are people mainly using C# creating Console Applications or Windows Forms applications?

---

It depends on the application. At my office, we use C# maily for Windows Forms Apps, Web Services, Windows Services, and Web Sites.

C# is the programming language, which some people may call Visual C# anyway. Visual C# is the Microsoft IDE, which many will call just C# anyway, used to develop in C#.

Those who develop in C# use it for everything. You can create any type of application that will run on a Windows system in C#. Thanks to Mono you can also run C# apps on Unix/Linux-based systems.

Thanks for clearing that up JMC.

Quote:

---

Originally Posted by jmcilhinney

C# is the programming language, which some people may call Visual C# anyway. Visual C# is the Microsoft IDE, which many will call just C# anyway, used to develop in C#.

Those who develop in C# use it for everything. You can create any type of application that will run on a Windows system in C#. Thanks to Mono you can also run C# apps on Unix/Linux-based systems.

---

That was a whole lotta C#. :bigyello:

yeah it depends on what kind of project..right now, our team use ASP.NET 2.0 using C#...

And we use VC# 2005 as our IDE...

Greg

C Sharp could also be used to program into phone devices.

Quote:

---

Originally Posted by JenniferBabe

C Sharp could also be used to program into phone devices.

---

Can you not do this in VB.Net?

Reading through the book I bought, I had another question about Visibility Keywords.

I am trying to understand the meaning of the word Assembly when it is used in the context below:

internal = This member is accessible by any code within the assembly.

Does Assembly mean everything in the entire Project (Web/Win Form, Class, Module etc etc)?

An assembly is a .NET executable file, i.e. an EXE or a DLL. Each project you create that compiles to an EXE or a DLL represents an assembly. The idea of internal types and members is that any other assembly that references your DLL will not be able to see them, so they are for internal use only. My favourite example of this is the DataRow class. It is defined in the System.Data.dll assembly as a public class, but its constructor is declared internal. That means that it's not possible for any of us to create a DataRow object directly. We have to call the NewRow method of a DataTable to create a DataRow. Note that the DataTable class is also declared in the System.Data.dll assembly, so it IS able to access the DataRow constructor.

Any .NET language can be used to develop applications for any system that can run a CLR. Windows Mobile devices run a CLR so any .NET language can be used to develop for that platform.

Quote:

---

Originally Posted by jmcilhinney

An assembly is a .NET executable file, i.e. an EXE or a DLL. Each project you create that compiles to an EXE or a DLL represents an assembly. The idea of internal types and members is that any other assembly that references your DLL will not be able to see them, so they are for internal use only. My favourite example of this is the DataRow class. It is defined in the System.Data.dll assembly as a public class, but its constructor is declared internal. That means that it's not possible for any of us to create a DataRow object directly. We have to call the NewRow method of a DataTable to create a DataRow. Note that the DataTable class is also declared in the System.Data.dll assembly, so it IS able to access the DataRow constructor.

Any .NET language can be used to develop applications for any system that can run a CLR. Windows Mobile devices run a CLR so any .NET language can be used to develop for that platform.

---

Good stuff as usual JMC.