On the .NET platform, the code is run in the form of an intermediate language, which is the basis of a large advantage of .NET. But in stand-alone desktop applications, it brings a threat to the security of source code. This article explores the cause of this problem and analyzes possible solutions.
In the Visual Studio.NET (VS.NET) system, the compiler such as VB, Visual C , and C # compiles the source program into MSIL. MSIL, or Microsoft Intermediate Language, it is compiled as a machine language before execution (Just-in-Time Compile, JIT). However, you may have nothing to know more about when you click the Build button in VS, or if your private source code and information are safe in front of the voyeur, when you put the IL code to the customer if you guarantee The code is not tampered with. Below we will deeply go deep into .NET's internal work process, explore the characteristics of VB.NET system MSIL and some questions you have to care.
You have to figure out the following questions. First, .NET is designed for client / server systems and web applications. Software development is gradually developing to the Internet and client / server-based applications, many applications no longer have traditional interface interfaces, but providing interfaces with browsers. .NET also follows this trend.
Second, in desktop applications, we cannot protect the code in the form of managed MSIL, if you feel very important to protect intellectual property (ie, source code), then .NET is not suitable for desktop applications. Although MSIL's commitment is heart-moving, although .NET platform and CLR (Common language runtime are very stable, from a secure point of view, all of this lacks practical significance for an independent desktop application. In .NET, as a VB programmer or even C # programmer, you can only write management, unprotected code.
Due to this limit, if you want to protect the code in your desktop app, you must use non-managed C . The only truly effective way to protect intellectual property is: use non-managed C component package code, then call it through the COM collaboration interface from the .NET managed code.
You must also clearly, because Active Server Pages.Net (ASP.NET) is running all over the server, ASP.NET applications are safe. In fact, this is the ideal realm of .NET - run code on protected servers, so that the code is far from anyone who wants to study it. ASP.NET simplifies web development to an unbelievable level, and Visual Basic.net is a good tool for writing ASP.NET applications.
Master VB.NET needs to learn hardships, and comprehensive acceptance .NET is a slow process. Migrating from VB6 to VB.NET is not easy, you still need to provide support for VB6 applications in time before the VB6 app is ported to VB.NET. Many developers will still use VB6 in a long time in the future.
