DNN - installing AjaxToolkit ahead of UKNuke RPX authentication

These were the draft steps I wrote about how to install the popup login functionality...

This is still in development... not really ready for primetime yet!

Stuart

1. AjaxToolkit

You need the AjaxToolkit installed within your DNN bin folder. This can be downloaded fromhttp://www.codeplex.com/AjaxControlToolkit. To install it you may also need to update your System.Web.Extensions.dll to a more recent version (and indeed you may need to update the whole portal to .Net 3.5). 

I can't assist you with this part in detail here - but there are quite a few links/instructions out there on Bing/Google!

One thing that helped me was updating web.config to include this "bindingRedirect" section:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

- this taken from a DNN 5.1.4 example portal.

2. Install the new RPX module I just sent you

3. Change your skin

You'll need to add this to the top of your skin:
<%@ Register TagPrefix="uknuke" TagName="Login" Src="~/DesktopModules/AuthenticationServices/UkNuke.RPX/LoginButton.ascx" %>

And you'll need to add this wherever you want the login link to appear:
<uknuke:Login ID="specialLogin" runat="server"></uknuke:Login>

4. That should be it :)

Some difference in DNN 5.1.4 - logging into SQL2005

For some reason my old connection strings - which started "Server=(local);" no longer work in DNN 5.1.4

To fix this, this gave me a clue: http://www.dnncreative.com/Forum/tabid/88/forumid/4/postid/15390/view/topic/Default.aspx

Basically, the connection string now starts "(local);" 

Getting AjaxToolkit to work in an old project

I was trying to update an old DotNetNuke project so it would use the AjaxToolkit.

To do this I had various problems with System.Web.Extensions versioning.

After some pain, I discovered one solution was to add this section to the web.config file :)

  <runtime>

    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <probing privatePath="bin;bin\HttpModules;bin\Providers;bin\Modules;bin\Support;" />

 <dependentAssembly>

 <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31BF3856AD364E35" culture="neutral"/>

 <bindingRedirect oldVersion="1.0.61025.0" newVersion="3.5.0.0"/>

 </dependentAssembly>

 <dependentAssembly>

 <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31BF3856AD364E35" culture="neutral"/>

 <bindingRedirect oldVersion="2.0.0.0" newVersion="3.5.0.0"/>

 </dependentAssembly>

 </assemblyBinding>  

  </runtime>

Finding a table name

I knew my table had "comment" in it... so I used this to find out the table name

SELECT name
FROM dbo.sysobjects
WHERE xtype = 'U' AND NAME LIKE '%COMMENT%'

I could also have used xtype:
'V' - views
'S' - system tables

From: http://database.ittoolbox.com/documents/finding-table-names-in-sql-18556 - thanks!

SagePay processing for nopcommerce - my first codeplex launch

Spent lots of today coding a SagePay payment processor for NopCommerce.

The details of it are on cirrious at: http://www.cirrious.com/Research/NopCommerceSagePay/tabid/62/Default.aspx

And I've launched it as a codeplex project at: http://nopsage.codeplex.com/

Overall I'm quite impressed with the support info available at http://www.sagepay.com/ - and their simulator is very useful for testing.