Introduction
We have been trying to get StarBurn to play well with others for a client project we have been working on lately. The problem is that StarBurn is very particular about the Windows environment, and though the support guys mean well the communication is sometimes hard to decipher. I don’t think English is their primary language, but can’t fault them there… they communicate much better in English than we speak French, or any other language for that matter.
Anyway, we deciphered some of their clues, experimented a bit, and finally came up with a step-by-step guide for getting the latest StarBurn SDK working well with our .Net 4.0 project. If you don’t get the right DLLs activated it will wreak havoc on your Visual Studio debug sessions and will not play well on most final release installs.
Step-By-Step
The first step is to make sure you have registered the StarBurn.X12.dll in your system registry via regsvr32:
1) Download & install latest StarBurn version. Make sure you have a January 2011 or later copy of StarBurn installed.
2) Run CMD as administrator. Search for “cmd” from the windows start menu, then right-click and “run as administrator”. If you do not run as admin you will get a cryptic error from Windows when using regsvr32.
3) CD to the StarBurn install directory. From the command prompt cd “…path-to-starburn-install”.
4) CD to the \Bin\Core\StarBurnX\x86 subdirectory.. Yes you could have done this all in one step, but I like to have the subdirectory spelled out so it is easier to find next itme around.
5) Register the DLL. Enter the command “regsvr32 StarBurnX12.dll”. You should get a message back with no errors saying the DLL was registered.
6) Remove any references to blah-interop-blah if you have them in your project. These references are wrong. Remove them. If you copied the setup from the sample solutions, they reference the Interop files, which is typically all you have to start with if you try registering anything StarBurn in your project prior to doing the regsvr32 trick noted above.
7) Add the corrrect StarBurnX 12.0 Type Library COM reference. Go to your project and add references. Click the COM tab. Look for the newly available “StarBurnX 12.0 Type Library” reference. This is what you want to add for .Net 4.0 Client Profile projects.
StarBurn COM Install
Manifestations
Here are some of the things you’ll see if this is not done correctly.
- Application crashes immediately on boot.
- Error code 8007007e simply means that a DLL that the application needs is not registered with the system.
- A common error when you have problems with StarBurn is “Retrieving the COM class factory for component with CLSID
{B756C224-A1EA-44F8-95C1-9F726040C800} failed…”. You can look for the CLSID by using regedit and searching for that string. This particular Class ID is registered to StarBurnX.StarBurnX, you can find it under HKCR/StarBurnX.StarBurnX/CLSID
Hope that helps some of you StarBurn developers out there. It sure took us a while to figure out the best way to do this, maybe this will save you a few hours.
