Crystal translation-yesky
We are very fond of this function for COM objects that no longer need to be registered on the server. However, with this process simplified, we may not
Enable a pot of worms. One reason for these nightmares hiding behind the DLL (as we hate it) is that it enhances the confidentiality of the version. You
It is no longer possible to run another DLL version on your server, and the code is fairly confidential, which means that without the correct development tools and source code,
It is difficult to change the code.
This security mechanism has now been deleted. You can run any DLL version on your server, which may cause various
Headaches and security issues.
Another great convenience for many developers who like COM objects is that you can package your business logic, and no one else can see it ----
Objects are compiled, so you cannot see them. In the new framework, you must use applications to distribute source files, because NGWS will certainly track
Path of the source file. End users can browse or modify the code as they wish. Of course, you can also compile the object, or do not give the source file,
As a result, you will lose some of the convenience functions provided by NGWS, which is not worth the candle.
You also need to pay close attention to some things beyond Source control that may be used by those entering your file (for example, Visual Source Safe ). So any use
Users can easily access or modify your objects, so think about those hackers.
These issues also apply to XML. Anyone can easily hack you.
Adaptability
Certainly, it usually takes some time for any new technology to penetrate the market. Microsoft is starting to allow ASP and IIS platforms to pass industry verification,
So that it can be used as a platform outside of other network servers.
It is difficult to persuade customers or developers to discard the methods they used before to switch to the existing methods for such a huge change in their basic architecture.
Method. Of course, with the passage of time, the problem will always be solved slowly, but in fact, ASP + is expected to be accepted by the market, and it is facing an obstacle.
To find high-quality solutions and technical support problems. In fact, ASP.net is still an alpha technology, but is seeking to support
It is so lucky.
Existing Code
Of course, you have to rewrite all your existing code before converting the system to ASP.net. Your old code will still work in IIS,
You will still use the traditional ASP framework (this is not a bad thing ). Of course, porting a huge web application to ASP.net is very painful.
Program, especially if you already have a large number of solutions or COM objects.
ASP. NET code compilation
Let me reiterate that the ASP. NET code has been compiled now. Don't be nervous. This is not what you think. You don't need to create a file, so you have to re-register parts.
Don't stop and restart. Now you don't need to do this. You only need to write the code as usual and still benefit from the early bundling. The system will compile it in time,