HOT Hover Over Technologies

70-519 Passed!!!

2010-06-30T07:00:00.001-07:00

Después de esperar y esperar, los examenes beta de .Net 4 están pasando a producción. Por lo que me empiezan a llegar las noticias esperadas. Y la primera es 70-519 aprobado. Vamos por los otros! (esto me salió medio mundialista)

Sigo en el camino de la certificación.

Stress & load web tests

2010-06-04T07:51:00.001-07:00

Posteé un primer artículo en el el blog de Southworks. Siguiendo la costumbre de este blog, la idea es postear aquí en castellano por lo que voy a intentar traducirme. Puede considerarse cross-posting.

Primeras semanas

Van pasando mis primeras semanas en Southworks, tuve diferentes desafios. Uno de ellos fue estresar un WorkerRole service localmente y en WindowsAzure.
Un WorkerRole es un rol para desarrollos generales y puede realizar procesamiento background para un web role. Una vez deployado localmente obtenemos una URL a nuestro servicio WCF.
Trabajando con esta arquitectura necesitamos estresar los request a este servicio para verificar distintos comportamientos de Windows Azure. El principal objetivo de el stress test es descubrir la recuperabilidad de el servicio o el server testeado.

Stress test usando Pylot

Existe una multiplicidad de herramientas caras para estresar web services. Decidimos utilizar una muy buena solución open source realizada en Python llamada Pylot.

Instalando Pylot

Pylot es un script Pyhton y utiliza librerias wxPython para la interfaz gráfica, NumPy and MatPlotLib para reportes y gráficos.

Usando Pylot

Usar la GUI de Pylot es elemental. Debemos crear un xml con los casos de prueba.

<case>    

     <url>http://www.goldb.org/foo</url>

    <verify>Copyright.*Corey Goldberg</verify>

    <verify_negative>Error</verify_negative>

<case>

Visual Studio 2010 Stress tests

Más allá de la solución de Pylot, en algunos casos necesitamos una pequeña aplicación para solucionar temas particulares. StressService es un servicio realizado en c#. Podemos estresar nuestro server con este simple contrato.

Utilizaremos el Load Test de Visual Studio 2010 para crear el stress test. Para hacer esto crearemos un unit test que realice la acción que queremos estresar.

[ServiceContract]

public interface IStresserService

{

        [OperationContract]

        int SimpleRequest(string url);

  

        [OperationContract]

        List<int> Stress(int workers, string url);

}

Implementación del contrato.

public class StresserService : IStresserService

{

    public int SimpleRequest(string url)

    {

        if (string.IsNullOrEmpty(url))

            throw new ArgumentOutOfRangeException("url");

        HttpWebRequest request = (HttpWebRequest)WebRequest.Create(url);

        HttpWebResponse response;

        try

        {

            response = (HttpWebResponse)request.GetResponse();

        }

        catch (WebException e)

        {

            return (int)((HttpWebResponse)e.Response).StatusCode;

        }

        return (int)response.StatusCode;

    }

  

    public List<int> Stress(int workers, string url)

    {

        var results = new List<int>();

        Parallel.For(0, workers, t =>

        {

            results.Add(SimpleRequest(url));

  

        });

        Thread.Sleep(10000);

        return results;

    }

}

[TestMethod]

public void ItShouldCreateNStressers()

{

    IStresserService service = new StresserService();

    var results = service.Stress(100, @"http://localhost/");

  

    Assert.AreEqual(100, results.Count());

}

Creamos el Load Test para estresar utilizando muchos usuarios durante un tiempo T.

Próximos pasos: escalar la solución.

Podemos escalar la solución comenzando nuevos servicios en otras máquinas y sincronizando los diferentes workers creando un manager.

Requerimientos desde diferentes dominios

La solución está estresando desde el mismo dominio. Podemos tener diferentes problemas (por ej. D.O.S.) que se pueden sobrellevar utilizando otros servicios como Gomez

Y como el movimiento se demuestra andando…

2010-05-14T08:26:00.001-07:00

Empiezo esta semana a blogear (valga el anglicismo) no sólo aquí, sino que también en el blog que me brinda Southworks, mi nuevo empleador. Se pueden dar una vuelta (por ahora está vacío) y también conocer todas los otros muy interesantes posts de los distintos compañeros.

Mariano Koldobsky en Southworks

Blogs de Southworks

getJson desde Asp.Net MVC

2010-05-05T11:07:00.001-07:00

Muchas veces utlizando Asp.Net MVC nos encontramos con la necesidad de acceder a resultados de nuestros metodos del controller, pero no queremos realizar un POST al server. Una buena opción es el llamado de JQuery utilizando la función getJson.

Vamos a llamar a un servicio que nos devuelve una definición de diccionario de una palabra en inglés.
La vista es super elemental tiene un ingreso de palabra (no estamos validando nada en este ejemplo, tampoco estamos testeando, lo cual seria un interesante posteo. Cómo testeo una llamada de AJAX?) y un botón para buscar la definición.

View

    <button id="btnDefine" name="btnDefine">
        Define</button>
    <br />
    <%= Html.TextBox("tbxWord") %>
    <%= Html.TextArea("txtDefinition") %>
    <div id="loading">
        Loading</div>

    <script type="text/javascript">

        $(document).ready(function() {
            $(function() {
                $("#loading").hide();
                $('#btnDefine').click(function() {
                    $("#loading").ajaxStart(function() {
                        $("#loading").show();
                    });
                    wordIn = $("#tbxWord").val();
                    $.getJSON("/Home/GetDefinition", { word: wordIn }, function(data) {
                        $("#txtDefinition").text(data);
                    });
                });
                $("#loading").hide();
            });
        });
    

    </script>

La línea getJson tiene como parametros el ruteo del método del controller, el parámetro del método (en este caso la palabra a buscar) y una función de callback que se llamará cuando vuelve del llamado AJAX, en este caso sólo setea el testo de la definición.

Controller

        public JsonResult GetDefinition(string word)
        { 
            DictService dictionary = new DictService();
            if (word == null) return null;
            var result = dictionary.Define(word);
            return Json(result.Definitions[0].WordDefinition, JsonRequestBehavior.AllowGet);
        }

En el caso del método del controller llamado, sólo tenemos que tener en cuenta devolver un JsonReesul 
y utilizar la clase Json para serializar lo que devolvemos.

Es un buen comienzo.

70-516 Exam – parte única

2010-04-29T08:14:00.001-07:00

Sólo posteo la guía no voy a llegar a poner links. Pero bueno la red proveera.

Modeling Data (20%)

Map entities and relationships by using the Entity Data Model.

This objective may include but is not limited to: using the Visual Designer, building an entity data model from an existing database, managing complex entity mappings in EDMX, editing EDM XML, mapping to stored procedures, creating user-defined associations between entities, generating classes with inheritance and mapping them to tables

This objective does not include: using MetadataWorkspace
Map entities and relationships by using LINQ to SQL.

This objective may include but is not limited to: using the Visual Designer, building a LINQ to SQL model from an existing database, mapping to stored procedures
Create and customize entity objects.

This objective may include but is not limited to: configuring changes to an Entity Framework entity, using the ADO.NET EntityObject Generator (T4), extending, self-tracking entities, snapshot change tracking, ObjectStateManager, partial classes, partial methods in the Entity Framework
Connect a POCO model to the Entity Framework.

