TX .NET used in a DLL?

[Unregistered]

Has anyone tried and succeeded in using TXText in a .NET application that is loaded dynamically by another application?

I've not been able to get this to work.


This message was originally posted by Mark Smith in the old TX Text Control Support Forum.

[Meik Dankleff]

There seems to be a bug in the current release of .NET which causes this problem. We will fix the problem in the next TX Text Control service pack.

[MarkSmith]

Meik -

When will that be?

This is a "stop-ship, sell the office, go home and apologise to wife and chidren for making them destitute, run and hide from investors" bug for us.

:eek:

[Björn Meyer]

Hello Mark

This is not possible with the TX Text Control .NET version, currently. We are working on this issue and will keep you all updated in this forum. Approx. a new update will be shipped in March/April 2003.

Björn Meyer, TX Text Control

[Nectar]

Maybe I'm talking about the wrong thing here,

I'm trying to add either the .NET or ActiveX versions to a Windows Control and then display it in Internet Explorer using ASP object tag.

I'm not having much luck. Would this fall under the same category?

[MarkSmith]

I'm working with Bjorn and his colleagues to see if one can use the Ax version instead of the .NET version in this context.

The good news is that you can import and launch the Ax control on a .NET application. This works being called from a DLL on my development PC.

My task for the rest of the evening is to build a distribution for my app to see if it works on our test PC.

[MarkSmith]

Originally posted by Nectar

I'm trying to add either the .NET or ActiveX versions to a Windows Control and then display it in Internet Explorer using ASP object tag

If you get a error with the TX.NET Licence manager then this is the same problem. Basically this programming erro (I don't use the term 'bug') means the .NET version is unusable if you don't control the host exe - eg you are writing an for IE or Office or any other third partyy app. :eek:

Regarding the AX version: I've certainly got as far as installing the TX Ax version onto my test PC, and getting it to appear in a .NET WinForm hosted by another application (Groove.exe - check out our website for more info!). To achieve this I needed to do some things with the registry as all the required keys didn't seem to appear.

I'll document how to get the Ax control to work in .NET and post it here once I've worked out how to do it automatically.

[Vann Joe]

Good work! I'll be interested in seeing your solution, though we aren't YET working on such ourselves.

[Martin Lang]

As a workaraound I moved the license file from the DLL project, which uses TXTextControl to my application project. Then it worked.:)

[MarkSmith]

More -

The registry issue seems to belong with the hosting application. Fortunately I can call a program to register the OCX properly myself as part of a one-time initialization. This problem shouldnt affect anyone else I don't think.

My current challenge is to put back the functionality I need into the OCX app - its only now that I'm realizing how much of an improvement the TX.NET object model is over the OCX one!

[MarkSmith]

More - part 2

Hmm, stymied again!

If you add a field and set its type to a value like txExternalLink, it doesn't actually get set, and retrieving it gives txStandard. This means you cannot have working hyperlinks in a document you save.

This is really weird. I can't think of any reason why one call (to set the field data) should work but another to set the field type should fail.

[MarkSmith]

Originally posted by Martin Lang
As a workaraound I moved the license file from the DLL project, which uses TXTextControl to my application project. Then it worked.:)

Yeah - there's no problem with that. The problem is when you don't control the application project, just the DLL. :(