Search results for 'app:weblogs' matching tag 'ASP.NET'

Recursos destacados en MSDN ASP.NET Home

cwalzer — Wed, 21 Oct 2009 05:00:00 GMT

Me ha tocado la grata tarea de seleccionar y promover los links que se listan en la sección de Recursos Destacados de MSDN ASP.NET Home.

La idea es promover artículos originales de autores de la comunidad de habla hispana, sobre temas de desarrollo Web. Estaré seleccionando unos 10 artículos al mes.

Algunos temas de ejemplo: ASP.NET, Silverlight, IIS, Seguridad, AJAX, IE, ASP.NET MVC, ASP.NET 4.0

Si encuentras algún artículo interesante o quieres promover el tuyo, comunícate conmigo vía http://twitter.com/cwalzer.

Saludos

Nederlandse CodeCamp 2009

Maurice — Mon, 19 Oct 2009 05:00:00 GMT

Op 21 november 2009 organiseren de SDN, Stichting dotNed en VBcentral samen het derde Nederlandse Code Camp. Dit is een dag lang met code, code sharing, freaking en gezellig samenzijn. Een evenement door ontwikkelaars, voor ontwikkelaars. De regie ligt voor een belangrijk deel bij de deelnemers! Het aantal plaatsen voor deelnemers is wel beperkt tot maximaal 150. Wacht dus niet te lang met beslissen want voor je het weet is er geen plaats meer. Vergeet bij je aanmelding niet op te geven welke onderwerpen je interesse hebben. Bovendien nodigen we iedereen graag uit om zelf een sessie in te vullen.

Op de website, www.codecamp.nl, vind je meer informatie en kan je je aanmelden.

Rick’s tip on ASP.NET client IDs + JQuery

luisabreu — Thu, 15 Oct 2009 05:00:00 GMT

Rick Strahl has an interesting post on how you might use JQuery’s powerful selector syntax to get a reference to an ASP.NET control placed inside a naming container. Pretty cool stuff :)

Web Application Tool Kit released

lavssun — Wed, 30 Sep 2009 05:00:00 GMT

Microsoft launched a number of Web Application Toolkits.

What is a web application ToolKit ?

Web Application Toolkits provide the packaged set of running samples, templates and documentation that enables the web developers to extend their web application capabilities

In the Microsoft WebSiteSpark launch, 7 Web Application Toolkits has been released.

	Web Application Toolkit for Internet Explorer 8 Extensibility Check out the accompanying screencast.
	Web Application Toolkit for Bing Search
	Web Application Toolkit for REST Services Check out the accompanying screencast.
	Web Application Toolkit for Mobile Web Applications Check out the accompanying screencast
	Web Application Toolkit for Template-Driven Email Check out the accompanying screencast.
	Web Application Toolkit for making Your Web Site Social Check out the accompanying screencast.
	Web Application Toolkit for FAQs. Check out the accompanying screencast.

7 tips for for loading Javascript rich Web 2.0-like sites significantly faster

omar — Fri, 25 Sep 2009 05:00:00 GMT

Introduction

When you create rich Ajax application, you use external JavaScript frameworks and you have your own homemade code that drives your application. The problem with well known JavaScript framework is, they offer rich set of features which are not always necessary in its entirety. You may end up using only 30% of jQuery but you still download the full jQuery framework. So, you are downloading 70% unnecessary scripts. Similarly, you might have written your own javascripts which are not always used. There might be features which are not used when the site loads for the first time, resulting in unnecessary download during initial load. Initial loading time is crucial – it can make or break your website. We did some analysis and found that every 500ms we added to initial loading, we lost approx 30% traffic who never wait for the whole page to load and just close browser or go away. So, saving initial loading time, even by couple of hundred milliseconds, is crucial for survival of a startup, especially if it’s a Rich AJAX website.

You must have noticed Microsoft’s new tool Doloto which helps solve the following problem:

Modern Web 2.0 applications, such as GMail, Live Maps, Facebook and many others, use a combination of Dynamic HTML, JavaScript and other Web browser technologies commonly referred as AJAX to push page generation and content manipulation to the client web browser. This improves the responsiveness of these network-bound applications, but the shift of application execution from a back-end server to the client also often dramatically increases the amount of code that must first be downloaded to the browser. This creates an unfortunate Catch-22: to create responsive distributed Web 2.0 applications developers move code to the client, but for an application to be responsive, the code must first be transferred there, which takes time.

Microsoft Research looked at this problem and published this research paper in 2008, where they showed how much improvement can be achieved on initial loading if there was a way to split the javascripts frameworks into two parts – one primary part which is absolutely essential for initial rendering of the page and one auxiliary part which is not essential for initial load and can be downloaded later or on-demand when user does some action. They looked at my earlier startup Pageflakes and reported:

