Project Management

Project Management

StumbleUpon

Overview • Customize? Why, what, how? • .NET Framework overview & fundamentals • Class libraries, namespaces, classes • Declaring and using variables • Defining and using functions • VS Projects & Solutions and folder/file organization • Layered Applications • Business Logic Layer & Testing • Presentation Layer (Windows Forms)

Why customize ArcGIS ? Workflow. Software does not do EXACTLY what you want to do “out-of-the-box” but has the programming infrastructure required that allows you to customize it to do exactly what you want

Extending ArcGIS, Add-ins, C#, & ArcObjects • Adding toolbars, buttons, tools, etc. • ArcGIS 10.1 provides tools for making Python Add-insArcGIS 10.0 did not (Free webinar) • ArcObjects SDK for the Microsoft .NET Framework will be covered in GIS Customization II • ArcObjects is more comprehensive than Python

ArcEngine • Build your own GIS-enabled app • Does not require ArcGIS but does require ArcEngine runtime ($) • Not coveredin Customizationcourses

Open Source GIS components

.NET Framework Overview CLS(Common Language Specification) C#, VB.NET, Managed C++, J# CLS specifes rules .NET languages must follow to create .NET code that will reference the.NET Framework Class Libraries (.NET DLL Assemblies) and .NET CTS. Framework Class Libraries UI Web Form WinForm WPF Services WCF WorkFlow Data Access ADO.NET Entity Framwork LINQ to SQL Framework Base Classes & CTS (Common Type System) IO, Collections, Security, Threading, etc. .NET compilers will compile.NET code into CIL stored in.NET assemblies (EXE or DLL) Compilers CIL(Common Intermediate Language) .NET CLR will perform JIT (Just-In-Time compilation) tonative machine code and ensure that the .NET assembly runs properly and securely. CLR(Common Language Runtime) Windows OS Win32, IIS, MSMQ

System.Console.WriteLine() example mscorlib is required by CLR so no reference is required in code

Compiling and running The 4.0 .NETFramework must be installed on the computer that will run a 4.0 Assembly(EXE) Use C# compilerto create hw.exe Running assembly invokes JIT by CLR and runs app

using keyword for Namespaces static keyword means you don’t need an instance of the class Program to call the function Main.

Class libraries, namespaces, classes Class Libraries are stored ina .NET assembly (DLL) Namespaces are a way of naming a group of related classes and other types. Namespaces can be nested. Namespaceicon

Declaring and using variables Variable declaration syntax: [scope] [static] type name;

Variable Scope Variable declaration syntax: [scope] [static] type name;

Scope Review public internal (default) protected Entire solution private More … Assembly only More … Derived classes More … Class only More … 16 of 29

Types Variable declaration syntax: [scope] [static] type name; string array etc. .NET Classes Classes you create. int long double bool etc.

Defining and calling functions Syntax for defining functions: [scope] [static] return_type name ([params]) { // C# statements } 0 or more params are declared like variables and comma separated.

Scope

Command-line args for Console applications

C# Compiler & command-line args

Projects … … because any application worth building usually has more than one .cs file and other files (e.g. images, cursors, etc.)

Solutions … … because Projects must be part of a Solution Visual Studio Solution (.sln) * Projects (.csproj)

Folder structure for application development Download …

Creating an app dev folder - Create a New Project … Blank Solution, in src- Save - Exit Visual Studio - Move files up one level into src - Delete solution folder Solutions can include code from other CLS languages (e.g. VB.NET)

Adding a Project to a Solution

StartUp Project is the first project to run when the application is run Class Library Projects cannot be set as the StartUp Project StartUp Project

Layered Applications Presentation Layer BLL Business objects & logic Business Logic Layer DAL Read/Write data from/to a database Data Access Layer Data

Steps to building a layered application • Get requirements for application feature(s) • Decide on a presentation layer and sketch it out(no code) • Create the … • Data access layer and tests, debug • Business logic layer and tests, debug • Presentation layer and connect to business layer, debug • Test the application • Create installer • Deploy application to users • Repeat until all application features are complete

Creating a Business Layer • Add Class Library Project to Solution • Suffix name with BLL (e.g. IssueTrackerBLL) • Add classes to represent the business objects • Add properties and methods to these classes to represent the business data and processes respectively

Testing a Business Layer • Create a Test Project • Common to have one Test Project per application Project • Suffix Test Project name with “Tests”

Adding a Test

Editing the TestMethod

Running the test – no debugging With cursor in test method … Or right-click and use TestDriven.NET

Running the test – with debugging With cursor in test method … Or right-click and use TestDriven.NET Need Breakpoint(F9 to toggle)

Test results

Building a Presentation Layer (UI) • Add UI Application Project that satisfies the requirements • Windows • Console Application • Windows Forms Application • WPF Application • Web • ASP.NET Web Application • ASP.NET MVC Application • Silverlight Application • Suffix Project name with UI • This is the StartUp Project

Windows Forms Application • A Form is a container for UI controls • Common for starting form to have name MainForm Drag & Drop from Toolbox

Naming child controls • Give child control names prefixes • btn = Button • txt = TextBox • lbl = Label • lst = ListBox • cbo = ComboBox • rdo = RadioButton • etc. • Adding code to controls … Double-click control or code by hand

“Connecting” the UI and BLL Add Reference in UI to BLL Project Add using to UI code(MainForm.cs in this example)

Example: Accessing BLL from UI

Links for VS 2010 and C# • “Quick Tour” of the VS 2010 IDE • Beginner Developer Learning Centre • Csharp-station.com tutorial

Keys to remember F1 – Context sensitive Help (If cursor is on keyword, help on keyword provided) F6 – Build code (compile) without running F5 – Build code (compile) and run F11 – Step through code, into called functions F10 – Step through code, not into called functions Shift-F5 – Stop running code F9 – Toggle Breakpoint at current statement

Project Management