I wrote a quick stored procedure to update the users with the new application id. Pass in the new application guid and the role name that you want to change.

set ANSI_NULLS ON
set QUOTED_IDENTIFIER OFF
GO
CREATE PROCEDURE [dbo].[aspnet_MoveUsersToNewApplicationID](@NewGuid varchar(MAX),
@RoleName varchar(MAX))
AS
BEGIN

UPDATE aspnet_roles
SET ApplicationID = @NewGuid
WHERE rolename = @RoleName

UPDATE aspnet_users
SET ApplicationID = @NewGuid
FROM  dbo.aspnet_users ui
inner join dbo.aspnet_UsersinRoles ur ON ur.userid = ui.userid
inner join dbo.aspnet_Roles r ON r.roleid = ur.roleid
WHERE r.rolename = @RoleName

UPDATE aspnet_Membership
SET ApplicationID = @NewGuid
FROM aspnet_Users ui
inner join dbo.aspnet_Membership m on m.userid = ui.userid
inner join dbo.aspnet_UsersinRoles ur on ur.userid = m.userid
inner join dbo.aspnet_Roles r on r.roleid = ur.roleid
WHERE r.rolename = @RoleName

END

Once this has run just change application name to match the new application name in the config file.

You will need to change the membership, profile and roleManager applicationName’s.

That’s it.

This article demonstrates how to implement a geographic regions search routine. After geo allocating all the individual latitude and longitude points in the result set, all hierarchical regions associated need to be mapped to the lowest common denominator – the individual points.

3^rd party Technologies

Geoname is a really great resource that holds over eight million place names and is free to download. It includes an API section for that has postal code look up, weather information, find nearby and hierarchical search.

Yahoo Geo Planet is a beta  technology that allows developers  to traverse the spatial hierarchy of geographic points. This technology was chosen over other hierarchical API’s as it will include rivers, lakes and other geographic based regions in the near future.

Implementation

Using a database of made up of primary ID’s, latitude and longitude we are able to map the ID’s to multiple geographic regions using the Yahoo Geo Planet API and the Geoname DB. A table structure was then setup with the search terms mapped to the individual points on the map.

Currently the yahoo service does not accept latitude and longitude markers, instead it takes geolocation names. To overcome this the Geoname database was used to find locations near the marker. Using a modified version of the “nearby” SQL function found here, on the Geoname database a list of places within 10 kilometres of the marker is returned in order of proximity. A recursive call checks if the place exists in the Yahoo API along side the country code.  By passing in the country code with the place name you ensure that the correct place is specified. On the first successive return from yahoo, the hierarchical structure is added to the database.  All search terms are mapped to one or more cities as defined by the Yahoo API creating a multi hierarchy location.

Conclusion

By mapping a multiple hierarchical structure for searches, applications are able to offer far more than the standard country, region and city searches prevalent today. Searches can now be based on any geographic location from mountain ranges to rivers and seas.

The call to the asyncronise method has changed from (userparameters, onComplete, onTimeOut, onError) to (userparameters, onSuccess, onFail, userContext).

Obviously this is an improvement as you can now track userContext of the Webservice calls.

To fix the above message make sure you are defining your userContext even if it is null. For example:

<script language=”javascript” type=”text/javascript”>

var userContext1;

WebContentFlow.AJAX.ContentflowAJAXAPI.BuildPage(“String parameter”,onSuccess,onFailed,userContext1)

function onSuccess(result,userContext,sender)        {            alert(result);        }

function onFailed(result)        {            alert(“Failed request >”  + result.get_message());

}

• Keep it simple. Forget all you know about tableless design and advanced CSS as HTML support in Email is awful. The worst offenders are the latest Outlook clients. So write your html as though you are still in the 90′s.
• Use inline CSS. The web based email clients strip out all the information from the body tag up. So using inline CSS the best way to go. Remember though not all CSS is recognised in some Email clients due to security issues so try stick to HTML for formatting that includes using tables for layout design.
• Images do not always display by default in the majority of clients and most of the time the alt tags are not displayed. So make sure all your content is text based. Another area to watch out for is the layout of the email. Without inserting the width and height settings the blank placeholders for your images will throw out your layout.
• HTML Email sizing. Best practice would dictate that emails use percentages for sizing as you have no idea on the dimensions of the email client. However if the design is fixed layout then try between 500px and 600px.
• Avoid JavaScript. The vast majority of clients will remove it.
• Spacing is very tricky as css margin and padding does not always work stick to td with width and height settings.
• Links should use the target=_blank. Online email clients do not want to lose their session when clicking a new link.
• Background images. Don’t bother trying to setup background images as most clients will not display them. Rather slice your images and around the content.

I recently upgraded a Linq beta product from the Beta to Final Release.

Lucky there were very few errors except for the default methods of add and delete on the System.Data.Linq.Table. The replacement methods are now InsertOnSubmit or DeleteOnSubmit. It is interesting to think that the conversation’s that took place to make such a fundamental change to one of the methods. Obviously it the new methods are more descriptive but the amount of coding hours it has cost beta developers makes you wonder. I now always think twice about naming public methods.

For more information on converting your 2005 web site to a WAP site visit http://msdn2.microsoft.com/en-us/library/aa983456.aspx.

It has been modified to allow for nulls in your fields.

set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
GO
–Exec dbo.ScriptInsertStatements ‘tablename’

CREATE Proc dbo.ScriptInsertStatements(
@TableName varchar(128),
@WhereClause varchar(400) = Null

)
AS

DECLARE @sql varchar(Max)
DECLARE @sqlColumns varchar(Max)
DECLARE @SqlColumnValues varchar(Max)

SELECT @sqlColumns = Coalesce(@SqlColumns + ‘,’,”) + Column_Name from Information_Schema.Columns where Table_name = @TableName

Print @sqlColumns

SELECT @SqlColumnValues = Coalesce(@SqlColumnValues + ‘+ ”,” + ‘,”) +
CASE
WHEN Data_Type in (‘varchar’,'nvarchar’, ‘char’, ‘nchar’, ‘datetime’ ) THEN ‘ISNULL(QuoteName(‘ + Column_Name + ‘, ””””), ”NULL”)’
ELSE ‘ISNULL(Cast(‘ + Column_Name + ‘ as varchar(MAX)), ”NULL”)’
END
FROM
Information_Schema.Columns where Table_name = @TableName

SELECT @sql = ‘Select ”Insert Into ‘ + @TableName + ‘ (‘ + @SqlColumns + ‘) Values (” + ‘ + @SqlColumnValues +’ + ”)” FROM ‘ + @TableName + IsNull(‘ WHERE ‘ + @WhereClause, ”)

exec(@sql)

Well now there is an attractive alternative – Cloud hosting. Imagine your server is run on a virtual machine that spans multiple hardware platforms, more machines can be added or subtracted depending on your websites demand. Even better this can be done in minutes so you have a promotion email going out, increase your server capability for the next 8 hours.

So far there are three main solutions available  Mosso, Microsofts Azure and Amazons EC2.

What really makes this technology stand out is the payment solution. Monthly payments are based purely on usage. Now depending on the solution you select this could included bandwidth, resource instances, uploads and total storage space used. From brief run a through of Amazon’s payment calculator I have come up with some really low monthly figures for your standard website.

I would strongly recommend this option as a solution to any potential start up websites that are still finding their feet. Even some of the larger sites that need to run less business critical resources such as video could benefit from this.

I plan to have a more in depth look into Azure and EC2 at some point in the near future.