2.2.2 Dynamic Loading: Pageflakes
A contrast to Bunny Hunt is the Pageflakes application, an
industrial-strength mashup page providing portal-like functionality.
While the download size for Pageflakes is over 1 MB, its initial
execution time appears to be quite fast. Examining network activity
reveals that Pageflakes downloads only a small stub of code
with the initial page, and loads the rest of its code dynamically in
the background. As illustrated by Pageflakes, developers today can
use dynamic code loading to improve their web application’s performance.
However, designing an application architecture that is
amenable to dynamic code loading requires careful consideration
of JavaScript language issues such as function closures, scoping,
etc. Moreover, an optimal decomposition of code into dynamically
loaded components often requires developers to set aside the semantic
groupings of code and instead primarily consider the execution
order of functions. Of course, evolving code and changing
user workloads make both of these issues a software maintenance
nightmare.

Back in 2007, I was looking at ways to improve the initial load time and reduce user dropout. The number of users who would not wait for the page to load and go away was growing day by day as we introduced new and cool features. It was a surprise. We thought new features will keep more users on our site but the opposite happened. Analysis concluded it was the initial loading time that caused more dropout than it retained users. So, all our hard work was essentially going to drain and we had to come up with something ground breaking to solve the problem. Of course we had already tried all the basic stuffs – IIS compression, browser caching, on-demand loading of JavaScript, css and html when user does something, deferred JavaScript execution – but nothing helped. The frameworks and our own hand coded framework was just too large. So, the idea tricked me, what if we could load functions inside a class in two steps. First step will load the class with absolutely essential functions and second step will inject more functions to the existing classes.

I published a codeproject article which shows you 7 tricks to significantly improve page load time even if you have large amount of Javascript used on the page.

7 Tips for Loading JavaScript Rich Web 2.0-like Sites Significantly Faster

Use Doloto
Split a Class into Multiple JavaScript Files
Stub the Functions Which Aren't Called During Initial Load
JavaScript Code in Text
Break UI Loading into Multiple Stages
Always Grow Content from Top to Bottom, Never Shrink or Jump
Deliver Browser Specific Script from Server

If you like these tricks, please vote for me!

Webcast para la Comunidad SharePoint México sobre autentificación basada en formularios de ASP.NET en tecnologías SharePoint

haaron — Sun, 20 Sep 2009 05:00:00 GMT

El próximo lunes 28 de septiembre estaré dando un Webcast para la Comunidad SharePoint México donde estaré platicando sobre como habilitar autentificación basada en formularios sobre sitios SharePoint. Si como parte de tus requerimientos es utilizar algún otro mecanismo de manejo de credenciales distintos a directorio activo entonces autentificación basada en formularios de ASP.NET es una opción disponible en SharePoint, en esta sesión veremos como configurar este mecanismo y los pasos necesarios para la administración de credenciales de usuario almacenadas sobre base de datos.

Más detalles aquí: http://mssharepoint.multiply.com/journal/item/250/WebCast_Comunidad_SharePoint_Mexico

Los espero, saludos.

PowerShell For The .NET Developer

paulo — Fri, 18 Sep 2009 05:00:00 GMT

Some time ago I needed to have the validationKey of the machineKey element of an ASP.NET application changed and found out that ASP.NET doesn’t provide a command-line tool (or any other) to do this.

Looking around I found several applications and code samples to do it, but to have a system administrator do this I needed to test and document the application and it was to much work for such task.

I’ve always been a supporter of the idea of PowerShell but I never used it my self. Just because I almost always have Visual Studio open and writing a simple console application is quicker and easier than learning PowerShell.

This time I decide that I would do a PowerShell script instead.

In C# I would have done something like this:

class Program
{
    private static string GenerateKey()
    {
        var buff = new byte[64];
        (new System.Security.Cryptography.RNGCryptoServiceProvider()).GetBytes(buff);
        var sb = new System.Text.StringBuilder();
        foreach (var b in buff)
        {
            sb.AppendFormat("{0:X2}", b);
        }
        return sb.ToString();
    }

    private static void Main(string[] args)
    {
        var path = args[0];
        var config = System.Web.Configuration.WebConfigurationManager.OpenMachineConfiguration(path);
        var systemWeb = config.GetSectionGroup("system.web") as System.Web.Configuration.SystemWebSectionGroup;
        var machineKey = systemWeb.MachineKey;
        machineKey.ValidationKey = GenerateKey();
        config.Save(System.Configuration.ConfigurationSaveMode.Modified);
    }
}

How would it be in PowerShell? As simple as this:

function GenerateKey
{
    [System.Byte[]]$buff = 0..63
    (new-object System.Security.Cryptography.RNGCryptoServiceProvider).GetBytes($buff)
    $sb = new-object System.Text.StringBuilder(128)
    for($i = 0; ($i -lt $buff.Length); $i++)
    {
        $sb = $sb.AppendFormat("{0:X2}", $buff[$i])
    }
    return $sb.ToString()
}