This objective may include but is not limited to: implementing the Entity Framework with persistence ignorance, user-created POCO entities

This objective does not include: using the POCO templates
Create the database from the Entity Framework model.

This objective may include but is not limited to: customizing the Data Definition Language (DDL) (templates) generation process, generating scripts for a database, Entity Data Model tools
Create model-defined functions.

This objective may include but is not limited to: editing the Conceptual Schema Definition Language CSDL, enabling model-defined functions by using the EdmFunction attribute, complex types

Managing Connections and Context (18%)

Configure connection strings and providers.

This objective may include but is not limited to: managing connection strings including Entity Framework connection strings, using the ConfigurationManager, correctly addressing the Microsoft SQL Server instance, implementing connection pooling, managing User Instanceand AttachDBfilename, switching providers, implementing multiple active result sets (MARS)

This objective does not include: using the ConnectionStringBuilder; Oracle data provider; creating and using a custom provider; using third-party providers
Create and manage a data connection.

This objective may include but is not limited to: connecting to a data source, closing connections, maintaining the life cycle of a connection
Secure a connection.

This objective may include but is not limited to: encrypting and decrypting connection strings, using Security Support Provider Interface (SSPI) or SQL Server authentication, read only vs. read/write connections

This objective does not include: Secure Sockets Layer (SSL)
Manage the DataContext and ObjectContext.

This objective may include but is not limited to: managing the life cycle of DataContext and ObjectContext, extending the DataContext and ObjectContext, supporting POCO
Implement eager loading.

This objective may include but is not limited to: configuring loading strategy by using LazyLoadingEnabled, supporting lazy loading with POCO, explicitly loading entities
Cache data.

This objective may include but is not limited to: DataContext and ObjectContext cache including identity map, local data cache

This objective does not include: Velocity, SqlCacheDependency
Configure ADO.NET Data Services.

This objective may include but is not limited to: creating access rules for entities, configuring authorization and authentication, configuring HTTP verbs

Querying Data (22%)

Execute a SQL query.

This objective may include but is not limited to: DBCommand, DataReader, DataAdapters, DataSets, managing data retrieval by using stored procedures, using parameters, System.Data.Common namespace classes
Create a LINQ query.

This objective may include but is not limited to: syntax-based and method-based queries, joining, filtering, sorting, grouping, aggregation, lambda expressions, paging, projection

This objective does not include: compiling queries
Create an Entity SQL (ESQL) query.

This objective may include but is not limited to: joining, filtering, sorting, grouping, aggregation, paging, using functions, query plan caching, returning a reference to an entity instance, using parameters with ESQL, functionality related to EntityClient classes
Handle special data types.

This objective may include but is not limited to: querying BLOBs, filestream, spatial and table-valued parameters

This objective does not include: implementing data types for unstructured data, user-defined types, Common Language Runtime (CLR) types
Query XML.

This objective may include but is not limited to: LINQ to XML, XmlReader, XmlDocuments, XPath

This objective does not include: XSLT, XmlWriter
Query data by using ADO.NET Data Services.

This objective may include but is not limited to: implementing filtering and entitlement in ADO.NET Data Services, addressing resources, creating a query expression, accessing payload formats, Data Services interceptors

Manipulating Data (22%)

Create, update, or delete data by using SQL statements.

This objective may include but is not limited to: Create/Update/Delete (CUD), using DataSets, calling stored procedures, using parameters
Create, update, or delete data by using DataContext.

This objective may include but is not limited to: CUD, calling stored procedures, using parameters

This objective does not include: ObjectTrackingEnabled
Create, update, or delete data by using ObjectContext.

This objective may include but is not limited to: CUD, calling stored procedures, using parameters, setting SaveOptions
Manage transactions.

This objective may include
but is not limited to: System.Transactions, DBTransaction, rolling back a transaction, Lightweight Transaction Manager (LTM)

This objective does not include: distributed transactions, multiple updates within a transaction, multiple synchronization of data within an acidic transaction
Create disconnected objects.

This objective may include but is not limited to: creating self-tracking entities in the Entity Framework, attaching objects, DataSets, table adapters

Developing and Deploying Reliable Applications (18%)

Monitor and collect performance data.

This objective may include but is not limited to: logging generated SQL (ToTraceString), collecting response times, implementing performance counters, implementing logging, implementing instrumentation
Handle exceptions.

This objective may include but is not limited to: resolving data concurrency issues (handling OptimisticConcurrency exception, Refresh method), handling errors, transaction exceptions, connection exceptions, timeout exceptions, handling an exception from the Entity Framework disconnected object, security exceptions
Protect data.

This objective may include but is not limited to: encryption, digital signature, hashing, salting, least privilege
Synchronize data.

This objective may include but is not limited to: online/offline Entity Framework, synchronization services, saving locally
Deploy ADO.NET components.

This objective may include but is not limited to: packaging and publishing from Visual Studio, deploying an ADO.NET Services application; packaging and deploying Entity Framework metadata

This objective does not include: configuring IIS, MSDeploy, MSBuild

70-519 Exam – parte 5

2010-04-25T18:12:00.001-07:00

Managing the Service Instance Life Cycle (13%)

Manage service instances.

This objective may include but is not limited to: per call: per session; single; code and configuration; activation and deactivation; durable services; throttling

http://msdn.microsoft.com/en-us/magazine/cc163590.aspx

Manage sessions.

This objective may include but is not limited to: code and configuration; session management attributes; throttling; reliable sessions; transport-level and application-level sessions; invoking a callback contract.

http://msdn.microsoft.com/en-us/library/ms733040.aspx

http://www.c-sharpcorner.com/UploadFile/dhananjaycoder/Instancemanagemnetpart206222009055018AM/Instancemanagemnetpart2.aspx

Implement transactions.

This objective may include but is not limited to: distributed transactions; transactional queues; transaction flow; configuring transaction binding attributes; WS-AtomicTransaction (WS-AT); transactional behavior attributes at the service and operation level; using transactions in code.

http://msdn.microsoft.com/en-us/library/ms730266.aspx

Manage concurrency.

This objective may include but is not limited to: single, multiple, and reentrant concurrency modes; SynchronizationContext and CallbackBehavior

This objective does not include: deadlocks and other mutithreading issues

Single
http://msdn.microsoft.com/en-us/library/system.servicemodel.concurrencymode.single.aspx

Multiple
http://msdn.microsoft.com/en-us/library/system.servicemodel.concurrencymode.multiple.aspx

Reentrant

http://msdn.microsoft.com/en-us/library/ms731193.aspx

Manage consistency between instances, sessions, transactions, and concurrency

This objective may include but is not limited to: possible combinations between instances, sessions, transactions, and concurrency (for example, instance mode single with concurrency mode multiple)

70-513 exam – parte 4

2010-04-25T09:22:00.001-07:00

Securing Services (17%)

Configure secure Bindings

This objective may include but is not limited to: transport, message, mixed mode

http://msdn.microsoft.com/en-us/library/ms731172(v=VS.100).aspx

Configure message security

This objective may include but is not limited to: specifying protection levels on different message parts

http://msdn.microsoft.com/en-us/library/ms789036.aspx

Implement Authentication

Implement Authentication.

