Suksvl Vki Lcdh Lgk;Rk Dsfy, Cuk;Sx;Sgsa a ;S Uksvl Ljy Hkk'kk Esa

Total Page:16

File Type:pdf, Size:1020Kb

Suksvl Vki Lcdh Lgk;Rk Dsfy, Cuk;Sx;Sgsa a ;S Uksvl Ljy Hkk'kk Esa .NET Programming 1 www.ashagroup.org fiz; fo|kfFkZ;ksa] ;s uksV~l vki lcdh lgk;rk ds fy, cuk;s x;s gSaA ;s uksV~l ljy Hkk’kk esa cuk;s x;s gSaA bu uksV~l dks i<+dj vki fofHkUu ijh{kkvksa dh rS;kjh dj ldrs gSaA bu uksV~l ds ckjs esa vki vius lkfFk;ksa tkudkjksa o fj”rsnkjksa dks Hkh crk ldrs gSaA budks cukus esa dkQh le; o esgur yxh gSA buesa dqN =qfVa;k o xyfr;ka gks ldrh gSA dqN VkWfid de gks ldrs gSa blds ckjs esa vki gesa lwfpr dj ldrs gSaA /kU;okn .NET Programming 2 www.ashagroup.org UNIT- I Introduction to .NET Framework: In July 2000 Microsoft announced a whole new software development framework for Windows called .NET in the Professional Developer Conference (PDC). In March 2002 Microsoft released final version of the .NET framework. We can develop various varieties of applications in it. It provides complete SDK (Software Development Kit). In .NET SDK classes, interfaces and language compilers are included. The Microsoft .NET framework 2.0 includes 18619 types 12909 classes 401759 public method, 93105 public property 30546 public events. Now we are using .NET framework 4.0 and 4.5. If we are developing powerful applications then we may require some IDE (Integrated Development Environment) that allows us rapid action development. The new visual studio.NET provides such IDE. There is various versions of VS such as VS 2008, 2010, 2012, 2013 are available. Terminology: To understand .NET framework properly we must have knowledge of some important terminologies. Common Language Runtime CLR: An important part of .NET framework is CLR (Common Language Runtime). CLR is responsible for executing our application code. It performs memory management, exception handling, debugging, security checking, thread execution, code execution, code safety, verification and compilation. Those codes which are directly managed by the CLR are called the managed code. MSIL (Microsoft Intermediate Language): When we write an application for the .NET framework with any language our source code is compiled directly into machine code. Instead our code is converted into a special language name MSIL (Microsoft Intermediate Language). MSIL is a low level and platform independent language. In reality the .NET framework understands only one language MSIL. We can write application using any language such as VB.NET, C++, Ada, COBOL, Fortran, Pascal, PHP, Perl, Java script and many more. The .NET framework includes compiler for these language that enables us to compile our code into MSIL. A Just in time compiler (JIT) compiles the IL code into native code, which is CPU specific. Framework Class Library: It contains a huge library of reusable types, classes, interfaces, structures and enumerated values, which are collectively called types. The .NET framework contains thousands of .NET Programming 3 www.ashagroup.org classes those we can use when building an application. The framework class library was designed to make it easier to perform most common programming tasks. Common Language Specification: It contains the specifications for the .Net supported languages and implementation of language integration. Common Type System: It provides guidelines for declaring, using and managing types at runtime, and cross-language communication. Namespaces: There are lots of classes in .NET framework. Microsoft divided the classes in framework into separate namespaces is simply a category to store the classes. Before we use a class in the program we must indicate the related namespace with the class name. Assemblies: An assembly is the actual .DLL (Dynamic Linking Library) file on our hard disk, where the classes in the .NET framework are stored. In other words an assembly is the primary unit of deployment, security and version control in the .NET framework, because an assembly can span multiple files. An assembly is often referred to as a logical DLL. Metadata: is the binary information describing the program, which is either stored in a portable executable file (PE) or in the memory. C# (Sharp) and .NET: C# is a simple, modern, object oriented and type safe programming language derived from C and C++. C# language was developed by small team of Microsoft engineer Anders Hejlsberg and Scott Wiltamuth. Hejlsberg is also known for creating Turbo Pascal. C# supports .NET framework and similar to java programming language. C# is a multi-paradigm programming language that encompasses functional, imperative, generic, object and component oriented programming disciplines. C# is one of the 44 programming languages supported by the .NET framework common language runtime. It was initially named cool which stood for C like Object Oriented Language. However in July 2000 when Microsoft made the project public the name of programming language was given as C#. Managed Execution Environment: The comparison between (C# / IL Code / CLR) and (Java / Bytecode / JVM) is an inevitable and valid comparison to make. With C and C++ we generally compile the source code to assembly language which will run on a .NET Programming 4 www.ashagroup.org particular processor and a particular operating system. The compiler need to know which processor and operating system it is targeting, because processor may vary in instruction sets and operating system may vary in its functions. C and C++ model has been very successful but has its limitations. Program interface do not interact with other programs. Microsoft COM (Component Object Model) was built to address this problem. Program can’t be used on different platforms. Java addressed these problems by interpreting program to bytecode which then runs on a virtual machine. This bytecode is machine independent which means the same class file can be used on number of platforms. But the interpretation is very slow process and it is never appealing to the performance conscious programmer. Today most JVM (Java Virtual Machine) use a Just In Time (JIT) compiler to make compilation fast. The basic model .NET uses the same as described above. The IL (MSIL) code has some improvements over byte code. 1. To provide greater type neutrality (helps implementation of templates). 2. To provide greater language neutrality. 3. To always be compiled to assembly language before executing and never interpreted. Similarities and Differences from Java: C++ and Java have many similarities. We can discuss these similarities and differences as follows:- Both have powerful reflection capabilities. C++ always uses .(dot) operator instead of arrow or scope resolution operator. Null, Boolean / Bool keywords area available. Garbage collection coupled with the elimination of pointers. Compiles into machine independent codes. Java generates bytecode and C# generate IL code. No header files, all code scoped to package or assemblies. No global function or constants everything belongs to a class. All values are initialized before use. Arrays and strings with length built-in and bounds checking. Both language support threads part of process such as open many tab in a browser. .NET Programming 5 www.ashagroup.org Structure of C# Program: Before we study basic building blocks of the C# programming language, let us look at a bare minimum C# program structure so that we can take it as a reference in upcoming chapters. A C# program basically consists of the following parts: Namespace declaration A class Class methods Class attributes A Main method Statements & Expressions Comments Let us look at a simple code that would print the words "Hello World": using System; namespace HelloWorldApplication { class HelloWorld { static void Main(string[] args) { /* my first program in C# */ Console.WriteLine("Hello World"); Console.ReadKey(); } } } When the above code is compiled and executed, it produces the following result: Hello World Let us look at various parts of the above program: The first line of the program using System; - the using keyword is used to include the System namespace in the program. A program generally has multiple using statements. The next line has the namespace declaration. A namespace is a collection of classes. The HelloWorldApplication namespace contains the class HelloWorld. The next line has a class declaration, the class HelloWorld contains the data and method definitions that your program uses. Classes generally .NET Programming 6 www.ashagroup.org would contain more than one method. Methods define the behavior of the class. However, the HelloWorld class has only one method Main. The next line defines the Main method, which is the entry point for all C# programs. The Main method states what the class will do when executed. The next line /*...*/ will be ignored by the compiler and it has been put to add additional comments in the program. The Main method specifies its behavior with the statement Console.WriteLine("Hello World"); WriteLine is a method of the Console class defined in the System namespace. This statement causes the message "Hello, World!" to be displayed on the screen. The last line Console.ReadKey(); is for the VS.NET Users. This makes the program wait for a key press and it prevents the screen from running and closing quickly when the program is launched from Visual Studio .NET.9610040036 It's worth to note the following points: C# is case sensitive. All statements and expression must end with a semicolon (;). The program execution starts at the Main method. Unlike Java, file name could be different from the class name. Compile & Execute a C# Program: If you are using Visual Studio.NET for compiling and executing C# programs, take the following steps: Start Visual Studio. On the menu bar, choose File, New, Project. Choose Visual C# from templates, and then choose Windows. Choose Console Application. Specify a name for your project, and then choose the OK button. The new project appears in Solution Explorer. Write code in the Code Editor. Click the Run button or the F5 key to run the project.
Recommended publications
  • Logview Studio Linux Preparation with Mono
    LogView Studio Linux Preparation with Mono 2014 by Dominik Schmidt [email protected] © 2014 Dominik Schmidt / Holger Hemmecke I LogView Studio Table of Contents Part I Linux Prepare 1 1 SSH Co..n..n..e..c..t. ........................................................................................................................ 1 2 Raspbe..r.r.y.. .P..i. ......................................................................................................................... 4 System Prepar..a..t.i.o...n.. ............................................................................................................................................... 5 Mono .......................................................................................................................................................... 6 Install Mono......................................................................................................................................................... 7 Compile Mon..o.. .f.r..o..m.. .T..A...R....................................................................................................................................... 8 Compile Mon..o.. .f.r..o..m.. .G...I.T........................................................................................................................................ 9 Testing ......................................................................................................................................................... 10 3 Cubie.t.r.u..c..k.. .........................................................................................................................
    [Show full text]
  • ENERGY EFFICIENCY in RESIDENTIAL BUILDINGS in MOZAMBIQUE Measurements and Simulations
    Report TABK-1027 BZ info: TABK-1027 GABRIEL AUZIANE Rygg: 13,22 = 187 sidor Setup (bxh): 369,22 x 252 Upplaga: 120 Mellanblad: grå and Simulations ENERGY EFFICIENCY IN RESIDENTIAL BUI DINGS MOZAMBIQUE - Measurements Färgsidor: ingen begränsn. ENERGY EFFICIENCY IN RESIDENTIAL BUILDINGS IN MOZAMBIQUE Measurements and Simulations GABRIEL AUZIANE Building Doctoral Thesis Science DEPARTMENT OF CONSTRUCTION SCIENCES DIVISION OF BUILDING SCIENCE ISRN LUTVDG/TABK--15/1027--SE (1-176) | ISSN 1103-4467 ISBN 978-91-7623-159-3 (print) | ISBN 978-91-7623-160-9 (pdf) DOCTORAL THESIS ENERGY EFFICIENCY IN RESIDENTIAL BUILDINGS IN MOZAMBIQUE Measurements and Simulations GABRIEL AUZIANE Copyright © Gabriel Auziane 2015. Printed by Media-Tryck LU, Lund, Sweden, April 2015 (Pl). For information, address: Division of Building Science, LTH, Lund University, Box 118, SE-221 00 Lund, Sweden. Homepage: http://www.bkl.lth.se Acknowledgements I am deeply thankful to my main supervisors, Professor Bertil Fredlund and Associate Professor Susanne Heyden, my co-supervisors Dr. Kurt Källblad, Dr. Daniel Baloi, and the former Head of the Department of Construction Sciences, Professor Göran Sandberg and Professor Anne Landin for offering me the possibility of working in this project and also for support, encouragement, inspiration and patience over the years, without their help and advice this thesis work would never have been successful. Furthermore, I would like to thank the Head of the Division of Structural Mechanics, Professor Erik Serrano and Professors Jesper Arfvidsson and Petter Wallentén, for their supervision of the work and great help in the overall process of this research. I thank Asdi/SAREC for this research receiving financial support through Lund University and Eduardo Mondlane University under the coordination of Prof.
    [Show full text]
  • KEMPER PROFILER Addendum 8.6 Legal Notice
    KEMPER PROFILER Addendum 8.6 Legal Notice This manual, as well as the software and hardware described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. The content of this manual is furnished for informational use only, is subject to change without notice and should not be construed as a commitment by Kemper GmbH. Kemper GmbH assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Except as permitted by such license, no part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, recording, by smoke signals or otherwise without the prior written permission of Kemper GmbH. KEMPER™, PROFILER™, PROFILE™, PROFILING™, PROFILER PowerHead™, PROFILER PowerRack™, PROFILER Stage™, PROFILER Remote™, KEMPER Kone™, KEMPER Kabinet™, KEMPER Power Kabinet™, KEMPER Rig Exchange™, KEMPER Rig Manager™, PURE CABINET™, and CabDriver™ are trademarks of Kemper GmbH. All features and specifications are subject to change without notice. (Rev. September 2021). © Copyright 2021 Kemper GmbH. All rights reserved. www.kemper-amps.com Table of Contents What is new? 1 What is new in version 8.6? 2 Double Tracker 2 Acoustic Simulator Enhancements 3 Auto Swell Sensitivity 3 PROFILER Stage Wi-Fi Enhancement 4 What is new in version 8.5? 5 Important Hints for Users of KEMPER Power Kabinet 5 KEMPER Rig Manager for iOS®* 6 Wi-Fi with PROFILER Stage 9 What is new in version 8.2? 11 Power Amp
    [Show full text]
  • Practical Migration to Linux on System Z
    Front cover Practical Migration to Linux on System z Overview and migration methodology Migration analysis Hands-on migration case study Lydia Parziale Joseph Apuzzo Saulo Augusto M Martins da Silva Louis Henderson Manoj Srinivasan Pattabhiraman Richard Sewell ibm.com/redbooks International Technical Support Organization Practical Migration to Linux on System z October 2009 SG24-7727-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (October 2009) This edition applies to z/VM Version 5.3 and Version 5.4, Novell SUSE Linux Enterprise Server Version 10 and Version 11, and Red Hat Enterprise Linux Version 5.3. © Copyright International Business Machines Corporation 2009. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xv The team who wrote this book . xv Become a published author . xviii Comments welcome. xviii Part 1. Overview and migration methodology . 1 Chapter 1. Migration considerations . 3 1.1 Reason to migrate systems. 4 1.1.1 How green is your data center . 4 1.1.2 The IBM Big Green server consolidation . 7 1.2 Benefits of migrating to Linux on System z . 7 1.3 Reasons to select Linux on System z . 9 1.3.1 System z strengths . 10 1.3.2 Value of Linux on System z. 12 1.3.3 Choosing workloads to migrate to IBM System z . 13 1.4 z/VM virtualization for Linux on IBM System z .
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • What Every Engineer Should Know About Developing Real-Time
    Contents What Every Engineer Should Know: Series Statement................ xv Preface. ................................................................. xvii Author. ................................................................. xix Acknowledgments . ................................................... xx List of Abbreviations................................................... xxi 1 Development Processes . ......................................... 1 1.1 Introduction ............................................... 1 1.2 Concept and Market ...................................... 5 1.3 People and Disciplines . .................................. 7 1.4 Architecting and Architecture . ......................... 8 1.5 Phases of a Project . ....................................... 16 1.6 Scheduling. ................................................ 19 1.7 Documentation . ........................................... 21 1.8 Requirements and Standards ............................. 24 1.9 Analysis . ................................................ 30 1.10 Design Trade-Offs. ....................................... 31 1.11 Tests . .................................................... 38 1.12 Integration. ................................................ 42 1.13 Manufacturing. ........................................... 44 1.14 Support .................................................... 45 1.15 Disposal . ................................................ 47 1.16 Liability.................................................... 48 1.17 Priorities. ...............................................
    [Show full text]
  • Autofac Documentation Release 6.0.0
    Autofac Documentation Release 6.0.0 Autofac Project Jul 11, 2021 Contents 1 Getting Started 3 1.1 Structuring the Application.......................................3 1.2 Add Autofac References.........................................5 1.3 Application Startup............................................5 1.4 Application Execution..........................................6 1.5 Going Further..............................................8 1.6 Need Help?................................................8 1.7 Building from Source..........................................8 2 What’s New 9 2.1 Release Notes..............................................9 2.2 Upgrading from Autofac 5.x to 6.x................................... 10 2.3 Upgrading from Autofac 3.x to 4.x................................... 12 3 Registering Components 15 3.1 Registration Concepts.......................................... 15 3.1.1 Reflection Components..................................... 16 3.1.2 Instance Components...................................... 17 3.1.3 Lambda Expression Components................................ 17 3.1.4 Open Generic Components................................... 19 3.1.5 Services vs. Components.................................... 19 3.1.6 Default Registrations...................................... 20 3.1.7 Conditional Registration.................................... 20 3.1.8 Configuration of Registrations................................. 22 3.1.9 Dynamically-Provided Registrations.............................. 22 3.2 Passing Parameters to Register.....................................
    [Show full text]
  • C# Multi-Platform Környezetben
    Eötvös Loránd Tudományegyetem Informatikai Kar Média- és Oktatásinformatikai Tanszék C# Multi-Platform Környezetben Dr. Illés Zoltán Szabó Dávid Egyetemi docens Programtervező Informatikus MSc Budapest, 2018. Tartalomjegyzék TARTALOMJEGYZÉK 1 MULTI-PLATFORM APPLIKÁCIÓ FEJLESZTÉS 4 Közös kódbázis 5 Hátrányok 6 Multi-platform Programozási Nyelvek 6 C# ÉS .NET 9 .NET Framework 9 .NET Assembly 10 .NET Multi-Platform 11 .NET Native 11 .NET DISZRIBÚCIÓK 14 Korábbi Microsoft .NET disztribúciók 14 Universal Windows Platform 15 .NET Core 16 Mono-Project 16 Unity3D 17 Xamarin 17 Diplomamunkám fókusza 18 KÖZÖS KÓDBÁZIS 20 Shared Project 20 Portable Class Library 20 .NET Standard 22 Konklúzió 23 UNIVERSAL WINDOWS PLATFORM 24 UWP fejlesztői eszközök telepítése és használata 25 Szabó Dávid C# Multi-Platform Környezetben 1. oldal Projekt létrehozása 25 Fordítás és hibakeresés 26 Publikálás 26 Telepítés és futtatás 27 UWP összegzés 29 .NET CORE 30 .NET Core fejlesztői eszközök telepítése és használata 31 Projekt létrehozása 31 Fordítás 32 Publikálás 33 Futtatás 35 .NET Core Grafikus Felhasználói Felületek 36 Gtk# 37 Avalonia 37 Egyéb könyvtárak 39 .NET Core Összegzés 39 MONO 41 Mono támogatott platformok 42 Windows 42 Linux és MacOS 42 Android és iOS 42 Mono fejlesztői eszközök telepítése és használata 43 Projekt létrehozása 43 Fordítás 43 Publikálás 44 Mono Grafikus Felhasználói Felület 45 Gtk# 45 Mono Összegzés 46 XAMARIN 47 Xamarin támogatott platformok 47 Xamarin.Mac 47 Xamarin.iOS 48 Xamarin.Android 49 Samsung Tizen 50 Xamarin fejlesztői eszközök
    [Show full text]
  • Upgrade Issues
    Upgrade issues Graph of new conflicts libsiloh5-0 libhdf5-lam-1.8.4 (x 3) xul-ext-dispmua (x 2) liboss4-salsa-asound2 (x 2) why sysklogd console-cyrillic (x 9) libxqilla-dev libxerces-c2-dev iceape xul-ext-adblock-plus gnat-4.4 pcscada-dbg Explanations of conflicts pcscada-dbg libpcscada2-dev gnat-4.6 gnat-4.4 Similar to gnat-4.4: libpolyorb1-dev libapq-postgresql1-dev adacontrol libxmlada3.2-dev libapq1-dev libaws-bin libtexttools2-dev libpolyorb-dbg libnarval1-dev libgnat-4.4-dbg libapq-dbg libncursesada1-dev libtemplates-parser11.5-dev asis-programs libgnadeodbc1-dev libalog-base-dbg liblog4ada1-dev libgnomeada2.14.2-dbg libgnomeada2.14.2-dev adabrowse libgnadecommon1-dev libgnatvsn4.4-dbg libgnatvsn4.4-dev libflorist2009-dev libopentoken2-dev libgnadesqlite3-1-dev libnarval-dbg libalog1-full-dev adacgi0 libalog0.3-base libasis2008-dbg libxmlezout1-dev libasis2008-dev libgnatvsn-dev libalog0.3-full libaws2.7-dev libgmpada2-dev libgtkada2.14.2-dbg libgtkada2.14.2-dev libasis2008 ghdl libgnatprj-dev gnat libgnatprj4.4-dbg libgnatprj4.4-dev libaunit1-dev libadasockets3-dev libalog1-base-dev libapq-postgresql-dbg libalog-full-dbg Weight: 5 Problematic packages: pcscada-dbg hostapd initscripts sysklogd Weight: 993 Problematic packages: hostapd | initscripts initscripts sysklogd Similar to initscripts: conglomerate libnet-akamai-perl erlang-base screenlets xlbiff plasma-widget-yawp-dbg fso-config- general gforge-mta-courier libnet-jifty-perl bind9 libplack-middleware-session-perl libmail-listdetector-perl masqmail libcomedi0 taxbird ukopp
    [Show full text]
  • A Fault Model for Upgrades in Distributed Systems
    A Fault Model for Upgrades in Distributed Systems Tudor Dumitraş, Soila Kavulya and Priya Narasimhan CMU-PDL-08-115 December 2008 Parallel Data Laboratory Carnegie Mellon University Pittsburgh, PA 15213-3890 Abstract Recent studies, and a large body of anecdotal evidence, suggest that upgrades are unreliable and often end in failure, causing downtime and data-loss. While this is sometimes due to software defects in the new version, most upgradefailures are the result of faults in the upgrade procedure, such as broken dependencies. In this paper, we present data on upgrade failures from three independent sources — a user study, a survey and a field study — and, through statistical cluster analysis, we construct a novel fault model for upgrades in distributed systems. We identify four distinct types of faults: (1) simple configuration errors (e.g., typos); (2) semantic configuration errors (e.g., misunderstood effects of parameters); (3) broken environmental dependencies (e.g., incorrect libraries, port conflicts); and (4) complex procedural errors. We estimate that, on average, Type 1 faults occur in 15.2 % of upgrades, and Type 4 faults occur in 16.8 % of upgrades. A Fault Model for Upgrades in Distributed Systems Tudor Dumitra¸s, Soila Kavulya and Priya Narasimhan Carnegie Mellon University Pittsburgh, PA 15217 [email protected] [email protected] [email protected] Abstract Recent studies, and a large body of anecdotal evidence, suggest that upgrades are unreliable and often end in failure, causing downtime and data-loss. While this is sometimes due to software defects in the new version, most upgrade- failures are the result of faults in the upgrade procedure, such as broken dependencies.
    [Show full text]
  • Open-Source Legal Process Designer in .NET Blazor Student: Martin Drozdík Supervisor: Ing
    ASSIGNMENT OF BACHELOR’S THESIS Title: Open-Source Legal Process Designer in .NET Blazor Student: Martin Drozdík Supervisor: Ing. Marek Skotnica Study Programme: Informatics Study Branch: Web and Software Engineering Department: Department of Software Engineering Validity: Until the end of summer semester 2020/21 Instructions An open-source smart contract designer is an ongoing research project at the CCMi research group. The main goal of this project is to provide a visual language to design legal contracts between parties which can be used to generate executable blockchain smart contracts. Blazor is a technology that allows running .NET code directly in the browser using a WebAssembly standard. A goal of this thesis is to investigate the possibilities of the Blazor technology to design an open-source smart contract designer and create a proof of concept prototype. Steps to take: - Review the Blazor framework. - Review an existing open-source designer for the Das Contract project. - Design and create a proof-of-concept application in Blazor. - Summarize the benefits and potential of the Blazor compared to other approaches. References Will be provided by the supervisor. Ing. Michal Valenta, Ph.D. doc. RNDr. Ing. Marcel Jiřina, Ph.D. Head of Department Dean Prague December 20, 2019 Bachelor’s thesis Open-Source Legal Process Designer in .NET Blazor Martin Drozd´ık Faculty of Information Technology Supervisor: Ing. Marek Skotnica May 6, 2020 Acknowledgements Thank you to my supervisor, Ing. Marek Skotnica, for providing guidance and feedback throughout this thesis. Declaration I hereby declare that the presented thesis is my own work and that I have cited all sources of information in accordance with the Guideline for adhering to ethical principles when elaborating an academic final thesis.
    [Show full text]
  • Improving the Dependability of Distributed Systems Through AIR Software Upgrades
    Carnegie Mellon University CARNEGIE INSTITUTE OF TECHNOLOGY THESIS SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF Doctor of Philosophy TITLE Improving the Dependability of Distributed Systems through AIR Software Upgrades PRESENTED BY Tudor A. Dumitra! ACCEPTED BY THE DEPARTMENT OF Electrical & Computer Engineering ____________________________________________ ________________________ ADVISOR, MAJOR PROFESSOR DATE ____________________________________________ ________________________ DEPARTMENT HEAD DATE APPROVED BY THE COLLEGE COUNCIL ____________________________________________ ________________________ DEAN DATE Improving the Dependability of Distributed Systems through AIR Software Upgrades Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Electrical & Computer Engineering Tudor A. Dumitra! B.S., Computer Science, “Politehnica” University, Bucharest, Romania Diplôme d’Ingénieur, Ecole Polytechnique, Paris, France M.S., Electrical & Computer Engineering, Carnegie Mellon University Carnegie Mellon University Pittsburgh, PA December, 2010 To my parents and my teachers, who showed me the way. To my friends, who gave me a place to stand on. Pentru Tanti Lola. Abstract Traditional fault-tolerance mechanisms concentrate almost entirely on responding to, avoiding, or tolerating unexpected faults or security violations. However, scheduled events, such as software upgrades, account for most of the system unavailability and often introduce data corruption or latent errors. Through
    [Show full text]