Tomasz Modelski IT blog

Links Tagged - online demo - My Links - bug fix

Tomek@TomaszModelski.net — Fri, 17 Oct 2008 07:22:03 GMT

I've fixed error on Links Tagged -> Online Demo -> My Links page .
Registered user was unable to edit links (add, edit, update), now it's fixed.

Links Tagged Release 1.0

Tomek@TomaszModelski.net — Thu, 16 Oct 2008 10:24:04 GMT

Finally, I've done release 1.0 of 'TM Links Tagged' project - DNN modules that allow display, browse, manage links (bookmarks) with tags. Links can be even imported from Firefox 3.x backup file.
Please, go to project page.
There is online demo and free version available.

You can buy Links Tagged on Snowcovered.

I'm very very happy. I've learned a lot doing this project and release.

DNN 4.9 upgrade

Tomek@TomaszModelski.net — Wed, 15 Oct 2008 21:18:23 GMT

I've done upgrade to Dot Net Nuke 4.9 version.
Upgrade was smooth and without any problems.

But I've noticed one bug, releated to FckEditor (new provider) and blog.
On add or edit blog entry, in Summary text box, auto text is inserted '

'.
You can't see it in Rich Text mode, but it is, and when you finish, summary from blog entry won;t be generated, because there is already invisible summary '

'.
I need to remember always to switch summary to Basic mode and remove auto inserted HTML characters.

T-SQL split function

Tomek@TomaszModelski.net — Fri, 08 Aug 2008 19:01:24 GMT

I needed T-SQL split function and found on : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=543217&SiteID=1
by Jens Suessmeyer :

CREATE FUNCTION dbo.Split
(
   @String VARCHAR(200),
   @Delimiter VARCHAR(5)
)
RETURNS @SplittedValues TABLE
(
   OccurenceId SMALLINT IDENTITY(1,1),
   SplitValue VARCHAR(200)
)
AS
BEGIN
   DECLARE @SplitLength INT
   WHILE LEN(@String) > 0
   BEGIN
        SELECT @SplitLength = (CASE CHARINDEX(@Delimiter,@String) WHEN 0 THEN
            LEN(@String) ELSE CHARINDEX(@Delimiter,@String) -1 END)

        INSERT INTO @SplittedValues
            SELECT SUBSTRING(@String,1,@SplitLength)

        SELECT @String = (CASE (LEN(@String) - @SplitLength) WHEN 0 THEN ''
            ELSE RIGHT(@String, LEN(@String) - @SplitLength - 1) END)
   END
   RETURN
END

dotNetExt - .NET Extension Method Library

Tomek@TomaszModelski.net — Thu, 07 Aug 2008 12:06:05 GMT

I've encountered some very little small issue - string should not be longer that a certain number.
Substring method [ s.Substring(0,number) ] raises exception when string lenght is lesser than above number.

So small thing and additional code is required.
The best solution that come to my mind is to write extension method to string class.

Google .. and I've found it on Codeplex:
dotNetExt - .NET Extension Method Library

It has method Left(number) - I needed exactly such.
Another nice thing is that methods are well writen and deals nicly with nulls string, so :
string s=null;
string s1=s.Left(10);

executes without exception 'Object reference .... ' and s1=null.

Nice. This's beta, looking forward for release version.

DotNetNuke : Import module definition blank page error solution

Tomek@TomaszModelski.net — Tue, 05 Aug 2008 08:23:50 GMT

After upgrade DotNetNuke to 4.6 and higher versions error occurs : Page Host > Module Definitions > Import module definition is empty.

I've found solution on DNN forums , and posted it in 'usable' version :.

So, the solution is to run SQL script with Run as Script option, in Host > SQL :

IF EXISTS (SELECT * FROM dbo.sysobjects WHERE id = object_id(N'{databaseOwner}[{objectQualifier}GetUserRoles]') AND OBJECTPROPERTY(id, N'IsPROCEDURE') = 1)
DROP PROCEDURE {databaseOwner}{objectQualifier}GetUserRoles
GO