This objective may include but is not limited to: Microsoft ASP.NET Membership Provider, Custom Provider, Windows Integrated Security, certificates (X.509), Federated Authentication endpoint identity; configuring client credentials; Custom Validator

This objective does not include: Geneva Framework
Implement Authorization.

This objective may include but is not limited to: role based, claim based; configuring role providers for endpoints; principal permission attribute

This objective does not include: rights-management authorization such as Active Directory Rights Management Services (AD RMS)
Implement Impersonation.

This objective may include but is not limited to: configuration and code; configuring WCF-specific Internet Information Services (IIS) impersonation properties; configuring impersonation options; operation-based and service-based
Implement security auditing.

This objective may include but is not limited to: using serviceSecurityAudit behavior, service auditing, audit log

70-513 Exam – parte 3

2010-04-25T08:18:00.001-07:00

Consuming Services (19%)

Create a service proxy

This objective may include but is not limited to: using a proxy class or channel factory to create a proxy; creating a proxy for an asynchronous communication; creating a proxy for a duplex communication

This objective does not include: SvcUtil command line switches

Proxy class
http://msdn.microsoft.com/en-us/library/ms733133.aspx

Channel factory
http://msdn.microsoft.com/en-us/library/ms734681(v=VS.100).aspx

Asynchronous communication
http://msdn.microsoft.com/en-us/library/ms730059(v=VS.100).aspx

Duplex communication
http://msdn.microsoft.com/en-us/library/ms731935(v=VS.100).aspx

Configure client endpoints.

This objective may include but is not limited to: standard bindings, custom bindings created from standard binding elements; configuring behaviors; code-based and configuration-based bindings; configuring addresses

This objective does not include: security; creating custom behaviors

Standard binding
http://msdn.microsoft.com/en-us/library/ms731092(v=VS.100).aspx
http://msdn.microsoft.com/en-us/library/ms730879(v=VS.100).aspx

Custom binding created from standard binding elements

Configuring behaviors
http://msdn.microsoft.com/en-us/library/aa702788(v=VS.100).aspx

Code-based and configuration-based bindings
http://msdn.microsoft.com/en-us/library/ms731144(v=VS.100).aspx
http://msdn.microsoft.com/en-us/library/ms731862(v=VS.100).aspx

Configuring addresses
http://msdn.microsoft.com/en-us/library/aa751841(v=VS.100).aspx

Invoke a service

This objective may include but is not limited to: invoking a service operation synchronously and asynchronously; handling service faults; using the Message class; managing the life cycle of the proxy (open channels, close channels, abort channels, handle faulted channels); implemented duplex communication

Invoking synchronously and asynchronously
http://msdn.microsoft.com/en-us/library/ms730059(v=VS.100).aspx

Handling service faults
http://msdn.microsoft.com/en-us/library/ms733721.aspx

Message class
http://msdn.microsoft.com/en-us/library/ms734675.aspx

Life cycle of the proxy

Duplex communication
http://msdn.microsoft.com/en-us/library/ms731064.aspx

Consume RESTful services.

This objective may include but is not limited to: access HTTP context; JSON/POX

Access HTTP context

JSON/POX

Implement service discovery

This objective may include but is not limited to: configuring target scope; monitoring service announcements.

Configuring target scope

Monitoring service announcements

70-513 Exam – parte 2

2010-04-24T15:29:00.001-07:00

Hosting and Configuring Services (18%)

Create and configure endpoints.

This objective may include but is not limited to: default and standard bindings; custom bindings created from standard binding elements; standard endpoints; transports including HTTP, TCP, named pipes; UDP, MSMQ code-based service configuration; message encoding

This objective does not include: creating a custom binding element; creating new standard endpoints, loading configuration from a location other than the default application configuration file, security transaction, reliable sessions

Default and standard bindings
Custom bindings created from standard binding
http://msdn.microsoft.com/en-us/library/ms733033(v=VS.100).aspx

Standard endpoint
http://msdn.microsoft.com/en-us/library/ms733821(v=VS.100).aspx

Transport including HTTP, TCP, named pipes
http://msdn.microsoft.com/en-us/library/ms729350(v=VS.100).aspx

Configure Behaviors,

This objective may include but is not limited to: applying service, endpoint, and operation behaviors in configuration and code.

This objective does not include: creating a custom behavior; creating and using dispatch behaviors; loading configuration from a location other than the default application configuration file

Configuration file
http://msdn.microsoft.com/en-us/library/ms733932(v=VS.100).aspx

Implement self hosting

This objective may include but is not limited to: configuring and instantiating a service host

This objective does not include: implementing a custom service host

Hosting a service
http://msdn.microsoft.com/en-us/library/bb332338.aspx#msdnwcfhc_topic3

Implement Web server hosting

This objective may include but is not limited to: configuring IIS/WAS for WCF; deploying to IIS/WAS; file-less configuration; specifying a ServiceHost

This objective does not include: Windows Application Server

Configuring web hosting
http://msdn.microsoft.com/en-us/library/ms734710(v=VS.100).aspx

Deploying to IIS/WAS
http://msdn.microsoft.com/en-us/library/aa751792(v=VS.100).aspx

File-less configuration

ServiceHost
http://msdn.microsoft.com/en-us/library/aa702697(v=VS.100).aspx

70-513 exam – Pausa

2010-04-22T08:07:00.001-07:00

Link a un post sobre temas del examen

http://www.jamesjfoster.com/blog/post/Resource-Links-for-70-513-WCF-Certification-Exam.aspx

70-513 Exam – parte 1

2010-04-22T07:52:00.001-07:00

Creating Services (20%)

Create service and operation contracts.

This objective may include but is not limited to: one-way, duplex, and request reply; creating and specifying fault contracts; configuration-based contracts; exposing service metadata; serialization (e.g., data contract serializer vs. XML serializer)

This objective does not include: designing service and operation contracts; transactions, instantiation, security-related attributes

OperationContract attibute
http://msdn.microsoft.com/en-us/library/system.servicemodel.operationcontractattribute.aspx

FautContract attribute
http://msdn.microsoft.com/en-us/library/ms752208.aspx

Exposing service metadata
http://msdn.microsoft.com/en-us/library/ms730243.aspx

Serialization
http://msdn.microsoft.com/en-us/magazine/cc163569.aspx

Create data contracts.

This objective may include but is not limited to: managing Known Types; controlling data serialization; using required and order attributes on data members; implementing versioning using IExtensibleDataObject; POCOs

This objective does not include: using custom serializer (ISerializationSurrogate)

KnownType attribute
http://msdn.microsoft.com/en-us/library/ms730167.aspx

Serialization
http://msdn.microsoft.com/en-us/magazine/cc163569.aspx

Data member order
http://msdn.microsoft.com/en-us/library/ms729813.aspx

Versioning
http://msdn.microsoft.com/en-us/library/ms731138.aspx

IExtensibleDataObject
http://msdn.microsoft.com/en-us/library/ms731083.aspx

POCO
http://blogs.windowsclient.net/zuker/archive/2008/05/21/wcf-poco-support-in-net-v3-5-sp1.aspx

Create message contracts.

This objective may include but is not limited to: body and header elements; using required and order attributes on members

Implement generic message handling.

This objective may include but is not limited to: creating a catch-all contract; reading and writing messages; working with properties; working with headers

