By Oleg Zhukov on 2/9/2010 12:32 AM

 

Read More »

By Oleg Zhukov on 2/8/2010 10:10 PM

The other day I needed to unzip a bunch of zip-archives, modify the unzipped content and zip them back again. Since I'm lazy (as every developer should be) I decided to write a tool that would do all the work for me.

After googling around I found several ways of handling zip archives...

Read More »

By Oleg Zhukov on 6/20/2008 5:31 AM

API documentation may be of great importance to a project. Especially when the project is a library intended for use by other developers. As a rule such documentation is represented in a form of help files (*.hxk for instance) or in a form of HTML pages contating reference for all project's namespaces, classes and etc.

However neither .NET framework nor Visual Studio contain tools for creating API documentation. Instead, developers need to address some separate tools for this aim.

For a long time NDoc tool has been the best choice to generate API docs from source code comments. It is fast, reliable, easy-to-use and free. But unfortunalely NDoc project was freezed and is not supported anymore. It works only with .NET 1.1 projects.

Read More »

By Oleg Zhukov on 12/22/2007 12:39 PM

Whereas the Windows Presentation Foundation (a part of .NET 3.0) introduces pure .NET classes for drawing simple 3D graphics, its functionality may be not enough for feature-rich 3D applications. If this is the case, some more powerful graphics library may be required, such as OpenGL. Fortunately a managed .NET facade to unmanaged OpenGL dll's exists. This facade is a part of the Tao framework and allows accessing OpenGL functions from .NET applications as easily as it is done from managed C/C++ code.

Last few days I have been experimenting with OpenGL in .NET and have written a small application which visualizes 3D objects specified in a binary STL file format. The application allows moving and rotating the camera (eye point) and switching between different rendering options (sm ... Read More »

By Oleg Zhukov on 10/21/2007 2:14 PM

Sometimes building a software product from the source code requires more than just compiling. That is the case especially for big software systems where the build process consists of numerous steps.

A long long time ago (don't ask when :) the MAKE utility appeared to solve this problem. It offered a rather powerful scripting language for describing the build process. But time went by and new utilities came to substitute MAKE. They didn't have the drawbacks peculiar to MAKE and used XML as a script format. One of such tools was Ant and its .NET clone named NAnt. Microsoft suggested their own build tool too (well, that was expected :) under MSBuild name. Here I would not devle into MSBuild and Ant comparison, but I am going to list the things that really make MSBuild attractive compared to NAnt:

• Tight integartion with Visual Studio IDE. Actually VS projects are MSBuild scripts. And modifying the project means just modifying the MSBuild script. An ... Read More »
  Comments (0)

By Oleg Zhukov on 6/10/2007 4:32 AM

The majority of .NET developers are still sitting on 1.1 and 2.0 versions and are thinking of all those troubles they will meet moving to 3.0 and 3.5. However there are no reasons for pessimism since 3.0 and 3.5 are based on 2.0 and utilize the same CLR 2.0 version. This is the case when 3.5 - 2.0 < 1.5. In his recent post Daniel Moth explains this in detail. The difference between VS2005 and upcoming VS2008 is not as much either. See another Moth's post about VS2008 stack.