CREATE PROCEDURE {databaseOwner}{objectQualifier}GetUserRoles
@PortalId int,
@UserId    int

AS

SELECT
    R.*,
    UR.UserRoleID,
    U.UserID,
    U.DisplayName,
    U.Email,
    UR.EffectiveDate,
    UR.ExpiryDate,
    UR.IsTrialUsed
FROM {databaseOwner}{objectQualifier}UserRoles UR
    INNER JOIN {databaseOwner}{objectQualifier}Users U ON UR.UserID = U.UserID
    INNER JOIN {databaseOwner}{objectQualifier}Roles R ON UR.RoleID = R.RoleID
WHERE
    U.UserID = @UserId AND R.PortalID = @PortalId

GO

declare @ModuleDefID int

select @ModuleDefID = ModuleDefID
from   {databaseOwner}{objectQualifier}ModuleDefinitions
where FriendlyName = 'Module Definitions'
IF NOT EXISTS (SELECT ModuleControlID FROM {databaseOwner}{objectQualifier}ModuleControls WHERE ModuleDefID = @ModuleDefID AND ControlKey = N'Import')
BEGIN
insert into {databaseOwner}{objectQualifier}ModuleControls ( ModuleDefID, ControlKey, ControlTitle, ControlSrc, IconFile, ControlType, ViewOrder, HelpUrl, SupportsPartialRendering )
values ( @ModuleDefID, 'Import', 'Import Module Definition', 'Admin/ModuleDefinitions/ImportModuleDefinition.ascx', NULL, 3, NULL, NULL, 0 )
END

What's new in Visual Studio.NET 2008 by John Charles Olamendy

Tomek@TomaszModelski.net — Fri, 23 May 2008 08:05:14 GMT

I've started to use VS 2008.
Nice article, 'what's new' brefing :

http://www.c-sharpcorner.com/UploadFile /john_charles/ WhatnewinVisualStudioNET200802012008121831PM /WhatnewinVisualStudioNET2008.aspx

Downgrade database from MS SQL 2005 to MS SQL 2000 (copy database from MS SQL 2005 to MS SQL 2000)

Tomek@TomaszModelski.net — Tue, 20 May 2008 04:27:54 GMT

Text by Panos Tzirakis & George Dounavis found on http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=722132&SiteID=1 :

As you may all know, SQL Server 2005 request a minimum of 8GB RAM to work… let say satisfactorily. I first didn’t knew that and after a while from the upgrade I did from SQL Server 2000 to 2005 my SQL Services were starting to crash three or four times per DAY!!!

At first I thought I was being attacked, but soon I realized it was nothing like that. I then decided to downgrade to an SQL Server 2000 edition. Though I looked around the internet to find some information on how to do that, I got very disappointed when I realized that no actual documentation of any kind could be found for that. So I am posting this thread to inform you on the procedures I had to follow for this action.

Before beginning I must assume, firstly that the user, who will attempt such thing, has a basic knowledge of SQL Environment, secondly that he has the two versions already installed (both 2000 and 2005), that a basic backup of the databases has been created and finally that all the 2005 SQL Server Users have been created at the SQL Server 2000 environment as well.

Step 1 Generating Scripts for the Database Elements and Structures

1) Right-click over the desired Database at 2005, Choose Tasks and the Generate Scripts (Option).

2) At the pop-up Dialog Box click at the Script All Objects in the selected Databases check box, to activate it and then Click the Next Button.

3) Set the following Elements to the following Values

a. Script Collation , set to TRUE

b. Script Database Create, set to TRUE

c. Script of SQL Version, set to SQL SERVER 2000

d. Script foreign keys, set to FALSE

e. Script Triggers, set to FALSE

Then Hit the Next button