This objective does not include: inheriting from Message class; using BodyWritter; creating Fault messages

Catch-all contract

Reading and writing messages

Implementing RESTful services.

This objective may include but is not limited to: accessing HTTP context; WebGet/WebInvoke, UriTemplates; JSON/POX

http://msdn.microsoft.com/en-us/library/dd203052.aspx

HTTP context

WebGet/WebInvoke
http://msdn.microsoft.com/en-us/library/bb412172.aspx

UriTemplates

JSON/POX

Create and configure a Routing service.

This objective may include but is not limited to: filters, static and dynamic, context-based routing; router interfaces.

Create and configure a Discovery service.

This objective may included but is not limited to: configuring ad hoc and managed modes; Discovery scopes; service announcements

70-513 Exam - parte 0

2010-04-21T09:54:00.001-07:00

TS: Windows Communication Foundation Development with Microsoft .NET Framework 4

Habiendo rendido el examen 70-519 (beta) me empiezo a preparar para el de WCF. No se resultados aun.

Va el summary de skills necesarios. Y en post posteriores (valga la redundancia) lo ire desarrollando.

Creating Services (20%)

Create service and operation contracts.

This objective may include but is not limited to: one-way, duplex, and request reply; creating and specifying fault contracts; configuration-based contracts; exposing service metadata; selecting serialization (e.g., data contract serializer vs. XML serializer)

This objective does not include: designing service and operation contracts; transactions, instantiation, security-related attributes
Create data contracts.

This objective may include but is not limited to: managing Known Types; controlling data serialization; using required and order attributes on data members; implementing versioning using IExtensibleDataObject; POCOs

This objective does not include: using custom serializer (ISerializationSurrogate)
Create message contracts.

This objective may include but is not limited to: body and header elements; using required and order attributes on members
Implement generic message handling.

This objective may include but is not limited to: creating a catch-all contract; reading and writing messages; working with properties; working with headers

This objective does not include: inheriting from Message class; using BodyWriter; creating Fault messages
Implement RESTful services.

This objective may include but is not limited to: accessing HTTP context; WebGet/WebInvoke, UriTemplates; JSON/POX
Create and configure a Routing service.

This objective may include but is not limited to: filters, static and dynamic, context-based routing, content-based routing; router interfaces
Create and configure a Discovery service.

This objective may include but is not limited to: configuring ad hoc and managed modes; Discovery scopes; service announcements

Hosting and Configuring Services (18%)

Create and configure endpoints.

This objective may include but is not limited to: default and standard bindings; custom bindings created from standard binding elements; standard endpoints; transports including HTTP, TCP, named pipes, UDP, MSMQ code-based service configuration; message encoding

This objective does not include: creating a custom binding element; creating new standard endpoints, loading configuration from a location other than the default application configuration file, security, transaction, reliable sessions
Configure Behaviors.

This objective may include but is not limited to: applying service, endpoint, and operation behaviors in configuration and code

This objective does not include: creating a custom behavior; creating and using dispatch behaviors,loading configuration from a location other than the default application configuration file
Implement self hosting.

This objective may include but is not limited to: configuring and instantiating a service host

This objective does not include: implementing a custom service host
Implement Web server hosting.

This objective may include but is not limited to: configuring IIS/WAS for WCF; deploying to IIS/WAS; file-less configuration; specifying a ServiceHost

This objective does not include: Windows Application Server

Consuming Services (19%)

Create a service proxy.

This objective may include but is not limited to: using a proxy class or channel factory to create a proxy; creating a proxy for an asynchronous communication; creating a proxy for a duplex communication

This objective does not include: SvcUtil command-line switches
Configure client endpoints.

This objective may include but is not limited to: standard bindings, custom bindings created from standard binding elements, configuring behaviors; code-based and configuration-based bindings; configuring addresses

This objective does not include: security; creating custom behaviors
Invoke a service.

This objective may include but is not limited to: invoking a service operation synchronously and asynchronously; handling service faults ; using the Message class; managing the life cycle of the proxy (open channels, close channels, abort channels, handle faulted channels); implementing duplex communication
Consume RESTful services.

This objective may include but is not limited to: access HTTP context; JSON/POX
Implement service Discovery.

This objective may include but is not limited to: configuring target scope; monitoring service announcements

Securing Services (17%)

Configure secure Bindings.

This objective may include but is not limited to: transport, message, mixed mode
Configure message security.

This objective may include but is not limited to: specifying protection levels on different message parts
Implement Authentication.

This objective may include but is not limited to: Microsoft ASP.NET Membership Provider, Custom Provider, Windows Integrated Security, certificates (X.509), Federated Authentication endpoint identity; configuring client credentials; Custom Validator

This objective does not include: Geneva Framework
Implement Authorization.

This objective may include but is not limited to: role based, claim based; configuring role providers for endpoints; principal permission attribute

This objective does not include: rights-management authorization such as Active Directory Rights Management Services (AD RMS)
Implement Impersonation.

This objective may include but is not limited to: configuration and code; configuring WCF-specific Internet Information Services (IIS) impersonation properties; configuring impersonation options; operation-based and service-based
Implement security auditing.

This objective may include but is not limited to: using serviceSecurityAudit behavior, service auditing, audit log

Managing the Service Instance Life Cycle (13%)

Manage service instances.

This objective may include but is not limited to: per call; per session; single; code and configuration; activation and deactivation; durable services; throttling
Manage sessions.

This objective may include but is not limited to: code and configuration; session management attributes; throttling; reliable sessions; transport-level and application-level sessions; invoking a callback contract
Implement transactions.

This objective may include but is not limited to: distributed transactions; transactional queues;transaction flow; configuring transaction binding attributes; WS-AtomicTransaction (WS-AT); transactional behavior attributes at the service and operation level; using transactions in code
Manage concurrency.

This objective may include but is not limited to: single, multiple, and reentrant concurrency modes; SynchronizationContext and CallbackBehavior

This objective does not include: deadlocks and other multithreading issues
Manage consistency between instances, sessions, transactions, and concurrency.

This objective may include but is not limited to: possible combinations between instances, sessions, transactions, and concurrency (for example, instance mode single with concurrency mode multiple)

Monitoring and Troubleshooting Distributed Systems (14%)

Configure message logging.

This objective may include but is not limited to: configuring message listeners; logging level; message filters; configuring logging known PII

This objective does not include: secure message logs
Configure diagnostics.

This objective may include but is not limited to: WMI; performance counters; event logging
Debug client-service interactions.

This objective may include but is not limited to: sending server exception details to client; end-to-end tracing; interpreting output from the trace viewer (single message and end to end)

This objective does not include: tracing viewer features outside of viewing traces

C# 4.0 – Dynamic

2010-04-09T03:17:00.001-07:00

Una primera aproximación al tipo dynamic introducido en la versión 4.0 de C#

El tipo dynamic nos va a permitir instanciar un objeto en tiempo de ejecución. Con lo que podremos hacer cosas como:

            dynamic duck = GetDynamic();
           
            Console.WriteLine(duck.bark());

La instanciación se evalúa en tiempo de ejecución por lo que si el objeto devuelto por GetDynamic() no contiene definición del método bark() recibiremos un error en tiempo de ejecución.

