why do i want to learn C#?

[kypeswith]

i've been learning C++ in my spare time, but i've been thinking about learning C#. i've just now begun to learn OOP and later plan to learn windows programming. also i dabbled in assembly, but found out all i would do with it is reverse engineer something.. any thoughts or comments are welcome

[kypeswith]

i've been learning C++ in my spare time, but i've been thinking about learning C#. i've just now begun to learn OOP and later plan to learn windows programming. also i dabbled in assembly, but found out all i would do with it is reverse engineer something.. any thoughts or comments are welcome

[kypeswith]

i've been learning C++ in my spare time, but i've been thinking about learning C#. i've just now begun to learn OOP and later plan to learn windows programming. also i dabbled in assembly, but found out all i would do with it is reverse engineer something.. any thoughts or comments are welcome

[Guest Wolfeymole]

I've no doubt Mike (Owner and Administrator) will offer his thoughts on this shortly Kype.

 

Stick around mate.

[Guest Wolfeymole]

I've no doubt Mike (Owner and Administrator) will offer his thoughts on this shortly Kype.

 

Stick around mate.

[Guest Wolfeymole]

I've no doubt Mike (Owner and Administrator) will offer his thoughts on this shortly Kype.

 

Stick around mate.

[mike]

Hi Kypeswith,

 

Interesting topic you bring up...

 

I am no expert in C++ or C#, my forte is in Web Developing. Having said that, I have learnt a bit of Assembly and C++.

 

I'll start with Assembly, the lowest level of programming we can get - unless you want to program in 1's & 0's! :) - Knowing such a language is extremely useful for reverse engineering as you said. But also, it is taught in a lot of Universities because it helps Students understand how the CPU actually works with its registers, caches, memory location etc.

 

Your C++ and C# code in turn is compiled into Assembly language anyway, so "but found out all i would do with it is reverse engineer something" is simply not true :P

 

I have some good resources from my Uni on Assembly Language, but unfortunately i can not distribute them. Have a look at this website though, it appears to be pretty good.

 

Art of Assembly Language Programming and HLA by Randall Hyde

 

Secondly, C++ vs C#... There is much debate on which is better. I think it comes down to what you actually want to accomplish. C# was developed by Microsoft and has its roots based on C++ and Java. It is a OOP language and is part of the .Net framework so it would be a good choice to learn as your wanting to develop Windows Applications and it is easy to design interfaces due to the UI packages available in the .Net platform.

 

I’d suggest to learn the basics of C# and its syntax and then learn and understand OOP concepts and apply this to C#.

 

Hope this helps,

Mike

[mike]

Hi Kypeswith,

 

Interesting topic you bring up...

 

I am no expert in C++ or C#, my forte is in Web Developing. Having said that, I have learnt a bit of Assembly and C++.

 

I'll start with Assembly, the lowest level of programming we can get - unless you want to program in 1's & 0's! :) - Knowing such a language is extremely useful for reverse engineering as you said. But also, it is taught in a lot of Universities because it helps Students understand how the CPU actually works with its registers, caches, memory location etc.

 

Your C++ and C# code in turn is compiled into Assembly language anyway, so "but found out all i would do with it is reverse engineer something" is simply not true :P

 

I have some good resources from my Uni on Assembly Language, but unfortunately i can not distribute them. Have a look at this website though, it appears to be pretty good.

 

Art of Assembly Language Programming and HLA by Randall Hyde

 

Secondly, C++ vs C#... There is much debate on which is better. I think it comes down to what you actually want to accomplish. C# was developed by Microsoft and has its roots based on C++ and Java. It is a OOP language and is part of the .Net framework so it would be a good choice to learn as your wanting to develop Windows Applications and it is easy to design interfaces due to the UI packages available in the .Net platform.

 

I’d suggest to learn the basics of C# and its syntax and then learn and understand OOP concepts and apply this to C#.

 

Hope this helps,

Mike

[mike]

Hi Kypeswith,

 

Interesting topic you bring up...

 

I am no expert in C++ or C#, my forte is in Web Developing. Having said that, I have learnt a bit of Assembly and C++.

 

I'll start with Assembly, the lowest level of programming we can get - unless you want to program in 1's & 0's! :) - Knowing such a language is extremely useful for reverse engineering as you said. But also, it is taught in a lot of Universities because it helps Students understand how the CPU actually works with its registers, caches, memory location etc.

 

