ASPhere is a freeware tool that helps to create and modify configuration files for ASP.NET.
What if one could encode all the information required to complete the registration into the actual confirmation link? The downside is that you end up with a long and not so pretty URL, the upside is that you end up with a new level of ease and flexibility. This is not only for confirming account registration, but also for passing data from emails and between pages etc.
This project consists of a URL Object Serialization component that provides serialization, compression, and encryption of CLR objects so that they can be embedded within URLs, a user-account purging component that performs the periodic removal of unconfirmed user accounts, and a demonstration website that shows the use of the components in an ASP.NET user-account confirmation system.
URL Length Limitations
When generating URLs, we must be aware that some browsers and Web servers have a limit on URL length. URLs using the GET method in Internet Explorer are limited to 2,083 characters. The POST method also limits the URL length to 2,083, but this does not include query string parameters (http://support.microsoft.com/kb/208427). This point is important when intending to serialize large object graphs, or instances with a lot of member data. Safari, Firefox, and Opera (version 9 and above) appear to have no such limit. Older browsers such as Netscape 6, support around 2,000 characters.
As far as Web servers go, IIS supports up to 16,384 characters. For those using Mono and Apache, however, Apache supports up to 4,000 characters (Boutell, 2006).
So, the short story is, if you wish to maintain compatibility with most browsers, then you should ensure that all URLs remain under 2,000 characters. This gives us about 8000 bytes or 7.8 KBs to work with. Not too shabby.
Visual Studio 2008 Web Deployment Projects is an add-in to Visual Studio 2008 which provides developers with advanced compilation and deployment options… A Web Deployment project is extensible, enabling web developers to create pre-build and post-build actions…
You can download this RTW version from http://www.microsoft.com/downloads/details.aspx?FamilyId=0AA30AE8-C73B-4BDD-BB1B-FE697256C459&displaylang=en
A Web Deployment project provides the following features for building and deploying ASP.NET 2.0 Web sites:
- ASP.NET 2.0 precompilation as part of the build process.
- More flexible options for generating compiled assemblies from a Web project, including these alternatives:
- A single assembly for the entire Web site.
- One assembly per content folder.
- A single assembly for all UI components.
- An assembly for each compiled file in the Web site.
- Assembly signing options.
- The ability to define custom pre-build and post-build actions.
- The ability to exclude folders from the build.
- The ability to modify settings in the Web.config file, such as the <connectionString> element, based on the Visual Studio build configuration.
- Support for creating .msi files with setup projects.
A tutorial on Web Deployment Projects can be found at Scottgu’s blog
Watch the flotsam and jetsam of data that you care about in this mash-up of Facebook, Flickr, Twitter, YouTube, Digg and RSS blogs. Using this simple application, you can configure what you want to watch and the speed in which you see it. Want to view what your Twitter friends are doing? Want to see the photos your friends have posted on Facebook? Or maybe their photos on Flickr, too? Download now and have all of your photos, Tweets, Diggs, Facebook invites & pokes and feeds come to you!
Being a WPF application, Flotzam can be easily restyled. From the enter/exit transitions for new items to the overall visual look and feel of the Flotzam interface, you can do almost anything you want just by tweaking the XAML mark-up.
The more I delve into distributed architectures, the more I’m feeling like Microsoft just isn’t providing much of a path forward to scalable distributed systems. Case in point: state management.
By default, session state in ASP.NET is stored in the web server’s memory. To share state across servers – which you would want to do in a server farm – you need to store it in SQL Server or in the .NET state service. This is fine for small solutions, but once you bump up against the need to partition state across many servers or multiple hosting locations, things start to get complex and expensive.
Using JavaSpaces from .NET
3rd Parties: ScaleOut, NCache, GigaSpaces
- Install this QFE.
- Note, if you’re on 64-bit Windows, read the description as there is a single manual step for 64-bit folks like me.
Go into Tools|Options|Debugging|General and turn off “Enable Just My Code” and turn on “Enable Source Server.” Go to Symbols and add this URL http://referencesource.microsoft.com/symbols and a local cache path. Make sure “search only when symbols are loaded manually” is checked.
The New York Times reader is based on this SDK. To allow newspapers and content publishers to create rich, “occasionally-connected” experiences based on the flow layout capabilities in WPF.
The reader toolkit is called Syndicated Client Experiences Starter Kit. This reflects its potential to go beyond a news reading scenario and handle other kinds of data synchronization and display needs.