Qué diferencia tiene con var? Básicamente var es una asignación por inferencia, o sea que en tiempo de compilación será el compilador el encargado de inferir el tipo de acuerdo al contexto, un par de ejemplos sencillos:

var duck = new Duck();

En este ejemplo sencillamente el compilador infiere que duck es una instancia de la clase Duck;

            var duck = animals.Where(a => a.HasFeather() && a.LegQty() == 2)
                .FirstOrDefault();

En este ejemplo es un poco más complicado inferir el tipo. Igualmente el compilador lo realizará en tiempo de compilación.

Ahora cual sería la diferencia con el que es la base de nuestra jerarquía de clases object? A simple vista parecería que son similares. Pero recordemos que hasta la versión 4.0 de C# nuestro lenguaje era estáticamente tipado. por lo que utilizar object no hacía que el compilador no verifique el tipo en tiempo de compilación, sino todo lo contrario. Cada vez que el compilador encuentra un object validará que las operación que se realizan con él sean válidas para el tipo casteado. Aquí entran los conceptos de boxing y unboxing.

Veamos ejemplo:

            Object dog = GetObject();
            Console.WriteLine(dog.bark());

Este ejemplo directamente no compila. object no contiene un método bark()

            Console.WriteLine(((Dog)dog).bark());

El precioso mundo del casteo. Aquí vemos que necesariamente en momento de compilación el compilador debe conocer cual es la clase para poder utilizar los métodos que correspondan.

Las posibilidades son infinitas. Como así también salirnos de la tutela de nuestro compilador puede complicarnos la vida.

70-519 – Free training kit

2010-04-02T06:33:00.001-07:00

Para concluir con el material

para rendir el examen 70-519 les dejo el link al training kit de Visual Studio 2010 y .Net Framework 4.

http://www.microsoft.com/downloads/details.aspx?FamilyID=752CB725-969B-4732-A383-ED5740F02E93&displaylang=en

70-519 – parte 7

2010-04-01T11:34:00.001-07:00

Designing a Deployment Strategy (14%)

Index

Design a deployment process

This objetive may include but not limited to: Windows Installer (MSI) vs. xcopy vs. Web Deployment Tool, scaling, rolling deployments.

Windows Installer MSI
http://msdn.microsoft.com/en-us/library/aa367449(VS.85).aspx

xcopy
http://msdn.microsoft.com/en-us/library/f735abw9.aspx

Web Deployment Tool
http://channel9.msdn.com/posts/VisualStudio/Web-Development-and-Deployment-with-Visual-Studio-2010/
http://blogs.msdn.com/webdevtools/archive/2009/02/04/web-deployment-with-vs-2010-and-iis.aspx
http://live.visitmix.com/MIX10/Sessions/FT14

Scaling

Rolling deployments

Design configuration management

This objetive may include but is not limited to: using the ConfigSource attribute (for example, connection strings), staging vs. production vs. development, topologies, machine config vs, web.config, using IIS vs. Visual Studio Development Server during development, application pools, configuration inheritance.

ConfigSource attribute
http://msdn.microsoft.com/en-us/library/ms228167.aspx

Staging vs. production vs. development
http://www.slideshare.net/ecastrom/easing-aspnet-web-and-sql-server-database-deployment-withvs-2010-and-msdeploy-2167629

Machine config vs. web.config

Application pools

Configuration inheritance

Plan for scalability and reliability

This objetive may include but is not limited to: scaling up, scaling out, at physical level and at architectural level, impact of offloading technologies on load balancing, including slate, synchronazing machine and encryption keys.

Scaling Up

Scaling Out (physical and architectural level)

http://msdn.microsoft.com/en-us/magazine/cc500561.aspx

Design a health monitoring strategy

This objetive may include but is not limited to: when to monitor application or business-related events (e.g.. on UI every time clicked or in business layer) determining a strategy for using ASP.NET Health Monitoring, throttling, filtering, delivery method

70-519 – parte 6

2010-03-30T08:51:00.001-07:00

Preparing For and Investigating Application Issues (15%)

Choose a testing methodology

This objetive may include but is not limited to: black box, integration, regression, coverage, API testing, performance testing, security testing

Black Box
Black box testing. This approach tests all possible combinations of end-user actions. Black box testing assumes no knowledge of code and is intended to simulate the end-user experience. You can use sample applications to integrate and test the application block for black box testing. You can begin planning for black box testing immediately after the requirements and the functional specifications are available.
http://en.wikipedia.org/wiki/Black-box_testing

Integration
http://en.wikipedia.org/wiki/Integration_testing
http://msdn.microsoft.com/en-us/library/aa292128(VS.71).aspx

Regression
http://en.wikipedia.org/wiki/Regression_testing
http://msdn.microsoft.com/en-us/library/aa292167(VS.71).aspx

Coverage
http://en.wikipedia.org/wiki/Code_coverage
http://msdn.microsoft.com/en-us/library/ms182496(VS.100).aspx

API testing
http://msdn.microsoft.com/en-us/library/cc300143.aspx

Performance testing
http://en.wikipedia.org/wiki/Software_performance_testing
http://msdn.microsoft.com/en-us/library/bb924375.aspx

Security testing
http://msdn.microsoft.com/en-us/magazine/cc507646.aspx

This objective does not include: load testing, Web testing, unit testing

Design an exception handling strategy

This objetive may include but is not limited to: HandleError attibute in MVC, common error pages, post-error processing, global vs page level.

HandleError attibute in MVC
The HandleError attribute (which appears on the default controllers in an MVC project) tells the framework that if an unhandled exception occurs in your controller that rather than showing the default Yellow Screen of Death it should instead serve up a view called Error. The controller-specific View folder will be checked first (eg. Views/Home/Error.aspx) and if it's not found, the Shared folder (Views/Home/Error.aspx) will be used.
http://weblogs.asp.net/scottgu/archive/2008/07/14/asp-net-mvc-preview-4-release-part-1.aspx

Common error pages
http://aspalliance.com/1008_Working_with_Custom_Error_Pages_Using_ASPNET.5

Post-error processing

Global vs. page level
http://www.15seconds.com/issue/030102.htm

Recommend and approach to debugging

This objetive may include but is not limited to: tools and approaches for a given scenario (for example, memory dumps, DebuggingAttributes, crashes vs hangs, deadlocks, assembly binding), when to attack a process (visual Studio Development Server vs. IIS vs. Internet Explorer), root cause analisys.

The objetive doesn’t include: basic breakpoints

Memory dumps

DebuggingAttributes

Crashes vs. hangs

Deadlocks

Asembly bindings

Root cause analisys

Recommend an approach to performace issues.

This objetive may include but is not limited to: wich instrumentation to watch or create, (including performance counters and event tracking) to analyze performance issues, page and fragment caching.

70-519 – parte 5

2010-03-28T18:52:00.001-07:00

Designing Security Achitecture and Implementation (17%)

Plan for operational security

This objetive may include but is not limited to: approaches for process; and resource-level security, including local and remote resources; Code-Access Security (CAS), including trust level, process identity, application pool, and identity tag.

Approaches for process

http://msdn.microsoft.com/en-us/magazine/ee819091.aspx

Resource-level security

Code-Access Security (CAS)
http://en.wikipedia.org/wiki/Code_Access_Security
http://msdn.microsoft.com/en-us/library/930b76w0.aspx

