2
Since I come from PHP and I’m starting now with ASP.NET and I’m pretty raw, I’ll need to argue about. NET to one of the owners of the company, and he develops in Intraweb. By my vision of WEB, the structure of . NET is much better to work, both structural and conceptual.
Until this part ok, the problem is when enters the "expanded" programming that they already have here, for example: In Intraweb, it has a "menu" component that comes from a DLL developed by him, it includes this DLL in the project, drops this menu in the application and the menu is already working, and in case he needs to change something or even fix a bug, it even goes to uses DLL, compiles and is already all right in all the menus of the applications of that extended menu. They do not want to migrate precisely because of this, they say . NET does not have this kind of thing.
Aaah, among other arguments like "recovery" form, because the form in Intraweb are objects, you can bring this object on the screen at any time and with all the data typed by the user, until you "destroy" the same...
I can do that on . NET?
Diego, isn’t Intraweb the framework that is made available by Delphi? If they already have a DLL, why don’t you try to open an Asp.net mvc project or even webform, and make an attempt to read the dll by the "Add Reference" of visual studio.
– Andre Mesquita