#1 Burning Software

It is currently Wed Dec 18, 2024 11:07 pm

All times are UTC




Post new topic Reply to topic  [ 27 posts ]  Go to page 1, 2  Next
Author Message
 Post subject: StarBurn and .Net 4.0
PostPosted: Fri Feb 04, 2011 2:12 pm 
Offline

Joined: Fri Feb 04, 2011 2:01 pm
Posts: 9
Is there official support for StarBurn and the .Net 4.0 framework?

I've been having considerable difficulties getting it to work correctly. Curiously, there does not seem to be any problems compiling or running the executable directly, but when run through Visual Studio's debugging mode an exception is thrown immediately upon instantiation of the StarBurnX class. I've tried using various combinations of DLLs (the interop, manifest, starburnx) but they all behave in the same manner (though when I use the manifest I get different exception errors, they're far less verbose).

This is the exception detail from using the interop dll:

Code:
System.Windows.Markup.XamlParseException was unhandled
  Message='The invocation of the constructor on type 'FriendlySongsBurnonDemand.MainWindow' that matches the specified binding constraints threw an exception.' Line number '3' and line position '9'.
  Source=PresentationFramework
  LineNumber=3
  LinePosition=9
  StackTrace:
       at System.Windows.Markup.XamlReader.RewrapException(Exception e, IXamlLineInfo lineInfo, Uri baseUri)
       at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
       at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
       at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
       at System.Windows.Application.LoadBamlStreamWithSyncInfo(Stream stream, ParserContext pc)
       at System.Windows.Application.LoadComponent(Uri resourceLocator, Boolean bSkipJournaledProperties)
       at System.Windows.Application.DoStartup()
       at System.Windows.Application.<.ctor>b__1(Object unused)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
       at System.Threading.ExecutionContext.runTryCode(Object userData)
       at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
       at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.Run()
       at System.Windows.Application.RunDispatcher(Object ignore)
       at System.Windows.Application.RunInternal(Window window)
       at System.Windows.Application.Run(Window window)
       at System.Windows.Application.Run()
       at FriendlySongsBurnonDemand.App.Main() in Z:\kidmusic\project\FriendlySongsBurnonDemand\FriendlySongsBurnonDemand\obj\x86\Debug\App.g.cs:line 0
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.AppDomain.nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.Runtime.Hosting.ManifestRunner.Run(Boolean checkAptModel)
       at System.Runtime.Hosting.ManifestRunner.ExecuteAsAssembly()
       at System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext activationContext, String[] activationCustomData)
       at System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext activationContext)
       at System.Activator.CreateInstance(ActivationContext activationContext)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssemblyDebugInZone()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException: System.Runtime.InteropServices.COMException
       Message=Creating an instance of the COM component with CLSID {B756C224-A1EA-44F8-95C1-9F726040C800} from the IClassFactory failed due to the following error: 80010105.
       Source=mscorlib
       ErrorCode=-2147417851
       StackTrace:
            at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
            at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache)
            at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean skipCheckThis, Boolean fillCache)
            at System.Activator.CreateInstance(Type type, Boolean nonPublic)
            at System.Activator.CreateInstance(Type type)
            at FriendlySongsBurnonDemand.MainWindow..ctor() in Z:\kidmusic\project\FriendlySongsBurnonDemand\FriendlySongsBurnonDemand\MainWindow.xaml.cs:line 58
       InnerException:


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Mon Feb 07, 2011 4:52 pm 
Offline

Joined: Fri Feb 04, 2011 2:01 pm
Posts: 9
Does any one have any info on this? I'd like some sort of answer, even if it's just a plain "No" (though I really hope not).


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Tue Feb 08, 2011 1:15 pm 
Offline

Joined: Thu Dec 13, 2007 8:44 am
Posts: 609
Hello,

Try to refresh reference on the StarBurnX component! Remove the current StarBurnX interop reference and add new reference on StarBurnX COM component ( not to StarBurnX interop !!! )! As result the new valid "interop" will be generated!!


Regards,

Dmitry


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Tue Feb 08, 2011 1:31 pm 
Offline

Joined: Fri Feb 04, 2011 2:01 pm
Posts: 9
Unfortunately, I've tried this numerous times and always get the same results (exception upon class instantiation). I was only using the interop DLL because I had run out of other options for things to try out.

Additionally, I changed the target platform on the sample C# audio burner app from .Net 3 to .Net 4 and immediately got the exact same issue.

dima (staff) wrote:
Hello,

Try to refresh reference on the StarBurnX component! Remove the current StarBurnX interop reference and add new reference on StarBurnX COM component ( not to StarBurnX interop !!! )! As result the new valid "interop" will be generated!!


Regards,

Dmitry


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Tue Feb 08, 2011 2:49 pm 
Offline

Joined: Thu Dec 13, 2007 8:44 am
Posts: 609
1) Did you start your Visual Studio IDE under the Admin rights?

2) So .. we will check this issue!

Thanx,

Dmitry


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Wed Feb 09, 2011 1:36 pm 
Offline

Joined: Fri Feb 04, 2011 2:01 pm
Posts: 9
dima (staff) wrote:
1) Did you start your Visual Studio IDE under the Admin rights?

2) So .. we will check this issue!

Thanx,

Dmitry


Yes, Visual Studio has full permissions.


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Tue Feb 15, 2011 9:09 am 
Offline

Joined: Thu Dec 13, 2007 8:44 am
Posts: 609
Hello,

1) We have tested our C# samples with Visual Studio 2010 and .Net 4.0 ... all works fine!

