Roman Nikitin

IPBtoCS2007 & PHPBBtoCS2007: new releases

2008-05-02T10:11:00Z

New release of IPBtoCS2007 Converter.

Also PHPBB to CS2007 converter released.

You can view\download here: http://www.codeplex.com/csconverter/Release/ProjectReleases.aspx?ReleaseId=13037

About any bugs and problems please tell me.

Invision Power Board 2.x.x to Community Server 2007 Converter

2008-01-08T04:03:13Z

Some time ago I decided to move my community (worked on Invision Power Board) to Community Server 2007 and create blogs for all users.

But I didn't find any converter software.

So, I wrote converter by myself.

In this project i used LINQ for Community Server MSSQL database and Mysql LINQ Provider for IPB MySQL database.

Several restrictions, such as necessity of additional memory, can be found in this program because of some limitations at the earliest stage of MySQL Linq Provider development.

Because the initial stage of the last and its limitations, I cache all data in Program, so on big database there big memory usage.

What is supported:

convert all users with unique emails
Forum structure converting
Full converting of threads and topics
Optional. Blog auto-create for each converted user.

What is missed:

Additional information (ICQ, Yahoo, MSN information)
User signatures
Avatars
Display names (if they turned on in IPB)
User groups and roles
Forum permissions
Attachments
Voting's

Another restriction for IPB: database must have "ibf_" prefix.

I strongly recommend you to convert forums on local machine.

Conversion of the ~2000 users, ~2000 topics and ~60000 posts took on my machine about 15-20 minutes.

I have published whole solution. You can change the code and use it in any purposes (except commercial use).
I don't grant any warranties and don't respond of data loses. Do backup yourself

If you have any questions - I will be happy to answer them.

Also will be great if you made some enhancements and share they. May be one day this project will be placed on codeplex.com

That the link: IPBtoCS_0.0.0.1.zip

Sys.Debug in Asp.Net Ajax Framework

2007-11-21T23:27:35Z

Every developer needs to debug his applications. There are two ways:

Debugging - step-by-step tracking of an application process.
Tracing - monitoring of application processes without breaking and writing useful information in a special console.

Asp.Net developers wrote the great Ajax Framework. There is so much stuff for professionals and beginner developers.
Also they didn't forget about debugging tools. (may be was done first)

class Sys.Debug contains 5 methods:

   1:  // output the text message into Debug Console

   2:  Sys.Debug.trace(text);

   3:  // output the information about specified object into Debug Console.

   4:  // second parameter (object name) - is optional

   5:  Sys.Debug.traceDump(object, name);

   6:  // clear Debug Console*

   7:  Sys.Debug.clearTrace();

* - it doesn't clear Debug Console of your default Debugger(more information below the post).

   1:  // output the message only if(condition == true)
   2:  // if the third parameter is specified and set to true then name of the caller function will be shown
   3:  Sys.Debug.assert(condition, message, displayCaller);
   4:  // output the message into Debug Console and break program into default debugger in the invocation point
   5:  Sys.Debug.fail(message);
 

So, what does "Debug Console" mean?

Let`s see the core of Asp.Net Ajax Framework (MicrosoftAjax.js).

There are 2 interesting methods:

   1:  // output the text message into Debug Console window of your current debugger.

   2:  this._appendConsole(text);

   3:  // output the text message into textarea in the webform (more information below the text)

   4:  this._appendTrace(text);

Debugger Console may looks like that (Output window in your favorite Visual Studio):

Or like that (Console tab in Firebug plugin for Mozilla Firefox):

Or something else.

So, what does second method do?

   1:  this._appendTrace(text);

Follow it source:

   1:  var traceElement = document.getElementById('TraceConsole');

   2:  if (traceElement && (traceElement.tagName.toUpperCase() === 'TEXTAREA'))

   3:  {

   4:       traceElement.value += text + '\n';

   5:  }

It looks up an element with ID="TraceConsole" in a webform and verify for the "textarea" type. If well done, message will be written into this element.

Exactly that Console will be cleaned by the method

   1:  Sys.Debug.clearTrace();

Sys.Debug works only if:

debug="true" in Web.config

   1:  <compilation debug="true">

2. ScriptMode="Debug" or ScriptMode="Inherit" (it will be inherited from web.config ) in ScriptManager in the page.

   1:  <asp:ScriptManager ID="ScriptManager1" runat="server" ScriptMode="Debug">

In conclusion I want to say, that Sys.Debug saves my time and nerves. What about you?

Technorati Теги: Ajax,Asp.Net,Debug,Framework,JavaScript,Microsoft,Scripting,Sys.Debug,Programming