[System.Reflection.Assembly]::LoadWithPartialName("System.Web")
$config = [System.Web.Configuration.WebConfigurationManager]::OpenWebConfiguration("<path>")
$systemWeb = $config.GetSectionGroup("system.web");
$machineKey = $systemWeb.MachineKey
$machineKey.ValidationKey=GenerateKey
$config.save("Modified")

Wonder how I got from no knowledge of PowerShell to this? Simple. Something that every real .NET developer has and loves: .NET Reflector (with a PowerShell add-in, of course).

At your service (part II) – ASMX Web Service vs WCF

Joacim — Wed, 16 Sep 2009 05:00:00 GMT

Introduction

Last time I demonstrated how to develop a Windows Communication Foundation (WCF) service. This time we’re going to look at the differences between a ASP.Net WebService and a WCF service. The biggest difference between them is probably that a WebService only can be activated via HTTP and they are tightly coupled with ASP.Net HTTP pipeline. A WCF service on the other hand can be bound to a large variety of network protocols. It also doesn’t require that it is hosted on a web server, it can be hosted in a console application, in a Windows Forms app, or in a WPF application. However WCF does have an ASP.Net compatibility mode setting to enable WCF services to be configured like a web service and also mimic their behavior.

Data representation

A WebService relies on the XmlSerializer to serialize types into XML and back to a .Net type. The following is a list of the things XmlSerializer can serialize to and from XML.

Only the public properties (or fields) of an object.
Collections can be serialized only if the implement the IEnumerable or ICollection interfaces.
Classes that implements the IDictionary interface, such as Hacktable, cannot be serialized into XML.
You can use attributes from the System.Xml.Serialization namespace on your own classes and members to control how instances of that class will be serialized.
You can also generate classes that can be serialized into XML from definitions of the types in XML Schema using the xsd.exe command line tool.

Point 4 and 5 describes how you can define complex types (classes) that can be serialized to and from XML.

In WCF you would also usually begin with the definition of complex types which is done adding the DataContractAttribute and the DataMemberAttribute to the class and its members, as described in my earlier post. The DataContractAttribute can be used on classes or structures and the DataMemberAttribute on properties and/or fields, which can be either private or public.

A few important differences between the DataContractSerializer and the XmlSerializer are:

The XmlSerializer serialize all public fields and properties, while you have better control using the DataContractSerializer.
The DataContractSerializer has better performance over XmlSerializer.
The DataContractSerializer can serialize Hashtables.

Service Development

To develop a WebService you would normally decorate a class with the WebServiceAttribute and each method with the WebMethodAttribute. This is however not an optimal solution since it does not constitute a contract for the operations performed by the service. ASP.Net 2.0 tried to rectify that by allowing you to use those attributes on an interface as well. That is the preferred method of doing it since the service contract can be reused with various classes that can implement that interface.

A WCF service requires you to create a contract, since the ServiceContractAttribute only can be used on an interface. So a WebService allows you to constitute a contract but doesn’t enforce it while a WCF service do.

A WebService only incorpartes BasicHttpBinding while a WCF service can use a wide range of bindings, such as WSHttpBinding, NetTcpBinding, NetNamedPipeBinding, amongst others.

Hosting the service

ASP.Net web services are hosted on a Web Server. A WCF service can be hosted on a Web Server but can just as well be hosted by a Console- or Windows Forms application.

Conclusion

I don’t want to make any conclusions about which technique is the best to use, because that depends on the specification. A WebService is usually easier to develop but are somewhat limited. A WCF service is more versatile but can be harder to develop. To make a true comparison you should really compare the two techniques if you want to host the service on a Web Server, such as IIS, since if you want to use another host you can’t use an ASP.Net WebService. I just leave the judgment up to you.

Have fun!

[VSTS] Integrando Flex con VSTS

ffagas — Tue, 15 Sep 2009 05:00:00 GMT

Introducción

Este artículo se revisará como integrar una interface hecha en Flex Builder 3.0 con objetos de .Net, en post anteriores se revisó como hacer la integración entre Flex y TFS 2008 utilizando el plugin de teamprise en esta ocasión veremos que al momento que integramos nuestro proyecto de Flex a Visual Studio 2008 automáticamente nos habilita la administración de dicho código.

Ver más: http://geeks.ms/blogs/ffagas/archive/2009/09/15/vsts-integrando-flex-con-vsts.aspx

Retomando com o blog

andrey — Tue, 15 Sep 2009 05:00:00 GMT

Olá Amigos,

Estou retomando com o blog e vou postar muitas coisas legais que ando vendo sobre as novas tecnologias ASP.NET 3.5, C#, WPF, LINQ e muito mais.

Espero que seja proveitoso à todos.

abs