Important!! Security changes in .Net 4
http://msdn.microsoft.com/en-us/library/dd233103(VS.100).aspx

Design and authentication and authorization model

This objetive may include but is not limited to: authentication providers, including WindowsForms, and custom user identity flowthrough (for example, trusted subsystem), role management, membership providers, URL authorization (for example, AuthorizationAttribute), file authorization, Authorization Manager (AzMan)

Authentication providers
http://msdn.microsoft.com/en-us/library/9wff0kyh(VS.100).aspx

Role management
http://msdn.microsoft.com/en-us/library/5k850zwb(VS.100).aspx

Membership provider
http://msdn.microsoft.com/en-us/library/tw292whz(VS.100).aspx

URL Athorization
http://msdn.microsoft.com/en-us/library/wce3kxhd(VS.100).aspx

AzMan
http://msdn.microsoft.com/en-us/library/ms998336.aspx

Plan for minimizing attack surfaces

This objetive may include but is not limited to: input validation, throttling inputs, request filtering, where to use Secure Sockets Layer (SSL)

Input validation (buscar material mas moderno)
http://msdn.microsoft.com/en-us/library/ms972961.aspx

Throttling inputs

Request filtering
http://msdn.microsoft.com/en-us/library/system.web.httprequest.filter(VS.100).aspx

SSL
http://en.wikipedia.org/wiki/HTTP_Secure

70-519 – parte 4

2010-03-26T16:03:00.001-07:00

Designing Data Strategies and Structures (18%)

Index

Parte 0 | Parte 1 | Parte 2 | Parte 3a | Parte 3b

Design data access

Design data presentation and interaction

This objetive may include but is not limited to: pulling data from data layer and binding into views, pages and controls, and poulling data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically.

Bindings
http://msdn.microsoft.com/en-us/magazine/ee819084.aspx

ModelBinders
http://msdn.microsoft.com/en-us/library/dd410405(VS.100).aspx
http://www.microsoft.com/belux/msdn/nl/chopsticks/default.aspx?id=798

Data source controls
http://aspnet.4guysfromrolla.com/articles/011106-1.aspx

HtmlHelper extensions
http://blogs.microsoft.co.il/blogs/gilf/archive/2009/01/13/extending-asp-net-mvc-htmlhelper-class.aspx

Plan for data validation

Contextual validation

http://msdn.microsoft.com/en-us/library/ms191447.aspx

Synchro between UI and data layer

http://msdn.microsoft.com/en-us/library/dd901590(VS.95).aspx

70-519 – una pausa

2010-03-25T19:00:00.001-07:00

Ya van cinco post, creo que tengo posibilidades de llegar a preparar el examen. Lo que me he dado cuenta que los post se van convirtiendo mas en una especie de wiki que vuelvo y los updateo constantemente que en un blog en si. por lo que si existe una propuesta de armar esto de alguna otra forma es bienvenido.

Index

Parte 0 | Parte 1 | Parte 2 | Parte 3a | Parte 3b

70-519 – parte 3b

2010-03-24T16:05:00.001-07:00

Designing the User Experience (17%)

Index

Parte 0 | Parte 1 | Parte 2 | Parte 3a

Plan for cross-browser and/or form factors

This objective may include but is not limited to: evaluating the impact on client side behaviors, themes, bandwidth, style sheets (including application design - task based or scaled rendering of existing page), when to apply Browsers file, structural approaches, user agents, different platforms (mobile vs. desktop)

Evaluating the impact on

client side behaviors
themes
bandwidht
style sheets

Plan for globalization

This objective may include but is not limited to: designing to support local, regional, language, or cultural preferences, including UI vs. data localization (for example, implementing at database level or resource level), when to use CurrentCulture vs. CurrentUICulture, globalization rollout plan (for example, setting base default language, planning localization), handling Unicode data (for example, what fields to include, request encoding), right-to-left support, vertical text and non-Latin topographies, calendars, data formatting, sorting

UI Localization

Data Localization

Resources

CurrentCulture vs. CurrentUICulture

Planning localization

Unicode

righ-to-left support

Vertical text Non-Latin typos

Calendars / Data formatting

Sorting

70-519 – parte 3a

2010-03-24T08:01:00.001-07:00

Designing the User Experience (17%)

Index

Parte 0 | Parte 1 | Parte 2

Design the site structure.

This objective may include but is not limited to: designing application segmentation for manageability and security (for example, using areas, shared views, master pages, and nested master pages), appropriate use of style sheets, client-side scripting, themes, client ID generation, rendering element modes, routing engine

Una digresión, leamos un poco sobre UX http://en.wikipedia.org/wiki/User_experience

Materiales

Una pagina interesante para ver los cambios de Asp.Net 4 y que nos va a ayudar a entender un poco mas estos puntos http://www.asp.net/LEARN/whitepapers/aspnet4/default.aspx
Ahora yendo punto por punto vamos buscando mas material que nos pueda servir para prepararnos mejor.

Areas

Areas let you group controllers and views into sections of a large application in relative isolation from other sections. Each area can be implemented as a separate ASP.NET MVC project that can then be referenced by the main application. This helps manage complexity when you build a large application and makes it easier for multiple teams to work together on a single application.

Shared Views
Master Pages
http://msdn.microsoft.com/en-us/library/wtxbf3hh(VS.100).aspx

Nested Master Pages
http://msdn.microsoft.com/en-us/library/x2b3ktt7(VS.100).aspx

Style Sheets
http://www.adobe.com/devnet/dreamweaver/articles/why_css.html
http://msdn.microsoft.com/en-us/library/h4kete56(VS.100).aspx

Client-side scripting
http://msdn.microsoft.com/en-us/library/aa479302.aspx
http://msdn.microsoft.com/en-us/library/aa479011.aspx
http://www.chadmyers.com/Blog/archive/2007/12/13/using-jquery-with-asp.net-mvc.aspx

Themes
http://msdn.microsoft.com/en-us/library/ykzx33wh(VS.100).aspx

Client ID generation
http://msdn.microsoft.com/en-us/library/system.web.ui.control.clientid(VS.100).aspx
http://gerardocontijoch.wordpress.com/2009/06/12/generacion-personalizada-de-ids-en-asp-net-4-0/

Rendering elements modes

By default, when a Web application or Web site targets the .NET Framework 4, the controlRenderingCompatibilityVersion attribute of the pages element is set to "4.0". This element is defined in the machine-level Web.config file and by default applies to all ASP.NET 4 applications:
 
<system.web> 
  <pages controlRenderingCompatibilityVersion="3.5|4.0"/> 
</system.web> 
The value for controlRenderingCompatibility is a string, which allows potential new version definitions in future releases. In the current release, the following values are supported for this property:

"3.5". This setting indicates legacy rendering and markup. Markup rendered by controls is 100% backward compatible, and the setting of the xhtmlConformance property is honored.

"4.0". If the property has this setting, ASP.NET Web server controls do the following:

The xhtmlConformance property is always treated as "Strict". As a result, controls render XHTML 1.0 Strict markup.

Disabling non-input controls no longer renders invalid styles.

div elements around hidden fields are now styled so they do not interfere with user-created CSS rules.

Menu controls render markup that is semantically correct and compliant with accessibility guidelines.

