January 2007 - Posts
Some times you need to set up a set of screens to discuss an ideia and you need it quickly and with no effort. For this, MockupScreens is your tool.
It doesn't have the near real look and feel of other tools like Microsoft Office Visio but captures the ideia without the "noise" of colors and images.
It even has a slide show feature.
One of the many reasons I don't like UI development is because of a severe lack of drawing skills from my part.
If you know me, you won't believe I did this myself:
Well, Axialis' IconWorkshop gave a little help.
Defining custom culture and region information is a common practice in many enterprise environments.
In the .NET Framework 2.0, we can use the CultureAndRegionInfoBuilder class build a custom culture that is new or based on an existing culture and region. The custom culture can be installed on a computer and subsequently used by any application running on that computer.
Using this class I've built a small command line tool to extract, register and unregister culture and region information.
red-gate just released version 3 of SQL Prompt.
The landing page for the Web Client Software Factory is now available on MSDN and I'm listed as one of the external contributors, reviewers and advisors.
It contains useful information for those starting to play with or evaluating the factory. Check it out at:
You can still find the community site at http://codeplex.com/websf. Keep an eye on it because the team will be posting useful stuff frecuently!
Sometimes I need to store data scoped by some context and isolated from the other scopes.
If I'm building a library that is to be used in both Windows client and Web server enviroments, I have different isolation/scope needs: for a Web server environment, the scope is the current HTTP context; for a Windows client environment, the scope is the current process.
Having that in mind, I just published an article in CodeProject.
Filed under: .NET, Architecture, WinForms, ASP.NET, Community, SoftDev, C#, Microsoft, MSDN, MVP, Web
Basically, the lack of IIdentity in the API.
How would we had IIdentity to the MembershipProvider API? Simply, with a LoginUser method:
/// Verifies that the specified user name and password exist in the data source.
/// A <see cref="T:System.Security.Principal.IIdentity"></see> instance
/// if the specified username and password are valid; otherwise, <see langword="null"></see>.
/// <param name="username">The name of the user to validate.</param>
/// <param name="password">The password for the specified user.</param>
public abstract IIdentity LoginUser(string username, string password);
Not all membership checking is just about validating username and password. Sometimes, one needs to logon into a backend service provider and get a session token to access the membership system.
And, since we are at it, why don't we add IIdentity support to the whole API?
Hi've just been introduced to MICROANGELO. Great tool!
In most enterprise environments there usually lots of web applications from various origins (bought as a ready-made product or built for a specific purpose) that are published in most different mediums (URLs sent by e-mail, enterprise portals, rich client applications hosting web browsers, etc.).
In such an environment, coupling every caller with a specific entry point that can change with time and versions leads to a maintenance nightmare.
To solve this problem, I came up with a URL Mapper and published it in CodeProject.
I've just CodeProject published the first of a series of articles on this concept of log scoping I've developing lately.