Dedicated and resolute C# Software Developer/Programmer with experience using object oriented design techniques and programming languages, including Microsoft .NET Technologies.
SharePoint2013 training in bangalore from vensys it services pvt. ltdsharepointexpert
SharePoint2013 training in bangalore,SharePoint2013 Developers training in bangalore,SharePoint2013 Administration training in bangalore,SharePoint2013 Admin training in bangalore,SharePoint2013 development training in bangalore
Adapt proposed and developed an Email Management System where all the emails related to a project can be created, stored and later on retrieved. It involved integrations with exchange, add on for outlook, and offline application to be built. Please read below to get the glimpse of the solution.
Why powerapps is replacing infopath forms Concetto Labs
While PowerApps is still growing and formulating features, it is ready to replace Infopath Forms. It could be in the form of creating interactive forms and modifying the SharePoint list and library dialogs
SharePoint2013 training in bangalore from vensys it services pvt. ltdsharepointexpert
SharePoint2013 training in bangalore,SharePoint2013 Developers training in bangalore,SharePoint2013 Administration training in bangalore,SharePoint2013 Admin training in bangalore,SharePoint2013 development training in bangalore
Adapt proposed and developed an Email Management System where all the emails related to a project can be created, stored and later on retrieved. It involved integrations with exchange, add on for outlook, and offline application to be built. Please read below to get the glimpse of the solution.
Why powerapps is replacing infopath forms Concetto Labs
While PowerApps is still growing and formulating features, it is ready to replace Infopath Forms. It could be in the form of creating interactive forms and modifying the SharePoint list and library dialogs
After you complete this module, you should be able to:
- Navigate the web client interface
- View requirement artifacts and information about them, both at the project level and in modules
- Use filters to focus on relevant information
- Change display settings to reveal relevant details
- Quickly switch perspectives of the requirements information by using views
- Use comments on artifacts to collaborate
- Use dashboards for lifecycle and progress analysis
Lecture 3: Navigating the Requirements Management application: Web clientIBM Rational software
After you complete this module, you should be able to:
► Navigate the web client interface
► View requirement artifacts and information about them, both at the project level and in modules
► Use filters to focus on relevant information
► Change display settings to reveal relevant details
► Quickly switch perspectives of the requirements information by using views
► Use comments on artifacts to collaborate
► Use dashboards for lifecycle and progress analysis
3. .NET Framework Project Objective For this project, the objective was to create the business tier for a retail company. This was achieved by creating and testing two assemblies: Foundation and AppTypes. Summary The AppTypes assembly is a Class library project that contains many entity, collection and exception classes that are used to facilitate most of the business processes. The Foundation assembly is a Class library project that contains the base classes and interfaces used in the project. This project focused predominantly on the various aspects of .NET Object-oriented programming with C#. Some of the highlights of this project include the use of C# properties, abstract classes and methods, inheritance, method overloading and overriding, interfaces, attributes, enums, custom exceptions, generics, delegates and collections.
6. Library Phase 1 Project Objective For this project, the objective was to create a Windows Forms-based application that would serve as the user interface tier to the supplied library book management database. This visual interface is responsible for providing a librarian with access to the day-to-day actions preformed in a library. Summary The focus of this project was on Windows Forms programming and it was built with an N-tiered approach in mind. The Business layer, The Data Access layer and the database where provided, so I was responsible for creating an effective front-end application to work with what was given. Requirements Design and develop a front end application that satisfies the four basic functionalities: Add Adult, Add Juvenile, Check-In a book and Check-Out a book. Develop code that is easily maintainable. Provide validation for all required fields. Provide adequate error handling. Provide a user interface that is intuitive, requiring minimal training for users while minimizing resource utilization.
7. Add Adult and Juvenile Member Forms Library Phase 1 Project
8. Check In and Check Out Forms Library Phase 1 Project
11. Library Phase 2 Project Objective For this project, the objective was to write my own Business and Data Access layers replacing the layers that were provided in Phase 1 while continuing to support the Windows Forms-based front-end application I created in Phase 1. Summary The focus of this project was predominantly on ADO.NET and T-SQL programming while keeping to the N-tiered structure used in Phase 1. I created T-SQL Stored Procedures for all the Library Functions (Check In, Check Out, Add Member, etc…) which were then called by the Data Access Layer methods. The Business Layer served to enforce the business logic and also to act as the middleman between the user interface and the Data Access Layer. I used ADO.NET to communicate with the database. Also, I chose to use Strongly Typed DataSets for this project to reduce the amount of coding required and also the likelihood of errors.
12. Library Phase 2 Project Requirements Design the Business and Data Access tiers. Develop code that is easily maintainable. Provide adequate error handling. Use database-programming techniques that provide maximum programming flexibility and control while minimizing resource utilization.
13. Check In Book Stored Procedure Library Phase 2 Project
14. Check In Book Stored Procedure (Continued) Library Phase 2 Project
15. Check In Book Data Access Layer Library Phase 2 Project
16. Library Phase 3 Project Objective For this project, the objective was to write a web application that supports all the functionality required in Phase 1 and 2 of the Library project. Summary The focus of this project centered around ASP.NET programming and keeping the N-tiered approach used in Phase 1 and Phase 2. The web application created for this project is meant to serve as an alternative user interface, while leaving the Phase 1 Windows Forms-based application unchanged and fully functional. This project will make use of the Business and Data Access layers I created in Phase 2. Highlights of this ASP.NET project include the use of master pages, membership and role management, forms-based authorization and authentication, data preservation using ViewState and Session State objects, partial page postbacks with Ajax, databindings, exception handling and input validation with validator controls.
17. Library Phase 3 Project Additional Requirements When displaying an adult’s membership information, the application should detect if the membership is expired and provide the librarian an option to renew the membership. Also, members with expired memberships cannot check out books. When working with juvenile members the application will check to ensure that the member is less then 18 years of age, if the member is older then 18 their membership will be automatically converted to an adult membership. Librarians must be able to enter new books into the database. All Overdue books, shown in the application must be highlighted. The design of the Member Information page must include the use of AJAX controls so that the check in and check out functionality cause only a partial page postback. The application must use hyperlinks to navigate between pages.