Validation controls do not render inline styles.

Controls that previously rendered border="0" (controls that derive from the ASP.NET Table control, and the ASP.NET Image control) no longer render this attribute.

Routing engine

http://msdn.microsoft.com/en-us/magazine/dd347546.aspx

Continuara….

Plan for cross-browser and/or form factors.

Plan for globalization.

70-519 – parte 2

2010-03-23T02:55:00.001-07:00

Index

Parte 0
Parte 1

Designing the Application Architecture (19%)

Un buen libro del equipo de patterns&practices que nos puede ayudar con esta parte del examen es
http://msdn.microsoft.com/en-us/library/dd673617.aspx

Plan the division of application logic

This objective may include but is not limited to: choosing between client-side and server side processing, planning separation of concern, (for example, partitioning functionality between controllers and evaluating business and data service consumption), planning for long-running processes (for example, synchronous vs. asynchronous)

http://msdn.microsoft.com/en-us/library/428509ah(VS.100).aspx
http://msdn.microsoft.com/en-us/library/ms998548.aspx
http://blogs.msdn.com/diegumzone/archive/2006/10/09/3_2D00_Tier_2C00_-3_2D00_Layer_2C00_-MVC_3A00_-a-Trio-of-Famous-Trios.aspx

Long-running process (synchro vs. asynchro)
http://www.ajaxmatters.com/articles/asp/long_run_process_p1.aspx
http://www.codeproject.com/KB/aspnet/asynctransactionhandler.aspx

Analyze requirements and recommend a system topology

This objective may include but is not limited to: designing interaction between applications, mapping logical design to physical implementation, validating nonfunctional requirements and cross-cutting concerns (for example, communications, operations management, and security), evaluating baseline needs (for example, scale and quality of service)

Cross-cutting concerns
http://msdn.microsoft.com/en-us/library/ee658105.aspx

Evaluating baseline needs

Choose appropriate client-side technologies

This objective may include but is not limited to: JavaScript, ASP.NET AJAX, jQuery, Microsoft Silverlight

JavaScript
http://es.wikipedia.org/wiki/JavaScript

Asp.Net WebForms
http://www.asp.net/web-forms/

Asp.Net MVC
http://www.asp.net/mvc/

JQuery
http://docs.jquery.com/Tutorials

AJAX
http://www.asp.net/ajax/

Silverlight
http://www.silverlight.net/

http://msdn.microsoft.com/en-us/library/dd410060(VS.100).aspx

Choose appropriate server-side technologies

This objective may include but is not limited to: user controls, server controls, partials, custom HtmlHelper extensions, Web parts, inheriting controls, dynamic data controls

User controls
http://msdn.microsoft.com/en-us/library/y6wb1a0e(VS.100).aspx

Server controls
http://msdn.microsoft.com/en-us/library/zt27tfhy(VS.100).aspx

Web parts
http://msdn.microsoft.com/en-us/library/e0s9t4ck(VS.100).aspx

Partials

Custom HtmHelper extensions
http://msdn.microsoft.com/en-us/library/system.web.mvc.htmlhelper(VS.100).aspx

Inheriting controls
http://weblogs.asp.net/cfigueroa/archive/2009/07/28/herencia-visual-asp-net.aspx

dynamic data controls
http://weblogs.asp.net/scottgu/archive/2007/12/14/new-asp-net-dynamic-data-support.aspx

Desing state management

This objective may include but is not limited to: designing an application for the proper use of application state, session state, and request state (for example, ViewState, ControlState, Cache object, cookies, and client-side persistence)

Application state
http://msdn.microsoft.com/en-us/library/ms178594(VS.100).aspx

Session state
http://msdn.microsoft.com/en-us/library/ms178581(VS.100).aspx

Request state ( ViewState, ControlState, Cache object, cookies, and client-side persistence, Velocity)
http://msdn.microsoft.com/en-us/library/bb386448(VS.100).aspx

http://msdn.microsoft.com/en-us/library/z1hkazw7(VS.100).aspx

70-519 Beta – parte 1

2010-03-23T02:36:00.001-07:00

Rol del Web server y protocolo HTTP

El web server responde a llamadas generadas por un browser. La llamada básica es

GET /Default.aspx HTTP/1.1

Host: www.hoversoft.com.ar

En esta llamada por medio del verbo Get el browser le solicita el recurso Default.aspx (pagina por defecto de Asp.Net) del servidor hoversoft utilizando el protocolo HTPP 1.1 (Estandar actual)

El servidor puede responder con un recurso estático y cerrar la conexión (Stateless) o mas actualmente puede dejar información de sesión y la conexión abierta (por ejemplo llamadas mediante AJAX Asynchronous JavaScript and XML)

En este momento es importante revisar los verbos básicos del estandar HTTP 1.1

Los Request y Response son manejados por Asp.Net con wrappers que nos permiten realizar varias acciones con ellos.

La estructura de un response es algo similar a

HTTP/1.1 200 OK

Server: Microsoft/IIS 6.0

Content-Type: text/html

Content-Lenght: 38

<html><body>Hello, World!</body></html>

En la primera línea se encuentra el código de status, los cuales recomiendo conocer al menos los básicos.

En la tercera línea del response tenemos el MIME type, los cuales también es conveniente conocer los tipos básicos.

Se puede utilizar Microsoft Network monitor o un simple Telnet para ver y analizar el flujo de conexiones entre el servidor y el browser.

Preparando el examen 70-519 Beta – parte 0

2010-03-23T02:20:00.001-07:00

El examen 70-519 es parte del camino para la MCPD (Microsoft Ceritified Professional Developer). Al ser un examen nuevo no existen aun materiales programáticos para prepararlo. Encontraremos material en el examen 70-562 TS: Microsoft .Net Fameqork 3.5 Asp.Net development, (hay que tener en cuenta que este examen era relacionado al framework 3.5 y se utilizaba la version 2008 del VIsual Studio, mientras que el que voy a preparar utiliza el framework 4 y la version 2010 del Visual Studio)

Por ser un examen beta tengo chance para rendirlo hasta el 30 de abril, pero lo schedulee (valga el anglicismo) para el 20 de abril. Con lo que empecemos.

Guia

Designing the Application Architecture (19%)

Plan the division of application logic.

This objective may include but is not limited to: choosing between client-side and server side processing, planning separation of concern, (for example, partitioning functionality between controllers and evaluating business and data service consumption), planning for long-running processes (for example, synchronous vs. asynchronous)
Analyze requirements and recommend a system topology.
This objective may include but is not limited to: designing interaction between applications, mapping logical design to physical implementation, validating nonfunctional requirements and cross-cutting concerns (for example, communications, operations management, and security), evaluating baseline needs (for example, scale and quality of service)
Choose appropriate client-side technologies.
This objective may include but is not limited to: JavaScript, ASP.NET AJAX, jQuery, Microsoft Silverlight
Choose appropriate server-side technologies.
This objective may include but is not limited to: user controls, server controls, partials, custom HtmlHelper extensions, Web parts, inheriting controls, dynamic data controls
Design state management.
This objective may include but is not limited to: designing an application for the proper use of application state, session state, and request state (for example, ViewState, ControlState, Cache object, cookies, and client-side persistence)

Designing the User Experience (17%)

Design the site structure.

