General discussion

  • Creator
    Topic
  • #2177184

    Updateing To DOTNET

    Locked

    by j.p ·

    Im a software Engg. working on VB6. Now that i want to update myself to DOTNET specialy C#.Have read few topic on OOPS thr WROX C# Proff. But i need to know where and how to implement them in live project. how to analyze?

All Comments

  • Author
    Replies
    • #3251536

      Reply To: Updateing To DOTNET

      by hiteshnr16 ·

      In reply to Updateing To DOTNET

      It is great that you have thought of moving into DotNet and C# and seems that you are on the correct track.
      First of all get to u have a good grasp of OOps Technology. Secondly Get a sound understanding of all the namespaces and some of the important classes within them.
      Lastly, the answer to your question about where to implement them… It is simply EVERYWHERE due to its immense benefits.

      DotNet has many advantages like
      Interoperability :- .Net applications can interact with legacy applications written in VB and COM, so any new developoment can be done in .NET.

      Scalability :- Technologies like Web services, Remoting, ASP.NET Session maintainence make your apps highly scalable, which is another place you can use .NET.

      Besides the above, There is a very RICH set of base classes provided by the .Net framework for Networking, Web Services, Web applications,Data Access ( for various data sources, and more which helps you achieve solutions for complex technologies in a good manner.

    • #3234934

      Reply To: Updateing To DOTNET

      by softcorp.us ·

      In reply to Updateing To DOTNET

      Hello…

      Something more…

      .NET provides many benefits and is very exciting. I love .NET. But, if you have any experience at all, you will then ask: “Now…what should I look out for?”.

      Be wary of performance in real-world applications written in .NET managed code. Two key points to note are:

      1. The compilers generate non-native code (MSIL).

      Later, as each .EXE is loaded, that intermediate code is converted into native binary so it can be executed. Of course, it is cached so this generally does not have to occur every time the .EXE is loaded.

      2. Application performance is greatly affected by the very large .NET Framework that you have no control of.

      Just remember that there is never a free lunch and you will be OK.

      —–Steve Jackson

      CEO/CSA
      Software Corporation (Softcorp)
      http://www.softcorp.us/probono
      Advanced pro bono tools and utilities free for personal use

    • #3244871

      Reply To: Updateing To DOTNET

      by dotby ·

      In reply to Updateing To DOTNET

      And one more thing – I’ve heard that code compiles while running? Okay, thats right… BUT there is a small utility NGEN.EXE provided with .NET SDK. It can compile code direct to “executable cached”. .NET Framework checks your exe: if it’s MSILed – code will be compiled, if it’s compiled with NGEN – it will be run immediately… Boost your app!

Viewing 2 reply threads