2) So you should try to:
- remove old reference on the StaBurnX12 interrop;
- add new reference on the StaBurnX12.dll!!! [ "Add Reference ... "->COM->StarBurnX 12 Type library ]!!
- open properties window for the newly added reference and set the "Embeded Interop Types" property value with FALSE!!!
- specify target platform - x86 or x64 [ not ANY CPU!!].

- use the InitializeEx function and specify the SPTD transport ( instead of the SPTI ).

Regards,

Dmitry


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Tue Feb 15, 2011 9:37 pm 
Offline

Joined: Fri Feb 04, 2011 2:01 pm
Posts: 9
dima (staff) wrote:
Hello,

1) We have tested our C# samples with Visual Studio 2010 and .Net 4.0 ... all works fine!



I originally tested this out with your sample C# files (and just tried it out again to be certain). I'm testing with the AudioBurner project for VS2008, I converted the project to VS2010 format and changed the target framework to .NET Framework 4 Client Profile. Running the project in debugging mode (F5) causes an immediate exception on line 372:

Code:
m_starBurnX     = new StarBurnX();


Running without debugging seems to work fine, however this is unacceptable for development purposes.

I guess I'm just going to have to wrap all of my calls to the starburn API with checks against the debugger, since there doesn't really seem to be any other way around this at the moment.


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Wed Feb 16, 2011 9:39 am 
Offline

Joined: Thu Dec 13, 2007 8:44 am
Posts: 609
Hello,

I have tested AudioBurner once more with the "Framework 4 Client Profile" ... "DEBUG" works fine!!! .. so

1) Try to re-register the StarBurnX12.dll using the "regsvr32' utility;

2) Try to download the latest update of StarBurnX : link was removed


Regards,

Dmitry


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Wed Feb 16, 2011 1:54 pm 
Offline

Joined: Fri Feb 04, 2011 2:01 pm
Posts: 9
dima (staff) wrote:
Hello,

I have tested AudioBurner once more with the "Framework 4 Client Profile" ... "DEBUG" works fine!!! .. so

1) Try to re-register the StarBurnX12.dll using the "regsvr32' utility;

2) Try to download the latest update of StarBurnX : link was removed


Regards,

Dmitry


I actually downloaded the v12_340 version a while back when I saw it mentioned in another thread. Using the regsvr32 utility did not make any noticeable difference.

For clarification, my issue is not a build error, nor is it related to the build configuration. The application will compile just fine in both Release and Debug configurations. Additionally, the executable itself will operate without any problems. The exception only occurs when attempting to run the application through Visual Studio with the debugger attached (allowing you to use breakpoints, etc). I've had another developer attempt to use the DLL on a different computer with the exact same results (immediate exception on StarBurnX instantiation).


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Wed Feb 16, 2011 2:28 pm 
Offline

Joined: Thu Dec 13, 2007 8:44 am
Posts: 609
Yes, I understand you well! I do the same and ... it works!

Note: StarBurnX component uses the StarBurn.dll. Check is your version of StarBurn.dll up-to-date.

Regards,

Dmitry


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Sun Mar 20, 2011 11:36 pm 
Offline

Joined: Sun Mar 20, 2011 11:34 pm
Posts: 2
This article may help. It outlines each step. The key was getting the DLL registered as a COM so we could include it in our project.
http://www.cybersprocket.com/2011/sdks/starburn-sdk-and-net-4-0/

We spent a lot of time trying to figure this out, then we pieced together the step-by-step based on the clues provided here.


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Mon Mar 21, 2011 7:11 pm 
Offline
Site Admin

Joined: Fri Jun 18, 2004 12:03 am
Posts: 4089
Location: British Virgin Islands
Oh, thank you very much for your valuable feedback. It did help a lot!

P.S. Please do not remove quoted URL as we'd like to have it forever :)

cyberlance wrote:
This article may help. It outlines each step. The key was getting the DLL registered as a COM so we could include it in our project.
http://www.cybersprocket.com/2011/sdks/starburn-sdk-and-net-4-0/

We spent a lot of time trying to figure this out, then we pieced together the step-by-step based on the clues provided here.


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Wed Apr 13, 2011 9:13 am 
Offline

Joined: Mon Apr 11, 2011 12:25 pm
Posts: 8
Hallo,

I am using VS 2010, .Net 4.0 client profile, installed the updates and done everything mentioned in this page.
I am using the trial version to test the SDK.
I still cannot start the program with debugger.

Error:
Creating an instance of the COM component with CLSID {B756C224-A1EA-44F8-95C1-9F726040C800} from the IClassFactory failed due to the following error: 80010105.

I find that the file "Interop.RocketDivision.StarBurnX.dll" is automatically created in the Release\Debug folder.

What I could do is to start the application without attaching the debugger, I get the trial version ... message and later on I could attach with VS using Attach to process...

I find it inconvenient to use the API like this, any suggestions would be helpful...


Top
 Profile  
 
 Post subject: Re: StarBurn and .Net 4.0
PostPosted: Wed Apr 13, 2011 6:38 pm 
Offline

Joined: Thu Dec 13, 2007 8:44 am
Posts: 609
Hello,

1) If you have downloaded the latest StarBurnX update link was removed you should manually register the StarBurnX.dll using the 'regsvr32' utility.

2) Next, you should remove the old StarBurnX.interop reference from your project.

3) Next, go to the "Add Reference->COM" configuration page and select the 'StarBurnX 12 Type library'. As result, the new StarBurnX.interop file will be generated and attached into your project!

Regards,

Dmitry


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 27 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: Google [Bot] and 34 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group