This objective may include but is not limited to: designing application segmentation for manageability and security (for example, using areas, shared views, master pages, and nested master pages), appropriate use of style sheets, client-side scripting, themes, client ID generation, rendering element modes, routing engine
Plan for cross-browser and/or form factors.

This objective may include but is not limited to: evaluating the impact on client side behaviors, themes, bandwidth, style sheets (including application design - task based or scaled rendering of existing page), when to apply Browsers file, structural approaches, user agents, different platforms (mobile vs. desktop)
Plan for globalization.

This objective may include but is not limited to: designing to support local, regional, language, or cultural preferences, including UI vs. data localization (for example, implementing at database level or resource level), when to use CurrentCulture vs. CurrentUICulture, globalization rollout plan (for example, setting base default language, planning localization), handling Unicode data (for example, what fields to include, request encoding), right-to-left support, vertical text and non-Latin topographies, calendars, data formatting, sorting

Designing Data Strategies and Structures (18%)

Design data access.

This objective may include but is not limited to: choosing data access technologies such as ADO.NETData Services, Entity Framework, Windows Communications Foundation (WCF), and ASP.NET Web Services
Design data presentation and interaction.

This objective may include but is not limited to: pulling data from data layer and binding into views, pages, and controls, and pulling data back to data layer by using ModelBinders, data source controls, and HtmlHelper extensions, or programmatically
Plan for data validation.

This objective may include but is not limited to: contextual validation vs. data integrity, where to validate data, synchronization between UI and data layer, data annotations

Designing Security Architecture and Implementation (17%)

Plan for operational security.

This objective may include but is not limited to: approaches for process- and resource-level security, including local and remote resources, Code Access Security (CAS), including trust level, process identity, application pool, and identity tag
Design an authentication and authorization model.

This objective may include but is not limited to: authentication providers, including WindowsForms, and custom user identity flowthrough (for example, trusted subsystem), role management, membership providers, URL authorization (for example, AuthorizationAttribute), file authorization, Authorization Manager (AzMan)
Plan for minimizing attack surfaces.

This objective may include but is not limited to: input validation, throttling inputs, request filtering, where to use Secure Sockets Layer (SSL)

Preparing For and Investigating Application Issues (15%)

Choose a testing methodology.

This objective may include but is not limited to: black box, white box, integration, regression, coverage, API testing, performance testing, security testing

This objective does not include: load testing, Web testing, unit testing
Design an exception handling strategy.

This objective may include but is not limited to: HandleError attribute in MVC, common error pages, post-error processing, global vs. page level
Recommend an approach to debugging.

This objective may include but is not limited to: tools and approaches for a given scenario (for example, memory dumps, DebuggingAttributes, crashes vs. hangs, deadlocks, assembly binding), when to attach to process (Visual Studio Development Server vs. IIS vs. Internet Explorer), root cause analysis

This objective does not include: basic breakpoints
Recommend an approach to performance issues.

This objective may include but is not limited to: which instrumentation to watch or create (including performance counters and event tracing) to analyze performance issues, page and fragment caching

Designing a Deployment Strategy (14%)

Design a deployment process.

This objective may include but is not limited to: Windows Installer (MSI) vs. xcopy vs. Web Deployment Tool, scaling, rolling deployments
Design configuration management.

This objective may include but is not limited to: using the ConfigSource attribute (for example, connection strings), staging vs. production vs. development, topologies, machine.config vs. web.config, using IIS vs. Visual Studio Development Server during development, application pools, configuration inheritance
Plan for scalability and reliability.

This objective may include but is not limited to: scaling up, scaling out, at physical level and at architectural level, impact of offloading technologies on load balancing, including state, synchronizing machine and encryption keys
Design a health monitoring strategy.

This objective may include but is not limited to: when to monitor application or business-related events (e.g., on UI every time clicked or in business layer), determining a strategy for using ASP.NET Health Monitoring, throttling, filtering, delivery method

Materiales

Indispensable. Visual Studio 2010 profesional o superior. Se puede bajar el RC.

MSDN y seleccionar las opciones de .Net Framework 4

Material de Microsoft Learning no hay disponible aun.

Material bibliográfico Self-Pace Training Kit. Para el framework 3.5 (verificar las diferencias)

Diferencias entre los frameworks

En MSDN y en StackOverflow

BDD

2009-09-22T14:02:00.001-07:00

Otra vez Rob Conery. esto es más un tweet que un post. Rob escribe sobre BDD, un post interesante, lo voy a leer en profundidad y compararlo con las técnicas que nosotros utilizamos. Por ahora y como comentario BDD funciona, aporta claridad y se puede complementar con TDD (y buenos User Stories por supuesto). Vuelven los post y espero que sea una vuelta que se mantenga en el tiempo.

HOT Hover Over Technologies

70-519 Passed!!!

Stress & load web tests

Primeras semanas

Stress test usando Pylot

Instalando Pylot

Usando Pylot

Visual Studio 2010 Stress tests

Próximos pasos: escalar la solución.

Requerimientos desde diferentes dominios

Y como el movimiento se demuestra andando…

getJson desde Asp.Net MVC

View

Controller

70-516 Exam – parte única

70-519 Exam – parte 5

Managing the Service Instance Life Cycle (13%)

Manage service instances.

Manage sessions.

Implement transactions.

Manage concurrency.

Manage consistency between instances, sessions, transactions, and concurrency

70-513 exam – parte 4

Securing Services (17%)

Configure secure Bindings

Configure message security

70-513 Exam – parte 3

Consuming Services (19%)

Create a service proxy

Configure client endpoints.

Invoke a service

Consume RESTful services.

Implement service discovery

70-513 Exam – parte 2

Hosting and Configuring Services (18%)

Create and configure endpoints.

Configure Behaviors,

Implement self hosting

Implement Web server hosting

70-513 exam – Pausa

70-513 Exam – parte 1

Creating Services (20%)

Create service and operation contracts.

Create data contracts.

Create message contracts.

Implement generic message handling.

Implementing RESTful services.

Create and configure a Routing service.

Create and configure a Discovery service.

70-513 Exam - parte 0

TS: Windows Communication Foundation Development with Microsoft .NET Framework 4

C# 4.0 – Dynamic

70-519 – Free training kit

70-519 – parte 7

Designing a Deployment Strategy (14%)

Index

Design a deployment process

Design configuration management

Plan for scalability and reliability

70-519 – parte 6

Preparing For and Investigating Application Issues (15%)

Index

Choose a testing methodology

Design an exception handling strategy

Recommend and approach to debugging

Recommend an approach to performace issues.

70-519 – parte 5

Designing Security Achitecture and Implementation (17%)

Index

Plan for operational security This objetive may include but is not limited to: approaches for process; and resource-level security, including local and remote resources; Code-Access Security (CAS), including trust level, process identity, application pool, and identity tag.

Design and authentication and authorization model

Plan for minimizing attack surfaces

70-519 – parte 4

Designing Data Strategies and Structures (18%)

Index

Design data presentation and interaction

Plan for data validation

70-519 – una pausa

Index

70-519 – parte 3b

Plan for operational security

This objetive may include but is not limited to: approaches for process; and resource-level security, including local and remote resources; Code-Access Security (CAS), including trust level, process identity, application pool, and identity tag.