Download to read offline
Uploaded bySharbani Bhattacharya
Visual Basic User Interface-III
The document discusses various topics related to Visual Basic user interfaces and .NET architecture, including: - It describes 2-tier and 3-tier architectures and how .NET enables easier development of N-tier applications. - It discusses the benefits of .NET such as a common language runtime, support for multiple languages, and easier deployment. - It explains key aspects of .NET architecture like the common language runtime, .NET framework class library, and how .NET applications can be developed for different environments and user interfaces.
Engineeringâ—¦
More Related Content
Similar to Visual Basic User Interface-III
More from Sharbani Bhattacharya
Visual Basic User Interface-III
- 1. Sharbani Bhattacharya Visual Basic–User Interface-III Govt. Polytechnic(W) Faridabad 22nd - 26th September 2016
- 2. • .NET Concept& Visual Basic • Color Dialog • Font Dialog
- 3. 2- tier, 3-tier and then move on to N- tier Windows DNA. • Windows DNA is a concept for building distributed applications using the Microsoft • Windows operating system and related software products.
- 4. Application into LogicalLayers • Factoring an application into logical parts is useful. Breaking a large piece of software into smaller pieces can make it easier to build, easier to reuse and easier to modify.
- 5.
- 6. Presentation Layer • Thingsyou might find in a presentation layer include • A Web browser, • A terminal, • A custom-designed GUI, • A character-based user interface.
- 7. Presentation services •The Presentationservices are also called the presentation layer because it presents information to the user.
- 8. 2-Tier Architecture • Atwo-tiered application is an application whose functionality can only be segmented into two logical tiers, presentation services and data services.
- 9.
- 10. The presentation services3-tier • Gathering information from the user • Sending the user information to the business services for processing • Receiving the results of the business services processing • Presenting those results to the user
- 11. Business Services 3-tier • Receiving input from the presentation tier. • Interacting with the data services to perform the business operations. • Sending the processed results to the presentation tier.
- 12. Data Services 3-Tier •Storage of data. • Retrieval of data. • Maintenance of data. • Integrity of data.
- 13. Windows DNA Applications WindowsDNA applications commonly implement their business logic using one or more of three implementation options. • Asp Pages • COM components • Stored procedures running in the DBMS
- 14. Windows DNA • Win32clients and • Browser based clients
- 15. Limitations in Win32Clients The drawbacks is that such client software is difficult to deploy and maintain, requiring and install on every client and a change to every client when an upgrade is needed.
- 16. Limitations in Win32Clients DLL conflicts on the client are frequent because of variations in the version of them operating system and other software installed on the client.
- 17. Component Object Model •COM components, in the middle tier must work together, Versioning all the components properly so that they understand each other's interfaces can be a challenge. • This requires a highly sophisticated skill level and a well - controlled deployment process.
- 18. Microsoft.NET solutions • • SingleProgramming Model • Distributed Systems • Richer User Interface • Easy Deployment • Support for Multiple Languages • Extendibility • Portability of compiled Applications • Integrity with COM
- 19. Single Programming Model •A related goal is to have development for the internet environment look very much like development for other types of software. Likewise, developing user interfaces in Windows Forms is very similar to developing them in Web Forms. • There are commonly used controls, such as Labels and Text Boxes, in both, with similar sets of properties and method. The amount of commonality makes it easy to transition between the two types of development, and easier for traditional VB developers to start using Web Forms.
- 20. Distributed Systems • TheVision of Microsoft.NET is globally distributed systems, using XML as the universal glue to allow functions running on different computers across an organization or across the world to come together in a single application. • In this vision, systems from servers to Wireless Palmtops, with everything in between, will share the same general platform, with versions of .NET available for all of them, and with each of them able to integrate transparently with the others.
- 21. Richer User Interface •Web Forms are a giant step towards much richer web- based user interfaces. • Their built-in intelligence allows rich, browser- independent screens to be developed quickly, and to be easily integrated with compiled code. • Microsoft has announced an initiative for the future called the Universal Canvas which builds upon the XML standards to transform the internet from a Read only environment into a read/write platform, enabling users to interactively create, browse, edit and analyze information.
- 22. Easy Deployment • Executablemodules in .NET are self-describing. • Once the Common Language Runtime (CLR is explained in next sections) knows where a module resides, it can find out everything else it needs to know to run the module, such as the module’s object interface and security requirements, from the module itself. • Means a module can just be copied to a new environment and immediately executed.
- 23. Support for MultipleLanguages • The CLR executes binary code called MSIL (Microsoft intermediate language), and that code looks the same regardless of the original source language. All .NET – enabled languages use the same data types and the same interfacing conventions. • This makes possible for all .NET language to interoperate transparently. One language can call another easily, and languages can even inherit classes written in another language and extend them current platform has anywhere near this level of language interoperability.
- 24. Extendibility • The completelyobject based approach of .NET is designed to allow base functionality to be extended through inheritance ( unlike COM) and the platform’s functionality is appropriately partitioned to allow various parts( such as the just-in-time compilers discussed in the next section) to be replaced as new versions are needed. • It is likely that, in the future, new ways of interfacing to the outside world will be added to the current trio of windows Form, Web Forms, and Web Services such as universal Canvas.
- 25. Portability of compiled Applications •.NET allows the future possibility of movingsoftware to other hardware and operating system platforms. • The ultimate goal is that compiled code produced on one implementation of .NET (such as Windows) could be moved to another implementation of .NET on a different operating system merely by copying the compiled code over and running it.
- 26. Integrity with COM •.NET integrates very will with COM-based software. Any COM component can be treated as a .NET component by other .NET components. • The .NET Framework wraps COM components and exposes an interface that .NET components can work with. • This is absolutely essential to the quick acceptance of .NET, because it makes .NET interoperable with a tremendous amount of older COM-based software.
- 27. Benefits of using.NET Architecture • The Microsoft .NET platform's reliance on XML for data exchange—an open standard managed by the World Wide Web Consortium (W3C)—and modular XML • Web services removes barriers to data sharing and software integration. • The .NET platform, through the .NET Framework's common language runtime, enables XML Web services to interoperate whatever their source language. • Developers can build reusable XML Web services instead of monolithic applications. • By making it easy to offer your XML Web services to others.
- 28. Benefits of using.NET Architecture • The ability to easily find available XML Web services means you can buy pieces of your applications rather than build everything from scratch, focusing your time and money where it makes the most sense. • Easier to build sophisticated development tools – debuggers and profilers can target the Common Language Runtime, and thus become accessible to all .NET-enabled languages.
- 29. Benefits of using.NET Architecture • Potentially better performance in system level code for memory management, garbage collection, and the like have yielded an architecture that should meet or exceed performance of typical COM-based applications today.
- 30. Benefits of using.NET Architecture • Fewer bugs, as whole classes of bugs should be unknown in .NET. With the CLR handling memory management, garbage collection. • Faster development using development tool like visual studio.net
- 31. N-tier architecture with .NET •the tiers will be a lot easier to produce in.NET. The presentation tier will benefit from the new interface technologies and especially Web Forms for Internet development. • The middle tier will require far less COM-related headaches to develop and implement. And richer, more distributed middle tier designs will be possible by using Web Services.
- 32. n-tier Application with MultipleComponents
- 33. Constituents of .NET Platform •.NET Framework – a completely re-engineered development environment. • .NET Products – applications from MS based on the .NET platform, including Office and Visual Studio. • .NET Services – facilitates 3rd party developers to create services on the .NET Platform.
- 34. .NET Platform Architecture •At the bottom of the diagram is your Operating System above that sits the .NET framework that acts as an interface to it. • The .NET wraps the operating system, insulating software developed with .NET from most operating system specifics such as file handling and memory allocation.
- 35.
- 36. Common Language Runtime (CLR) •At the base is the CLR. It is considered as the heart of the .NET framework. • .NET applications are compiled to a common language known as Microsoft Intermediate Language or “IL”.
- 37. CLR • The CLR,then, handles the compiling the IL to machine language, at which point the program is executed.
- 38. CLR • The CLRenvironment is also referred to as a managed environment, in which common services, such as garbage collection and security, are automatically provided.
- 39. The .NET ClassFramework • The next layer up in the framework is called the .NET Class Framework also referred as .NET base class library. • The .NET Class Framework consists of several thousand type definitions, where each type exposes some functionality.
- 40. .NET Class Framework •Web Services. Components that can be accessed over the Internet very easily. • Web Forms. HTML based applications (Web Sites). • Windows Forms. Rich Windows GUI applications. Windows form applications can take advantage of controls, mouse and keyboard events and can talk directly to the underlying OS. • Windows Console Applications. Compilers, utilities and tools are typically implemented as console applications. • Windows Services. It is possible to build service applications controllable via the Windows Service Control Manager (SCM) using the .NET Framework. • Component Library. .NET Framework allows you to build stand- alone components (types) that may be easily incorporated into any of the above mentioned application types.
- 61.