Hello, Thank you for your project. Just for your information, you can see in this image that your project works without a problem when deleting the references to TeeChart.dll and TeeChart.OpenGL.dll from your project and then adding in the latest NuGet package: Screenshot from 2022-08-10 13-39-30.pn...

Hello, We have a Website project example in one of our GiHub repos for .NET Framework 4, which you can see here: https://github.com/Steema/TeeChart-NET-Pro-Samples/tree/main/Web-API/NET%20Framework/TeeChart%20WebDemo Are any of the techniques shown there helpful to you? We would especially recommend...

Hello, again, apologies for our delay in getting back to you here. I think there is some confusion here. Historically, the TeeChart assemblies (TeeChart.dll, TeeChart.WPF.dll etc. etc.) have been delivered to client machines in two different ways: 1. Using a stand-alone installer 2. Using NuGet pack...

Hello,

apologies for the delay in our reply to you. Do you still have the Visual Studio project (*.csproj) you used to run your test with TeeChart? If so, could you please remove the binary files in the bin and obj directories, put it in a zip file, and post it here so I can test it here?

Hello Holgar, we're looking at this now, and we've got a quick question to ask you if that's okay with you. When you say that: The AddPalette function is similar to what I like to have but it does not automatically scale with Z values. what code can we use to see what you mean? The following code ge...

You're right, I cut the application to the bone and saw that if I publish the watermark it disappears. I didn't do this application but the problem at this point is of a different nature. I will investigate You're welcome. I'm glad to hear you managed to get that to work, please don't hesitate to c...

Hello, Thanks so it works. Great! Which means it does work if the configuration is right. I have another question regarding this topic. I have an old web-api application, I followed the example and added the various files for the license. In debug everything works but when I publish it I see the wat...

Hello Marta, once you have the sample on the other thread working in Debug, you can publish it to IIS. The steps are: 1. Add an application to your IIS: Screenshot from 2022-05-30 14-52-28.png 2. Modify the source code of Content.aspx.cs so it looks like this (make sure the 'webServer' variable has ...

Hello, How can I install the new license in this project? It is not a Web Forms project. I think there's an example of an old project type in our GitHub sample repos, specifically this sample here . I've just updated this sample to version 4.2022.4.26, and using this version I can paste in my licens...

Hello, please find attached a project demonstrating the use of multiple X axes, the code of which comes from one of the forum posts I suggested you to look at. MultiAxes.zip Can you please modify this project to demonstrate the problem you are experiencing with multiple X axes so that I can reproduc...

Hi Holgar, first of all, many thanks for your continuing use and support of Steema's TeeChart. It is a pleasure for us to work to continue such long-standing relationships. I've added your post to our issue tracker with id=2530 . Some of these requests are going to be easier and quicker to implement...

Hello,

please send me your licenses file to chris@steema.com and I will use it to respond with examples in both .NET Framework 4.8 and .NET 6.0.

Good morning, There was an issue with designtime use of TeeChart with the evaluation version in the NuGet version 4.2022.5.18 which we resolved in 4.2022.5.23 . You can check the contents of your TeeChart.licenses file here —you will need 'teechart.winform' in the assemblies list to use TeeChart in ...

Hello, apologies for the delay in response to this message. There are several questions related to ' multiple axes ' and ' multiple custom ' which may be of help; there is also the .NET Framework Windows Forms sample which has a couple of demos on custom axes: Screenshot from 2022-05-20 14-35-49.png...

Unfortunatelly I'm serious. My motivation is pretty simple (and lost of developers unfortunatelly have the same ) - Visual Studio 2019 doesn't officially support .NET 6 development. But purchasing a bunch of Visual Studio 2022 licenses in not so easy (and quick) task in large enterprise organisatio...