New version of SOR Shell Extension

Starting from Windows Vista Microsoft has changed the API to add custom Explorer columns, breaking backward compatibility with shell extensions written for Windows XP. That's why our first Windows Vista/7 compatible version of SOR Shell Extension did not support the feature on these versions of Windows. Our users, which had updated their OSes, told us they were missing the custom columns feature. So, we have just uploaded a new version of SOR Shell Extension, which adds this feature back on Windows Vista and 7.

Feel free to download the new version from our site.

First iPhone application designed specifically for handling and analyzing fiber optic OTDR results will appear on the market in September 2011

Belarus, Minsk, Aug. 15, 2011

Wide practical experience of software and hardware development for fiber optic test&measurement industry and awareness of the fact that smartphones will further be more and more integrated into business processes allowed OptixSoft company to take a decision of development first iPhone application for engineers working closely with fiber optics - Fiberizer.

Fiberizer allows telecommunication engineers, fiber optic line installers and other experts using OTDR results in their job to review and analyze OTDR traces compliant with Telcordia GR-196 & SR-4731 standard in format of *.sor files. There are such features implemented in Fiberizer app as: possibility to connect and work with cloud based file sharing services like DropBox, Google Docs, utilizing of powerful usability multi-touch gestures for work with OTDR trace displaying, etc. OptixSoft mean to Fiberizer app release in Apple AppStore in September 2011.

Currently everyone can submit his email on the www.fiberizer.com and he will be notified once app is released.

About OptixSoft: Optixsoft is small software development company based in Minsk, Belarus. It provides system, cloud, mobile and desktop software development for companies occupied at fiber optic and test&measurement industry.

For more information, contact:

Eugene Belianka,

Fiberizer product manager

+375172270311

e.belianka@optixsoft.com

www.fiberizer.com, www.optixsoft.com

New version of SOR Shell Extension

There is a new version of SOR Shell Extension - Windows shell extension, that makes working with Bellcore GR-196/SR-4731 (.sor) files more convenient. This update contains several fixes and improvements, the most valuable from which are, probably, Windows 64-bit support and registry access fix.
You can download the update from our site.

P.S.: This is not an April Fools' Day joke :)

We are Growing and Developing new Business! Agizer.

Specialists of OptixSoft Software Company have accumulated experience in instruments design. Since our Firmware Engineers and Product Managers have been working closely in T&M industry over the years, we decided to bring our own vision of Test Instruments to the market.

News! OptixSoft supports and participates in new start-up which name is Agizer!

Recently we've completed a good job and launched pilot Agizer project - OPX-350 OTDR.
Of course our major responsibilities are software/firmware/OS and nowadays our managers supervise platform hardware design to meet our requirements.
Optical module was developed by newly created team, which consists of professionals with good portfolio in industry.

Next innovation project is on the way - it is small wireless measurement boxes controlled by customer mobile device (any PDA like iPhone, iPad, Android powered gadget).
Our apps at the AppStote and Android Market coming soon!

We are keep doing in T&M industry!

Garbage collector and local variables

If you are a C# programmer, then I have a question for you. How do you think, how many times the string "GC called" will be written to console by the following code:

using System;
using System.Threading;

class GarbageCollectorTest
{
   public static void Main()
   {
      Timer t = new Timer(CallGC, null, 1000, 1000);
      Console.ReadKey();
   }

   static void CallGC(object o)
   {
      GC.Collect();
      Console.WriteLine("GC called");
   }
}

Correct answer: depends on compilation parameters. In release build the string will be written only once. Debug version will write it until the user presses a key.


In C++ a local (automatic) variable's lifetime is defined by variable's scope - the variable will be destructed when program flow goes out of the scope.
In C# the lifetime of such variable is defined by how long the variable is used. I.e., the variable may be destructed before it goes out of scope, if garbage collector considers that it's not used any more.
In debug version variable's lifetime is artificially extended to its scope.

In Java, as far as I know, the JVM specification allows similar realization of garbage collector.

P.S.: If you are a C# programmer, but this post became an eye-opener for you, then read Jeffrey Richter's book "СLR via C#". You can find much more interesting and useful for.NET development in it.

C# quick question.

Can you quickly specify three advantages of automatic property over public field, as a member of a class?
I.e., why is the following code:

public string Foo{ get; set; }

better than this:

public string Foo;

The asnwer is (as often) on StackOverflow.

NOPs and debug

It's often necessary to edit source code during debug. To make this fixes to take effect, usually, you need to rebuild your application and restart the debug session. But there is edit-and-continue feature in Microsoft Visual Studio, which allows these fixes to take effect without restarting of the application. Ever thought about how it works?

The secret is in NOP instructions, which compiler inserts in certain places of executable code. These instructions can be replaced with new code later. Also, they allow to place breakpoints at those source code lines, which have no correspondent executable code. E.g., at the beginning of code block (opening brace in C++ and C#). Or at the operator, that would otherwise be replaced during optimization.

BTW: NOP-instructions may also be reasonable in application's release-version. E.g., to align code block for better caching.