Your C++ and C# code in turn is compiled into Assembly language anyway, so "but found out all i would do with it is reverse engineer something" is simply not true :P

 

I have some good resources from my Uni on Assembly Language, but unfortunately i can not distribute them. Have a look at this website though, it appears to be pretty good.

 

Art of Assembly Language Programming and HLA by Randall Hyde

 

Secondly, C++ vs C#... There is much debate on which is better. I think it comes down to what you actually want to accomplish. C# was developed by Microsoft and has its roots based on C++ and Java. It is a OOP language and is part of the .Net framework so it would be a good choice to learn as your wanting to develop Windows Applications and it is easy to design interfaces due to the UI packages available in the .Net platform.

 

I’d suggest to learn the basics of C# and its syntax and then learn and understand OOP concepts and apply this to C#.

 

Hope this helps,

Mike

[kypeswith]

hey that website on assembly is great! any idea why my hello world program is 5kilobytes compared to 39kilobytes (39 in C++ and 5 in assembly)

[kypeswith]

hey that website on assembly is great! any idea why my hello world program is 5kilobytes compared to 39kilobytes (39 in C++ and 5 in assembly)

[kypeswith]

hey that website on assembly is great! any idea why my hello world program is 5kilobytes compared to 39kilobytes (39 in C++ and 5 in assembly)

[kypeswith]

is it true that assembly programming can damage hardware?

[kypeswith]

is it true that assembly programming can damage hardware?

[kypeswith]

is it true that assembly programming can damage hardware?

[mike]

Hi Kypeswith,

 

I would not think that Assembly could damage hardware. However it is very 'sensitive' language.

 

There are no rules / validation, it is up to you to ensure that your Data and Instructions do not combine. Also, it is very easy to merge two or more variables together by accident.

 

As such it is possible to access / change data that is not part of your program, thus crashing other programs.

 

If you use a Simulator to test your code, this should not be a problem as it should tell you. However, if you do not it will be very hard to debug your code and could cause problems for other programs.

[mike]

Hi Kypeswith,

 

I would not think that Assembly could damage hardware. However it is very 'sensitive' language.

 

There are no rules / validation, it is up to you to ensure that your Data and Instructions do not combine. Also, it is very easy to merge two or more variables together by accident.

 

As such it is possible to access / change data that is not part of your program, thus crashing other programs.

 

If you use a Simulator to test your code, this should not be a problem as it should tell you. However, if you do not it will be very hard to debug your code and could cause problems for other programs.

[mike]

Hi Kypeswith,

 

I would not think that Assembly could damage hardware. However it is very 'sensitive' language.

 

There are no rules / validation, it is up to you to ensure that your Data and Instructions do not combine. Also, it is very easy to merge two or more variables together by accident.

 

As such it is possible to access / change data that is not part of your program, thus crashing other programs.

 

If you use a Simulator to test your code, this should not be a problem as it should tell you. However, if you do not it will be very hard to debug your code and could cause problems for other programs.

[DirtyPolo]

  kypeswith said:

hey that website on assembly is great! any idea why my hello world program is 5kilobytes compared to 39kilobytes (39 in C++ and 5 in assembly)

 

My guess would be that because Assembly is a lower level programming language than C++, it will use up less space, as programs made in C++ must first be converted into "Machine code" which takes more steps to do to a C++ code than it does for Assembly :P

 

That is why an OS takes up so little room but is able to do so much when coded in Assembly.

[DirtyPolo]

  kypeswith said:

hey that website on assembly is great! any idea why my hello world program is 5kilobytes compared to 39kilobytes (39 in C++ and 5 in assembly)

 

My guess would be that because Assembly is a lower level programming language than C++, it will use up less space, as programs made in C++ must first be converted into "Machine code" which takes more steps to do to a C++ code than it does for Assembly :P

 

That is why an OS takes up so little room but is able to do so much when coded in Assembly.

[DirtyPolo]

  kypeswith said:

hey that website on assembly is great! any idea why my hello world program is 5kilobytes compared to 39kilobytes (39 in C++ and 5 in assembly)

 

My guess would be that because Assembly is a lower level programming language than C++, it will use up less space, as programs made in C++ must first be converted into "Machine code" which takes more steps to do to a C++ code than it does for Assembly :P

 

That is why an OS takes up so little room but is able to do so much when coded in Assembly.

[kypeswith]

so much for protected mode

[kypeswith]

so much for protected mode

[kypeswith]

so much for protected mode