DOT NET is one of the key products that enable application development under the new vision. However, DOT NET is not quite backward compatible with prior versions like visual basic version 6. This makes migration a serious issue. Converting existing source code to DOT NET architecture is not just a matter of loading it to the new version. DOT NET has its built-in migration tool, which performs the vital task of converting the source code syntax. But that’s just half of the work done. But before the converted code is actually compiled, the developer needs to enable it to smoothly fix lot of issues to fit into DOT NET architecture. In present efforts to find out solutions to these migration issues, a re-engineering Migration Model for Legacy Source Code (MMLC) has been proposed in this study. Proposed model has been further validated using a in-house project at one of the leading software development organisation. It is envisaged from the experimental try-out that the model would help the developer community to easily convert their legacy source code to DOT NET framework.
Read the rest of this entry »

• 0 Comments

The .NET framework was designed to be the “lingua franca” for Windows development, with the expectation that it will set a new standard for building integrated software for Windows. However, it is inevitable that there is a time lag before .NET is fully adopted and existing applications are recoded. In particular, there is a large body of legacy code that will likely never be rewritten in .NET. To address this situation, Microsoft provides attributes, assembly, and marshaling. At the Numerical Algorithms Group (where I work), our particular interest in using these techniques is to utilize numerical software developed in C from within the .NET environment. Because C# is the premier .NET language, the examples I present here are in C#. While I use an example of data types that are current in the NAG C Library, the techniques I present are general enough for calling unmanaged code written in C from C# directly.
Read the rest of this entry »

• 0 Comments

The introduction of Web 2.0 technologies into the enterprise greatly increases the value of your company?s most important asset: employees? knowledge, relationships and initiative. Increased collaboration accelerates productivity. Making knowledge more visible increases innovation and shortens turnaround times. Your company transforms into a more socially connected organization that reacts faster and more effectively to the market.
Read the rest of this entry »

• 0 Comments

The TriKinetics Drosophila Activity Monitoring System consists of one or more Activity Monitors, a Power Supply Interface Unit and Power Supply, and a host Macintosh or Windows PC for data collection. Each monitor uses an onboard microprocessor to independently detect and count activity events, and at periodic intervals to upload the activity totals to the host computer.

The monitors are connected to the Power Supply Interface Unit by a network of conventional 4-wire telephone cables which supply operating power and lines for data transmission. Monitors may be plugged and unplugged from the network at will without disturbing the activity of other monitors.
Read the rest of this entry »

• 0 Comments

JUDIE stands for Java Universal Database Import and Export. It was planned to allow users and developers to export data from one database to XML and import from this XML into another database. There are many use cases like data migration or setup of test databases. XML allows you to manipulate the data, maybe you already have XML export from legacy system and you can now transform this XML files (using XSLT) to JUDIE format. Also export from other tools (like db/Torque) can be easily transformed into JUDIE format and vice versa (see functional specification for more information about XML Schema/DTD).
Read the rest of this entry »

• 0 Comments

Why?
? Legacy and Common Architectures
? Access data in non-python languages
? Easy ad-hoc reporting
? ZODB optimized for reads not writes
? Relational has a proven track record
Read the rest of this entry »

• 0 Comments

To install PHP on an NT/2000/XP Server running IIS 4 or newer, follow these instructions. You have two options to set up PHP, using the CGI binary (php.exe in PHP 4, or php-cgi.exe in PHP 5) or with the ISAPI module. In either case, you need to start the Microsoft Management Console (may appear as ‘Internet Services Manager’, either in your Windows NT 4.0 Option Pack branch or the Control Panel=>Administrative Tools under Windows 2000/XP). Then right click on your Web server node (this will most probably appear as ‘Default Web Server’), and select ‘Properties’.
Read the rest of this entry »

• 0 Comments

As much as I would like people to believe that DotNetNuke was intentionally created as a premier open source project for the Microsoft platform, it is unfortunately not the case. As is true with many open source projects, the software was created with commercial intentions in mind, and only when it was discovered that its true purpose would not be realized was it reconsidered as an open source project.
Read the rest of this entry »

• 0 Comments