4) Select the way the generated scripts should be saved (There are different selections. The most common one is Clipboard). Finally click the Next button till you reach the end.

5) Click Finish

After completing this procedure, we have to move to the SQL SERVER 2000 environment. Here, by using the Query Analyzer, we will have to run the scripts that were generated using the master database. Copy and Paste the script at the Query Analyzer and run it. After that the Structure of the Database will be created.

Be careful, the SQL Server 2005 Edition inserts the Views in a random place through the script. Therefore, all the scripts that are referred to the Views MUST be moved to the end of the script. If the Query Analyzer shows some errors do not be bothered. Delete all the elements created from the script and after you fix the code run it again.

Step2 Moving the data from 2005 to 2000

1) After completing the previous step successfully, moving the data follows. Right-click at the 2005 database you used to run the previous step and select Tasks and then choose the Export Data (option).

2) From the pop-up Dialog Box, select the Source Db and Click at the Next Button.

3) At the next step you will have to choose the destination server and the destination Database for the Data to be exported. Then Click Next.

4) A List of all the Source Database’s Elements will appear in the screen. Select one by one all the Elements you wish to move and for each one click at the button Edit Mappings (Located at the bottom right corner of the Dialog Box just under the Elements list). A new Dialog box will pop-up. Select the Delete rows in Destination Tables option and activate the Enable Identity Insert Option. (Remember to repeat this action for each of the selected Element from the list that will be moved.

CAUTION!!! A malfunction of the SQL Server 2005 has been found. Not sure why, after multiple tries I have observed that when I tried to move more than twelve Elements at once, the Export Data Wizard of SQL Server 2005 seemed to disable the Enable Identity Insert Option that was activated over the Edit Mappings Dialog Box. But if the number of the selected Elements is smaller than 12 no problem seemed to appear.

Step 3 Generating Scripts for the Database Foreign Keys and Triggers

Finally, to successfully finish the downgrade of the Database, the Triggers and the Foreign Keys of the DB must be produced. The procedure that should be followed is the one stated next:

1) Right-Click at the SQL 2005 Database and Select from Tasks Menu the Generate Scripts Option.

2) Using the pop-up Dialog Box make sure that the check box Script All Objects in the selected Databases is not enabled and hit the Next Button.

3) Set all the Elements on the List to a False Value except the ones that follow:

a. Include IF NOT EXISTS , set to TRUE

b. Script Owner, set to TRUE

c. Script of SQL Version, set to SQL SERVER 2000

d. Script foreign keys, set to TRUE

e. Script Triggers, set to TRUE

Then Hit the Next button

4) After finishing reading the Elements of the Database, a new list will appear at the Dialog Box. Make sure that you select ONLY THE TABLES of the Database and hit the Next Button.

5) At the screen that follows hit the Select All button and the Next.

6) Select the way the generated scripts should be saved (There are different selections. The most common one is Clipboard). Finally click the Next button till you reach the end.

7) Click Finish Button.

After these steps the database should be fully functional under the SQL Server 2000 edition.

www.hellasinternet.com

Panos Tzirakis & George Dounavis

Still alive ...

Tomek@TomaszModelski.net — Sat, 26 Apr 2008 15:04:41 GMT

I didn't post anything for so long time.
A lot avtivities, studing & work. If I will find I'll write down new things I've discovered and worked on, ex: Ajax Pro on .Net 1.1 ans Sharepoint 2003, stored procs execution caching in SPS development, business methods caching, ... .

Found recently :

10 VS shortcuts you need to know - http://www.dev102.com/2008/04/17/10-visual-studio-shortcuts-you-must-know/

Foundations of Programming by Karl Sequin

Tomek@TomaszModelski.net — Thu, 06 Dec 2007 13:12:15 GMT

Serie of articles :
Part 1 : http://codebetter.com/blogs/karlseguin/archive/2007/11/29/171318.aspx
Part 2 : 'Domain Domain Domain'
Part 3 : Persistence