If you are a vendor of a desktop app, you know what you should do. You can write code with non-managed C and then call it from managed VB. Design application with this method, you can confirm the security of the code. However, if you are a third-party vendor, and prepare to replace the managed code with non-managed code in the component, you are to force users to give up .NET advantage, let them face them today The problem. Managed code prevents destructive operations from memory spaces used by the application itself or other applications, and is one of the reasons for the support of managed code. Some users may view the IL programs of the managed code, and even possible to analyze the application's algorithm implementation. If you don't correctly understand the advantage of .NET, third-party suppliers may refuse to use managed Code writes a variety of software components.
Vb.net/vs.net has many advantages, just the reason for the IDE (integrated development environment) is enough to be our reason for us to upgrade to VB.NET; linguistic enhancement brings us a lot of new programming support, for the bottom The simplification of the OS access makes our declaring variables, objects, and call low-level functions more convenient. VB.NET is an excellent tool for creating security ASP.NET applications; however, if your primary goals are concentrated in the client or desktop applications, you should carefully consider the possible problems. What help is Microsoft to provide desktop app developers? We will wait and see.
