DOCSLIB.ORG

NET Core: from Architecture to Code

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

.NET Core: from architecture to code Raffaele Rialdi @raffaeler [email protected] http://iamraf.net Big, big thanks to the Sponsors!!! About myself ... ▪ I started working professionally with software in 1987 ▪ In 2003 I received my first MVP Award (I got my 14th few days ago!) ▪ In a couple of weeks I will attend the MVP Summit in Redmond ▪ I am a Senior Software Architect ▪ Working as both as consultant and driving a a software division in Vevy Europe ▪ I have a lot of fun with exciting projects: ▪ Financial, Racing, Manufacturing, ... ▪ I have been in Romania several times ▪ «Visual Studio 2010 Launch» Keynote in Bucharest ▪ Regular speaker in ITCamp @ Cluj Napoca since 2012 Rationale for re-architecting the .NET Framework ▪ Rebuild the .NET platform to reach new goals ▪ Cross-platform: we live in an etherogeneous world ▪ Remove global dependencies: making xcopy work everywhere ▪ better versioning, side-by-side deployment ▪ Easier load balancing and designing scalable apps ▪ Getting better performance from modern hardware ▪ No compromises ▪ But looking for the lowest possible breaking changes .NET Framework (versions 1.0 to 4.62) ▪ 15 years, 1.8 billion installations VB C++ C# F# … ▪ Multiple codebase/flavors Common Language Specification .NET Framework ▪ Desktop, Silverlight Ado.net Asp.net Winform WPF ... ▪ x86 - Windows Base Class Library (BCL) ▪ Compact Framework ▪ ARM – Windows CE Common Language Runtime (CLR) ▪ Micro Framework ▪ ARM Duplicated BCL Codebase .NET ▪ Non-Microsoft .NET Mono ▪ Mono / Xamarin & ▪ Linux, iOS, MacOS, … Unity Compact Silverlight Framework ... ▪ x86 and ARM Micro Framework proportions do not reflect real API numbers What is Net Core The details and ▪ Technically a «fork» of the .NET Framework a lot of code ▪ New runtime (Common Language Runtime – CLR) in the next session ▪ New libraries (Base Class Library – BCL) (same room) ▪ Changes to make the Cross Platform story work ▪ Scenarios taking advantace from Net Core (currently) are: ▪ ASP.NET Core: new ASP.NET stack, re-written from scratch ▪ Universal Windows Platform: Windows Store Apps (cross-device) ▪ Containerized applications / docker - ready ▪ Cloud Applications: Applications and Microservices running on Azure ▪ Console Application: the best way to start testing Net Core Cross-Platform = No first-class Operating System ▪ Official daily compilations on GitHub include many OSes ▪ CentOS, Debian, FreeBSD, openSUSE, RedHat, Linux Mint, Ubuntu 14.04 to 16.10 ▪ OSX 10.11 ▪ Windows Occasionally this may happen :) The Big Picture ▪ Libraries using just CoreFX can be shared across all the Application Models ▪ Runtime Adaptation Layers are specific to a given Platform / CPU ▪ x86, x64, ARM, ... .NET Framework .NET CORE Xamarin / Mono (more CPUs are coming in town) "Classic" Win WPF iOS Android Forms ASP.NET UWP CORE … ▪ Modular design for future extensions ASP.NET OS X ▪ New Application Models CoreFX ▪ New Operating Systems / Platforms .NET Standard Library Runtime Adaption Level Runtime Adaption Level … ▪ New CLR variants CoreCLR .NET Native … The unified Command Line called "dotnet" The CLI (Command Line Interface) is back ▪ In the cross-platform world is the common denominator ▪ Nanoservers, IoT devices, etc. are controlled using the command line ▪ Deploy tasks can be automated ▪ Easy to install on a fresh machine ▪ Visual Studio will provide the UI for all the CLI commands ▪ Support "extensions" to add commands ▪ downloaded via dotnet restore http://dot.net/ Hands on the DotNet CLI https://github.com/dotnet/cli 1. Install the CLI C:\app1>dotnet --help .NET Command Line Tools http://dot.net/ Usage: dotnet [common-options] [command] [arguments] Arguments: 2. Create an App [command] The command to execute mkdir myapp [arguments] Arguments to pass to the command cd myapp Common Options (passed before the command): dotnet new -v|--verbose Enable verbose output --version Display .NET CLI Version Number --info Display .NET CLI Info 3. Write some code ... Common Commands: new Initialize a basic .NET project restore Restore dependencies specified in the .NET project 4. Restore packages build Builds a .NET project dotnet restore publish Publishes a .NET project for deployment (including the runtime) run Compiles and immediately executes a .NET project 5. Run the app test Runs unit tests using the test runner specified in the project pack Creates a NuGet package dotnet run An example of the dotnet CLI extensibility The Secret Manager Tool ▪ Warning: This tool is not suitable for production (data is NOT encrypted) ▪ It is an extension to the dotnet CLI "tools": { ▪ reference in the project "Microsoft.Extensions.SecretManager.Tools": { "version": "1.0.0-preview1-final", ▪ dotnet restore to download "imports": "portable-net45+win8+dnxcore50" }} ▪ Usage is very simple dotnet user-secrets -h dotnet user-secrets set key 1234 ▪ Secrets are stored in the user profile dotnet user-secrets list ▪ Windows: %APPDATA%\microsoft\UserSecrets\<userSecretsId>\secrets.json ▪ Linux: ~/.microsoft/usersecrets/<userSecretsId>/secrets.json ▪ Mac: ~/.microsoft/usersecrets/<userSecretsId>/secrets.json NetStandard https://github.com/dotnet/standard/ ▪ A library specification defining a set of APIs with no implementation ▪ Think to netstandard as it was a huge interface ▪ NET Frameworks provide at least a concrete implementation of all those APIs ▪ NET Core / CoreFX provides one of these implementations ▪ CoreFX is an implementation (superset) of NetStandard ▪ https://github.com/dotnet/corefx ▪ How the review board defines the surface of netstandard ▪ No platform specific APIs ▪ Only APIs that makes sense should be everywhere ▪ Is not necessary to put in the standard things that are IL-only (like C#, VB and F#) NetStandard versions vs Platforms more Frameworks more APIs No breaking changes between 1.x and 2.0 as initially announced Version # of APIs netstandard 1.6 13,501 netstandard 2.0 32,638 Unity will be there too (they are going to use the upcoming mono release) How much is different netstandard (and CoreFX) from the current BCL? ▪ AppDomain ▪ Back in nestandard2.0, not available in netstandard1.6 ▪ CreateDomain throws PlatformNotSupportedException on some platforms ▪ AssemblyLoadContext to dynamically load assemblies ▪ AppContext to access few global data (GetData, SetData, ...) ▪ Remoting not available anymore ▪ MarshalByRefObject exists for compatibility reasons ▪ System.Data (only the abstractions and DataSet) but no providers ▪ System.Reflection now lives in a separate assembly ▪ To avoid a complex dependency graph, GetTypeInfo() extension method exists Project.json ▪ Warning: tooling and project structure is going to change in the final bits ▪ Expect an «automagical» migration from project.json back to msbuild csproj ▪ Project.json accomplish multiple tasks. The most important are: ▪ dependencies: replace nuget packages.config nuget configuration file ▪ frameworks: specify the targets where the application or library may run on ▪ net core, .net framework "classic", uap, etc. ▪ runtimes: constrains the application / library to a specific runtime platform ▪ win, ubuntu.14.04-x64, etc. ▪ buildOptions: compilation and friends ▪ assembly-wide metadata (name, author, description, etc.) Project.json frameworks and dependencies ▪ "frameworks" is the section where we declare what CLR we want to use ▪ "netcoreapp1.0" is the moniker for .NET Core ▪ "net461" is the moniker for .NET Framework 4.61 ▪ complete list at https://docs.nuget.org/ndocs/schema/target-frameworks ▪ "dependencies" is where we declare the list of the required bits ▪ Class Libraries / DLL depends at least from "NETStandard.Library" ▪ Version "1.6.0" is the latest, soon the 2.0 ▪ Application Models / Apps depends at least from "Microsoft.NETCore.App" ▪ Currently version "1.0.0" and "1.0.1" are available ▪ Important note: dependencies may be "global" or specific to a specified framework Tooling ▪ Tooling is still in preview and miss a lot of things ▪ On October 19 the team announced the tooling for Visual Studio “15” ▪ Ability for current Net Framework projects to directly reference NetCore libraries ▪ Ability for NetCore project to reference Net Framework compatible libraries ▪ Transparent migration from project.json+xproj to csproj (the new one) ▪ using both "command line" or VS "15" UI ▪ nuget ▪ is expected to provide a better story around deployment (local and remote) ▪ dotnet cli ▪ the communities expect it to be expanded to support more options Packaging with Nuget ▪ NetCore dependencies must always be identified ▪ A package manager is required to identify the unit of deployment ▪ Nuget is now a leading actor in the build process ▪ Restore the dependencies from the known repositories (local or remote) ▪ Create packages for the libraries ▪ Resolve the dependency trees and identifies the versioning conflicts ▪ Cross-runtime and cross-framework packages will be even more popular ▪ Demo! Codecamp Feedback https://goo.gl/FK2LGL Room 1 Questions? Thank you!.
Recommended publications
  • Ironpython in Action

    Ironpython in Action

    IronPytho IN ACTION Michael J. Foord Christian Muirhead FOREWORD BY JIM HUGUNIN MANNING IronPython in Action Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> IronPython in Action MICHAEL J. FOORD CHRISTIAN MUIRHEAD MANNING Greenwich (74° w. long.) Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. Sound View Court 3B fax: (609) 877-8256 Greenwich, CT 06830 email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed without the use of elemental chlorine.
  • Opening Presentation

    Opening Presentation

    Mono Meeting. Miguel de Icaza [email protected] October 24, 2006 Mono, Novell and the Community. Mono would not exist without the community: • Individual contributors. • Companies using Mono. • Organizations using Mono. • Companies using parts of Mono. • Google Summer of Code. Introductions. 2 Goals of the Meeting. A chance to meet. • Most of the Novell/Mono team is here. • Many contributors are here. • Various breaks to talk. Talk to others! • Introduce yourself, ask questions. Talk to us! • Frank Rego, Mono's Product Manager is here. • Tell us what you need in Mono. • Tell us about how you use Mono. 3 Project Status Goals Originally: • Improve our development platform on Linux. As the community grew: • Expand to support Microsoft APIs. As Mono got more complete: • Provide a complete cross platform runtime. • Allow Windows developers to port to Linux. 5 Mono Stacks and Goals. MySMQySQLL//PPosstgtrgesrsess EvEovolluutitioonn# # ASP.NET Novell APIs: MMoozzillala Novell iFolder iFolder, LDAP, Identity ADO.NET ApAapchachee MMonoono DesktoGpTK#: GTK# OpNoevenlOl LfDfAiPce GCneomceil# Windows.Forms JavaJa vCa oCommpaatitbilbitiylity Google APIs Microsoft Compatibility Libraries Mono Libraries Mono Runtime (Implementation of ECMA #335) 6 Platforms, CIL, Code Generation. 7 API space Mono 1.0: July 2004 “T-Bone” Mono 1.2: November 2006 “Rump steak” Mono 1.2 bits. Reliability and C# 2.0, .NET 2.0 scalability: • Complete. • With VM support. • ZenWorks and iFolder • Some 2.0 API support. pushed Mono on the server. • IronPython works. • xsp 1.0: 8 request/second. • xsp 1.2: 250 Debugger: request/second. • x86 and x86-64 debugger. GUI • CLI-only, limited in scenarios (no xsp).
  • Design and Implementation of Generics for the .NET Common Language Runtime

    Design and Implementation of Generics for the .NET Common Language Runtime

    Design and Implementation of Generics for the .NET Common Language Runtime Andrew Kennedy Don Syme Microsoft Research, Cambridge, U.K. fakeÒÒ¸d×ÝÑeg@ÑicÖÓ×ÓfغcÓÑ Abstract cally through an interface definition language, or IDL) that is nec- essary for language interoperation. The Microsoft .NET Common Language Runtime provides a This paper describes the design and implementation of support shared type system, intermediate language and dynamic execution for parametric polymorphism in the CLR. In its initial release, the environment for the implementation and inter-operation of multiple CLR has no support for polymorphism, an omission shared by the source languages. In this paper we extend it with direct support for JVM. Of course, it is always possible to “compile away” polymor- parametric polymorphism (also known as generics), describing the phism by translation, as has been demonstrated in a number of ex- design through examples written in an extended version of the C# tensions to Java [14, 4, 6, 13, 2, 16] that require no change to the programming language, and explaining aspects of implementation JVM, and in compilers for polymorphic languages that target the by reference to a prototype extension to the runtime. JVM or CLR (MLj [3], Haskell, Eiffel, Mercury). However, such Our design is very expressive, supporting parameterized types, systems inevitably suffer drawbacks of some kind, whether through polymorphic static, instance and virtual methods, “F-bounded” source language restrictions (disallowing primitive type instanti- type parameters, instantiation at pointer and value types, polymor- ations to enable a simple erasure-based translation, as in GJ and phic recursion, and exact run-time types.
  • CNT6008 Network Programming Module - 11 Objectives

    CNT6008 Network Programming Module - 11 Objectives

    CNT6008 Network Programming Module - 11 Objectives Skills/Concepts/Assignments Objectives ASP.NET Overview • Learn the Framework • Understand the different platforms • Compare to Java Platform Final Project Define your final project requirements Section 21 – Web App Read Sections 21 and 27, pages 649 to 694 and 854 Development and ASP.NET to 878. Section 27 – Web App Development with ASP.NET Overview of ASP.NET Section Goals Goal Course Presentation Understanding Windows Understanding .NET Framework Foundation Project Concepts Creating a ASP.NET Client and Server Application Understanding the Visual Creating a ASP Project Studio Development Environment .NET – What Is It? • Software platform • Language neutral • In other words: • .NET is not a language (Runtime and a library for writing and executing written programs in any compliant language) What Is .NET • .Net is a new framework for developing web-based and windows-based applications within the Microsoft environment. • The framework offers a fundamental shift in Microsoft strategy: it moves application development from client-centric to server- centric. .NET – What Is It? .NET Application .NET Framework Operating System + Hardware Framework, Languages, And Tools VB VC++ VC# JScript … Common Language Specification Visual Studio.NET Visual ASP.NET: Web Services Windows and Web Forms Forms ADO.NET: Data and XML Base Class Library Common Language Runtime The .NET Framework .NET Framework Services • Common Language Runtime • Windows Communication Framework (WCF) • Windows® Forms • ASP.NET (Active Server Pages) • Web Forms • Web Services • ADO.NET, evolution of ADO • Visual Studio.NET Common Language Runtime (CLR) • CLR works like a virtual machine in executing all languages. • All .NET languages must obey the rules and standards imposed by CLR.
  • INTRODUCTION to .NET FRAMEWORK NET Framework .NET Framework Is a Complete Environment That Allows Developers to Develop, Run, An

    INTRODUCTION to .NET FRAMEWORK NET Framework .NET Framework Is a Complete Environment That Allows Developers to Develop, Run, An

    INTRODUCTION TO .NET FRAMEWORK NET Framework .NET Framework is a complete environment that allows developers to develop, run, and deploy the following applications: Console applications Windows Forms applications Windows Presentation Foundation (WPF) applications Web applications (ASP.NET applications) Web services Windows services Service-oriented applications using Windows Communication Foundation (WCF) Workflow-enabled applications using Windows Workflow Foundation (WF) .NET Framework also enables a developer to create sharable components to be used in distributed computing architecture. NET Framework supports the object-oriented programming model for multiple languages, such as Visual Basic, Visual C#, and Visual C++. NET Framework supports multiple programming languages in a manner that allows language interoperability. This implies that each language can use the code written in some other language. The main components of .NET Framework? The following are the key components of .NET Framework: .NET Framework Class Library Common Language Runtime Dynamic Language Runtimes (DLR) Application Domains Runtime Host Common Type System Metadata and Self-Describing Components Cross-Language Interoperability .NET Framework Security Profiling Side-by-Side Execution Microsoft Intermediate Language (MSIL) The .NET Framework is shipped with compilers of all .NET programming languages to develop programs. Each .NET compiler produces an intermediate code after compiling the source code. 1 The intermediate code is common for all languages and is understandable only to .NET environment. This intermediate code is known as MSIL. IL Intermediate Language is also known as MSIL (Microsoft Intermediate Language) or CIL (Common Intermediate Language). All .NET source code is compiled to IL. IL is then converted to machine code at the point where the software is installed, or at run-time by a Just-In-Time (JIT) compiler.
  • Why and How to Migrate from .NET to .NET Core. - Oliver Ray, Managing Director @ Number8

    Why and How to Migrate from .NET to .NET Core. - Oliver Ray, Managing Director @ Number8

    Why and How to Migrate from .NET to .NET Core. - Oliver Ray, Managing Director @ number8 There’s no time like the present when it comes to paying down technical debt, investing in high-value features, and keeping up with development house-keeping. These practices allow development velocity to skyrocket. And For most companies still utilizing .NET, migrating to .NET Core is the most impactful technical investment they can make right now. This transition will simplify your teams’ development cycles and have a measurable impact on your bottom-line. However, it can also include unforeseen complexities and dependencies, so it’s crucial that the planning and prep work is done throughly. Our team at number8 took the time to detail a few high-level benefits that every team should consider during this transition. So, let’s get started. Why migrate from .NET to .NET Core? .NET Core 1.0 was announced in 2014 and aimed to bring the .NET framework into the open source world. The ultimate goal of this initiative was to make .NET projects more portable to other platforms. With the explosion of commodity platforms like Linux and ARM64 processors, .NET had to become more open to survive. From it’s initial release .NET Core has continued to evolve to leverage a wide range of technologies that allow teams to develop systems in whatever way they see fit. A significant example of this forward thinking was early support for Docker containers and Kubernetes. Teams Start Planning everywhere are trying to rethink core enterprise Now applications to fully see the benefit of cloud tooling.
  • 18Mca42c .Net Programming (C#)

    18Mca42c .Net Programming (C#)

    18MCA42C .NET PROGRAMMING (C#) Introduction to .NET Framework .NET is a software framework which is designed and developed by Microsoft. The first version of .Net framework was 1.0 which came in the year 2002. It is a virtual machine for compiling and executing programs written in different languages like C#, VB.Net etc. It is used to develop Form-based applications, Web-based applications, and Web services. There is a variety of programming languages available on the .Net platform like VB.Net and C# etc.,. It is used to build applications for Windows, phone, web etc. It provides a lot of functionalities and also supports industry standards. .NET Framework supports more than 60 programming languages in which 11 programming languages are designed and developed by Microsoft. 11 Programming Languages which are designed and developed by Microsoft are: C#.NET VB.NET C++.NET J#.NET F#.NET JSCRIPT.NET WINDOWS POWERSHELL IRON RUBY IRON PYTHON C OMEGA ASML(Abstract State Machine Language) Main Components of .NET Framework 1.Common Language Runtime(CLR): CLR is the basic and Virtual Machine component of the .NET Framework. It is the run-time environment in the .NET Framework that runs the codes and helps in making the development process easier by providing the various services such as remoting, thread management, type-safety, memory management, robustness etc.. Basically, it is responsible for managing the execution of .NET programs regardless of any .NET programming language. It also helps in the management of code, as code that targets the runtime is known as the Managed Code and code doesn’t target to runtime is known as Unmanaged code.
  • Crossplatform ASP.NET with Mono

    Crossplatform ASP.NET with Mono

    CrossPlatform ASP.NET with Mono Daniel López Ridruejo [email protected] About me Open source: Original author of mod_mono, Comanche, several Linux Howtos and the Teach Yourself Apache 2 book Company: founder of BitRock, multiplatform installers and management software About this presentation The .NET framework An overview of Mono, a multiplatform implementation of the .NET framework mod_mono : run ASP.NET on Linux using Apache and Mono The Microsoft .Net initiative Many things to many people, we are interested in a subset: the .NET framework Common Language Runtime execution environment Comprehensive set of class libraries As other technologies, greatly hyped. But is a solid technical foundation that stands on its own merits The .NET Framework .NET Highlights (1) Common Language Runtime : Provides garbage collection, resource management, threads, JIT support and so on. Somewhat similar to JVM Common Intermediate Language, multiple language support: C#, Java, Visual Basic, C++, JavaScript, Perl, Python, Eiffel, Fortran, Scheme, Pascal Cobol… They can interoperate and have access to full .NET capabilities. Similar to Java bytecode .NET Highlights (2) Comprehensive Class Library: XML, ASP.NET, Windows Forms, Web Services, ADO.NET Microsoft wants .NET to succeed in other platforms: standardization effort at ECMA, Rotor sample implementation. P/Invoke: Easy to incorporate and interoperate with existing code Attributes, delegates, XML everywhere Mono Project Open Source .NET framework implementation. Covers ECMA standard plus
  • Programming with Windows Forms

    Programming with Windows Forms

    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
  • NET Framework Objectives

    NET Framework Objectives

    Introduction to .NET • Content : – Introduction to .NET Technology – Introduction to Web Based Applications – Introduction to ASP.NET 1 Introduction to .NET Technology What is .NET ? Microsoft.NET is a Framework – Microsoft .NET is a Framework which provides a common platform to Execute or, Run the applications developed in various programming languages. – Microsoft announced the .NET initiative in July 2000. – The main intention was to bridge the gap in interoperability between services of various programming languages. 3 .NET Framework Objectives • The .NET Framework is designed to fulfill the following objectives: – Provide object-oriented programming environment – Provide environment for developing various types of applications, such as Windows-based applications and Web- based applications – To ensure that code based on the .NET Framework can integrate with any other code 4 .NET Framework VB C++ C# JScript … Common Language Specification Visual Windows 2008 Studio ASP.NET ADO.NET Forms Base Class Library (CLR) Common Language Runtime Operating System • The .NET Framework consists of: – The Common Language Specification (CLS) It contains guidelines, that language should follow so that they can communicate with other .NET languages. It is also responsible for Type matching. – The Framework Base Class Libraries (BCL) A consistent, object-oriented library of prepackaged functionality and Applications. – The Common Language Runtime (CLR) A language-neutral development & execution environment that provides common runtime for application
  • Ink, Touch, and Windows Presentation Foundation

    Ink, Touch, and Windows Presentation Foundation

    9/2/2015 Ink, Touch, and Windows Presentation Foundation Lecture #4: Ink and WPF Joseph J. LaViola Jr. Fall 2015 Fall 2015 CAP 6105 – Pen-Based User Interfaces ©Joseph J. LaViola Jr. From Last Time Windows Presentation Foundation (WPF) integration of Ink multi-touch 2D Graphics 3D Graphics video and audio uses visual tree model component based XAML and C# code Important control – InkCanvas Fall 2015 CAP 6105 – Pen-Based User Interfaces ©Joseph J. LaViola Jr. 1 9/2/2015 Ink Environment Choices Microsoft traditional dev stream: Visual Studio, C#, WPF or (Mono+Xamarin) Pros: Mature platform with many online resources Cons: Can be deployed only on Windows ecosystem Using Mono+Xamarin can be deployed cross-platform Microsoft new dev stream: Visual Studio, JavaScript(or Typescript),HTML Pros: Can be deployed cross-platform(windows, android or IOS) Cons: Relatively new computing environment with new API Other alternatives, such as Python/Kivy, IOS, Android. Pros: Open-source with many online collaboration. Cons: Have little support on inking Fall 2015 CAP 6105 – Pen-Based User Interfaces ©Joseph J. LaViola Jr. Traditional Ink and Touch Ink SDK Before Windows 8.1: The inking API is System.Windows.Ink Online Sample code: Adventures into Ink API using WPF After Windows 8.1: The inking API is Windows.UI.Input.Inking Online Sample code: Input:Simplied ink sample You can find more articles or sample code resources from Microsoft Windows Dev Center or Code project Fall 2015 CAP 6105 – Pen-Based User Interfaces ©Joseph J. LaViola Jr. 2 9/2/2015 Important Ink Components InkCanvas – System.Windows.Controls receives and displays ink strokes starting point for ink applications stores ink in Strokes System.Windows.Ink Namespace contains classes to interact with and manipulate ink examples Stroke GestureRecognizer InkAnalyzer now separate (only on 32 bit) needs IACore.dll, IAWinFX.dll and IALoader.dll Fall 2015 CAP 6105 – Pen-Based User Interfaces ©Joseph J.
  • Detecting Wastedlocker Ransomware Using Security Analytics

    Detecting Wastedlocker Ransomware Using Security Analytics

    Securonix Threat Research: Detecting WastedLocker Ransomware Using Security Analytics Oleg Kolesnikov Securonix Threat Research Team Created on: July 28, 2020 Last Updated: August 18, 2020 Figure 1: Victim’s Systems Targeted by WastedLocker Unavailable (July 2020) The Securonix Threat Research Team (STR) is actively investigating the details of the critical targeted Wastedlocker ransomware attacks that reportedly already exploited more than 31 companies, with 8 of the victims being Fortune 500 companies [1], to help our customers detect, mitigate, and respond to such attacks. Here are some of the key technical details and our recommendations on possible Securonix predictive indicators/security analytics that can be used to detect the current and potentially future attack variants (these indicators may be updated as we receive more information.) 2 www.securonix.com Figure 2: WastedLocker/EvilCorp Attack in Progress - Targeting a Victim Company in a Recent High-Profile Attack Impact Here are the key details regarding the impact of the high-profile WastedLocker ransomware attacks/ EvilCorp malicious cyber threat actor(s)(MTA) involved: • The WastedLocker ransomware is a relatively new malicious payload used by the high-profile EvilCorp MTA, which previously used the Dridex trojan to deploy BitPaymer ransomware in attacks targeting government organizations and enterprises in the United States and Europe. (See Figure 1) • This MTA currently focuses on targeted “big game hunting” (BGH) ransomware attacks with multiple industry victims in recent months, with Garmin as one of the latest high-profile victims attacked (officially confirmed by Garmin on July 27). (See Figure 2) • The most recent ransom amount demanded was US$10M and appears to be based on the victim’s financial data.